Openmoko - User contributions [en]

SettingsGUI

2008-07-31T00:43:58Z

Kriss: /* Get GPRS working anyway */ typo

{{InProgress}}
[[Image:SettingsGUI-0.8-screen.png|thumb|SettingsGUI - Screen Settings]]
[[Image:SettingsGUI-0.8-audio.png|thumb|SettingsGUI - Audio Settings]]
[[Image:SettingsGUI-0.8-gsm.png|thumb|SettingsGUI - GSM Settings]]
[[Image:SettingsGUI-0.8-gprs.png|thumb|SettingsGUI - GPRS Settings]]
[[Image:SettingsGUI-0.8-bluetooth.png|thumb|SettingsGUI - Blueooth Settings]]

== Overview ==
Until [[OpenMoko]] releases an official GUI-Tool to change settings, SettingsGUI allows you to set various settings of the [[gta01]].

This program is written in [[Python]] using pygtk. It can be used only if those are present in your environment (see [[SettingsGUI#Environment]]).

== Current Features ==

* Screen (Backlight enable/disable, Backlight brightness, Screen Orientation)
* Audio (profile selection, volume, mute, save to profile)
* [[GSM]] (restart [[gsmd]], signal strength, provider, status)
* [[GPRS]] (load and save settings from and to /etc/ppp/peers/, connect, set APN, User, Password, Number)
* [[Bluetooth]] (enable/disable, set-up/monitor PAN connections, scan for peers)

== Planned Features ==

* GSM (Provider selection)
* [[Bluetooth]] (signal strength)
* GPRS (display transfer rate, activate GPRS router)
* [[Battery]] (show capacity, voltage, charger-status)

== Comment on GSM Support ==

* As there are no gsmd python bindings available at the time, SettingGUI uses python-subprocess and threads to communicate to the commandline of [[Gsmd#libgsmd-tool | libgsmd-tool]] for the time being.

* To prevent interference with the GSM modem you have to expicitly power-up and register the modem by toggeling the "GSM State" checkboxes.

* If you manually register to the gsm network (by toggeling the "Register" checkbox) SettingsGUI will sometimes not notice when the connection is established. Just toggle the init checkbox after about 3 seconds. (this seems to be due to a bug in gsmd...)

{{note|From Version 0.7 the atcmd mode of libgsmd-tool is used. To use it revision 2957 (2007-09-12) or later of gsmd is needed. If you have an older version of gsmd - or an older OpenMoko image - use the upgrade function of [[ipkg]], install a newer jffs2 image or use version 0.6 of SettingsGUI.}}

* When the GPRS connection is still active ([[pppd]] running on the system) you should close the connection as gsmd can't start up while pppd is using the modem connection - chose "Yes" in the dialog:

[[Image:SettingsGUI-0.7-close gprs.png|170px]]

== Comment on GPRS Support ==

If you have problems connecting check:

* If the modem is initialized and registered to a network (Start gsmd and register)
* If your login data (mostly APN and User are okay)

* When the gsmd still running you should close the connection as gsmd will interfere with pppd - chose "Yes" in the dialog:

[[Image:SettingsGUI-0.7-terminate-gsmd.png|150px]]

The connection will be terminated when you quit the application.
However saved peer configurations can be called independently using:

pppd debug call gprs # where gprs is the peer

Default configuration files are defined in GlobalConfiguration.py. The peer configuration, a connect- and disconnect chat script are written to /etc/ppp/peers/ on first startup if you don't already have a peer in /etc/ppp/peers/. When the connect button is pressed SettingsGUI will create latest_* files in /etc/ppp/peers/ and start the pppd with this latest_* peer.

SettingsGUI also brings a default Nameserver in case you don't have a valid /etc/resolve.conf. The IP is from the OpenDNS Project and will only work if your GPRS provider allows DNS access to this server.

If you have to change anything else than APN, user, password or dial in number for your provider please leave a note at the Discussion Page.

For details and background information on GPRS see [[Manually using GPRS]].

== Comment on Bluetooth Support ==

With SettingsGUI you can only connect using PAN. Due to display real estate problems Version 0.8 does not support HID pairing yet.

The IP address for your PAN connection will be generated from a configurable mask (see GlobalConfiguration.py) and the last byte of the Bluetooth Address (think of MAC address). Default IP is 10.0.0.x.

For details and background information on Bluetooth see [[Manually using Bluetooth]].

== Download ==
=== Releases ===
{|border=1
! Version
! Download
! Release Focus
! Release Date
|-
| 0.8 ('''current''')
| [http://mput.de/~kristian/.openmoko/settingsgui-0.8.tar.bz2 settingsgui-0.8.tar.bz2]
| bluetooth settings, reorganized package structure ("settingsgui" python package included, startscript is named "settings" now)
| 2008-03-16
|-
| 0.7b
| [http://mput.de/~kristian/.openmoko/settingsgui-0.7b.tar.bz2 settingsgui-0.7b.tar.bz2]
| bugfix on GSM page, bug prevented detection of gsmd connection (emerged with libgsmd-tool update)
| 2007-10-02
|-
| 0.7
| [http://mput.de/~kristian/.openmoko/settingsgui-0.7.tar.bz2 settingsgui-0.7.tar.bz2]
| cleanups, using AT mode, distutils, ATDT -> ATD
| 2007-09-21
|-
| 0.6
| [http://mput.de/~kristian/.openmoko/SettingsGUI-0.6.tar.gz SettingsGUI-0.6.tar.gz]
| audio settings (mute, save), gprs settings (all new)
| 2007-09-06
|-
| older
| [http://mput.de/~kristian/.openmoko/ Directory listing]
|}
=== SVN ===
Access the current SVN version at: http://neo1973-germany.de/svn/SettingsGUI/
=== Packages ===
The Package is now buildable by bitbake. Download the latest .ipk from: [http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/ipk/armv4t/settingsgui_0.7+0.8-beta-r0_armv4t.ipk settingsgui_0.7+0.8-beta-r0_armv4t.ipk]

Thanks to [[User:Alessandro | Alessandro]] there still is the inofficial .ipk and a .bb file. Have a look at his user site.

== Environment ==

:''For more, see [[Python]].''

The following archives will have to be installed (source packages: python python-pygtk python-pycairo python-pygobject):

* python-core
* python-misc
* python-lang
* python-pygtk
* python-subprocess
* python-threading (should be a dependency of python-subprocess - todo: fix)
* python-pygobject (should be a dependency of python-pygtk - todo: fix)

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

== Installation / Execution ==

=== FSO and ASU Users ===

Use the latest Version from SVN for now.
svn co http://neo1973-germany.de/svn/SettingsGUI/trunk SettingsGUI-svn

The following addidional packages have to be installed:
opkg install alsa-utils-amixer
opkg install bluez-utils
# opkg install gsmd
# opkg install gsmd-tools

==== GPRS / GSM Panel ====
'''You may not want to use those with FSO/ASU! - It WILL break the phone applications (no calls / sms)!'''

SettingsGUI is not yet supporting the new framework-stack, so you'll have to use gsmd for GSM/GPRS. Therefore you would have to install the packages and stop the gsmget daemon already running. Once you've installed gsmd it may start on every system boot, which may then prevent any other GSM daemon from starting. This may break your phone applications until you fix the problem again.

===== Get GPRS working anyway =====
1) Stop gsmget
killall gsmget

2) Connect to your mobile carrier using the GSM Panel

3) Connect to GPRS (answer "yes" when asked to kill the GSM daemon)

=== From package ===
* add Alessandros repository as a [[ipkg]] source

vi /etc/ipkg/alessandro.conf

* insert

src/gz aiurlano-armv4t http://aiurlano.netsons.org/OpenMoko/ipk/armv4t
src/gz aiurlano-all http://aiurlano.netsons.org/OpenMoko/ipk/all

* update your db

ipkg update

* install latest settingsgui

ipkg install settingsgui

=== From source ===
* download file to Neo (e.g. using wget)
* Uncompress tar.bz2 file (e.g. e.g. tar -xjvf file.tar.bz2)
* install:
cd settingsgui-x.x
mv settingsgui settingsgui.py
mkdir settingsgui
mv * settingsgui
mv settingsgui/settingsgui.py ./

* run:
export DISPLAY=:0.0
python settingsgui.py &

=== Comment on Installation ===

From Version 0.7 Python distutils is used. So you could also use the setup.py script to install the package:
python settingsgui-x.x/setup.py install

For Version 0.8beta (I didn't test for 0.7), don't change any names, just unpack and then:
cd settingsgui-x.x
python setup.py install

But to do this you'll also have to install the packages:
python-compile python-devel python-stringold python-distutils

==References==
* [http://www.mput.de/projects/code/settingsgui/ Project Homepage]

[[Category:Applications]]
[[Category:Openmoko]]
[[Category:Guides]]

SettingsGUI

2008-07-31T00:43:09Z

Kriss: /* Installation / Execution */ - Use with GTA02 and FSO/ASU

{{InProgress}}
[[Image:SettingsGUI-0.8-screen.png|thumb|SettingsGUI - Screen Settings]]
[[Image:SettingsGUI-0.8-audio.png|thumb|SettingsGUI - Audio Settings]]
[[Image:SettingsGUI-0.8-gsm.png|thumb|SettingsGUI - GSM Settings]]
[[Image:SettingsGUI-0.8-gprs.png|thumb|SettingsGUI - GPRS Settings]]
[[Image:SettingsGUI-0.8-bluetooth.png|thumb|SettingsGUI - Blueooth Settings]]

== Overview ==
Until [[OpenMoko]] releases an official GUI-Tool to change settings, SettingsGUI allows you to set various settings of the [[gta01]].

This program is written in [[Python]] using pygtk. It can be used only if those are present in your environment (see [[SettingsGUI#Environment]]).

== Current Features ==

* Screen (Backlight enable/disable, Backlight brightness, Screen Orientation)
* Audio (profile selection, volume, mute, save to profile)
* [[GSM]] (restart [[gsmd]], signal strength, provider, status)
* [[GPRS]] (load and save settings from and to /etc/ppp/peers/, connect, set APN, User, Password, Number)
* [[Bluetooth]] (enable/disable, set-up/monitor PAN connections, scan for peers)

== Planned Features ==

* GSM (Provider selection)
* [[Bluetooth]] (signal strength)
* GPRS (display transfer rate, activate GPRS router)
* [[Battery]] (show capacity, voltage, charger-status)

== Comment on GSM Support ==

* As there are no gsmd python bindings available at the time, SettingGUI uses python-subprocess and threads to communicate to the commandline of [[Gsmd#libgsmd-tool | libgsmd-tool]] for the time being.

* To prevent interference with the GSM modem you have to expicitly power-up and register the modem by toggeling the "GSM State" checkboxes.

* If you manually register to the gsm network (by toggeling the "Register" checkbox) SettingsGUI will sometimes not notice when the connection is established. Just toggle the init checkbox after about 3 seconds. (this seems to be due to a bug in gsmd...)

{{note|From Version 0.7 the atcmd mode of libgsmd-tool is used. To use it revision 2957 (2007-09-12) or later of gsmd is needed. If you have an older version of gsmd - or an older OpenMoko image - use the upgrade function of [[ipkg]], install a newer jffs2 image or use version 0.6 of SettingsGUI.}}

* When the GPRS connection is still active ([[pppd]] running on the system) you should close the connection as gsmd can't start up while pppd is using the modem connection - chose "Yes" in the dialog:

[[Image:SettingsGUI-0.7-close gprs.png|170px]]

== Comment on GPRS Support ==

If you have problems connecting check:

* If the modem is initialized and registered to a network (Start gsmd and register)
* If your login data (mostly APN and User are okay)

* When the gsmd still running you should close the connection as gsmd will interfere with pppd - chose "Yes" in the dialog:

[[Image:SettingsGUI-0.7-terminate-gsmd.png|150px]]

The connection will be terminated when you quit the application.
However saved peer configurations can be called independently using:

pppd debug call gprs # where gprs is the peer

Default configuration files are defined in GlobalConfiguration.py. The peer configuration, a connect- and disconnect chat script are written to /etc/ppp/peers/ on first startup if you don't already have a peer in /etc/ppp/peers/. When the connect button is pressed SettingsGUI will create latest_* files in /etc/ppp/peers/ and start the pppd with this latest_* peer.

SettingsGUI also brings a default Nameserver in case you don't have a valid /etc/resolve.conf. The IP is from the OpenDNS Project and will only work if your GPRS provider allows DNS access to this server.

If you have to change anything else than APN, user, password or dial in number for your provider please leave a note at the Discussion Page.

For details and background information on GPRS see [[Manually using GPRS]].

== Comment on Bluetooth Support ==

With SettingsGUI you can only connect using PAN. Due to display real estate problems Version 0.8 does not support HID pairing yet.

The IP address for your PAN connection will be generated from a configurable mask (see GlobalConfiguration.py) and the last byte of the Bluetooth Address (think of MAC address). Default IP is 10.0.0.x.

For details and background information on Bluetooth see [[Manually using Bluetooth]].

== Download ==
=== Releases ===
{|border=1
! Version
! Download
! Release Focus
! Release Date
|-
| 0.8 ('''current''')
| [http://mput.de/~kristian/.openmoko/settingsgui-0.8.tar.bz2 settingsgui-0.8.tar.bz2]
| bluetooth settings, reorganized package structure ("settingsgui" python package included, startscript is named "settings" now)
| 2008-03-16
|-
| 0.7b
| [http://mput.de/~kristian/.openmoko/settingsgui-0.7b.tar.bz2 settingsgui-0.7b.tar.bz2]
| bugfix on GSM page, bug prevented detection of gsmd connection (emerged with libgsmd-tool update)
| 2007-10-02
|-
| 0.7
| [http://mput.de/~kristian/.openmoko/settingsgui-0.7.tar.bz2 settingsgui-0.7.tar.bz2]
| cleanups, using AT mode, distutils, ATDT -> ATD
| 2007-09-21
|-
| 0.6
| [http://mput.de/~kristian/.openmoko/SettingsGUI-0.6.tar.gz SettingsGUI-0.6.tar.gz]
| audio settings (mute, save), gprs settings (all new)
| 2007-09-06
|-
| older
| [http://mput.de/~kristian/.openmoko/ Directory listing]
|}
=== SVN ===
Access the current SVN version at: http://neo1973-germany.de/svn/SettingsGUI/
=== Packages ===
The Package is now buildable by bitbake. Download the latest .ipk from: [http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/ipk/armv4t/settingsgui_0.7+0.8-beta-r0_armv4t.ipk settingsgui_0.7+0.8-beta-r0_armv4t.ipk]

Thanks to [[User:Alessandro | Alessandro]] there still is the inofficial .ipk and a .bb file. Have a look at his user site.

== Environment ==

:''For more, see [[Python]].''

The following archives will have to be installed (source packages: python python-pygtk python-pycairo python-pygobject):

* python-core
* python-misc
* python-lang
* python-pygtk
* python-subprocess
* python-threading (should be a dependency of python-subprocess - todo: fix)
* python-pygobject (should be a dependency of python-pygtk - todo: fix)

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

== Installation / Execution ==

=== FSO and ASU Users ===

Use the latest Version from SVN for now.
svn co http://neo1973-germany.de/svn/SettingsGUI/trunk SettingsGUI-svn

The following addidional packages have to be installed:
opkg install alsa-utils-amixer
opkg install bluez-utils
# opkg install gsmd
# opkg install gsmd-tools

==== GPRS / GSM Panel ====
'''You may not want to use those with FSO/ASU! - It WILL break the phone applications (no calls / sms)!'''

SettingsGUI is not yet supporting the new framework-stack, so you'll have to use gsmd for GSM/GPRS. Therefore you would have to install the packages and stop the gsmget daemon already running. Once you've installed gsmd it may start on every system boot, which may then prevent any other GSM daemon from starting. This may break your phone applications until you fix the problem again.

===== Get GPRS working anyway =====
1) Stop gsmget
killall gsmget
2) Connect to your mobile carrier using the GSM Panel
3) Connect to GPRS (answer "yes" when asked to kill the GSM daemon)

=== From package ===
* add Alessandros repository as a [[ipkg]] source

vi /etc/ipkg/alessandro.conf

* insert

src/gz aiurlano-armv4t http://aiurlano.netsons.org/OpenMoko/ipk/armv4t
src/gz aiurlano-all http://aiurlano.netsons.org/OpenMoko/ipk/all

* update your db

ipkg update

* install latest settingsgui

ipkg install settingsgui

=== From source ===
* download file to Neo (e.g. using wget)
* Uncompress tar.bz2 file (e.g. e.g. tar -xjvf file.tar.bz2)
* install:
cd settingsgui-x.x
mv settingsgui settingsgui.py
mkdir settingsgui
mv * settingsgui
mv settingsgui/settingsgui.py ./

* run:
export DISPLAY=:0.0
python settingsgui.py &

=== Comment on Installation ===

From Version 0.7 Python distutils is used. So you could also use the setup.py script to install the package:
python settingsgui-x.x/setup.py install

For Version 0.8beta (I didn't test for 0.7), don't change any names, just unpack and then:
cd settingsgui-x.x
python setup.py install

But to do this you'll also have to install the packages:
python-compile python-devel python-stringold python-distutils

==References==
* [http://www.mput.de/projects/code/settingsgui/ Project Homepage]

[[Category:Applications]]
[[Category:Openmoko]]
[[Category:Guides]]

Building FSO

2008-07-28T12:55:46Z

Kriss: /* GTK */ - set icon theme

'''FSO is an abbreviation for FreeSmartphone.Org'''

See [[OpenmokoFramework]] for more information.

And [http://www.freesmartphone.org www.freesmartphone.org]

And also [http://trac.freesmartphone.org trac.freesmartphone.org]

''Note : The following is an essay in order to explain how to build FSO. Please mind the fact that it's a work in progress, done by someone fairly new to Open Embedded.''

''This information is taken as is from [http://wiki.openembedded.net/index.php/OEandYourDistro#Using_OpenEmbedded_on_Linux_systems OpenEmbedded Wiki]. Some commentaries are voluntarily stripped in order to keep this page simple, please look on OE Wiki for more information.''

= Getting Open Embedded =

== Mandatory Packages ==

=== Deb-based distributions ===

<pre><nowiki>
apt-get install ccache sed wget cvs subversion git-core monotone coreutils \
unzip texi2html texinfo libsdl1.2-dev docbook-utils gawk
</nowiki></pre>

=== rpm-based distributions ===

<pre><nowiki>
urpmi python python-devel python-psyco ccache patch m4 sed bison make wget bzip2 \
cvs gawk glibc-devel gcc-c++ subversion sharutils coreutils docbook-utils openjade \
quilt pcre-devel unzip
</nowiki></pre>

=== SuSE (9.1/9.2) instructions ===
Install [http://linux01.gwdg.de/apt4rpm/ apt4rpm], then follow Debian instructions.

python-dev and python-spyco are not in suse apt repository. python-spyco is not mandatory, so one can ignore it.
I suppose python-devel (suse) is python-dev (debian).

=== Fedora Core 2/3 ===

<pre><nowiki> yum install python patch m4 sed make docbook* openjade glibc-devel xmlto</nowiki></pre>

=== Fedora Core 4 ===

Apart from the usual (native) development packages like gcc and binutils, you should check that you have the following RPM's installed:

* bison
* ccache (not required, but advised to speed up building)
* docbook* packages
* libpcre
* m4
* make
* openjade
* patch
* PyQt
* python
* python-psyco
* sed
* xmlto
* quilt (not required as OE builds it by itself, but install it if you want to use gquilt)

Use apt, synaptic, up2date or yum to automagically retrieve these packages or download and install them manually (lots of work).

=== Fedora Core 5/6 ===

Commands I used to install OE pre-requisites on FC5/6

This long command will ensure all pre-requisites are installed (patch is 2.5.4, not 2.5.9, but appears to work).

<pre><nowiki>
su -c "yum install python m4 make wget curl ftp cvs monotone subversion tar bzip2 gzip unzip python-psyco ccache perl texinfo texi2html diffstat openjade docbook-style-dsssl docbook-style-xsl docbook-dtds docbook-utils sed bison bc glibc-devel gcc binutils pcre pcre-devel git quilt groff linuxdoc-tools patch gcc gcc-c++ python-sqlite2 help2man"
</nowiki></pre>

or download the metapackage http://www.openembedded.org/dl/packages/rpm/openembedded-essential-1.1-1.noarch.rpm (may be out of date).

then do

<pre><nowiki>
su -c "yum localinstall openembedded-essential-1.1-1.noarch.rpm"
</nowiki></pre>

=== Fedora 7 ===

This long command will ensure all pre-requisites are installed (patch is 2.5.4, not 2.5.9, but appears to work).

<pre><nowiki>
su -c "yum install python m4 make wget curl ftp cvs monotone subversion tar bzip2 gzip unzip python-psyco ccache perl texinfo texi2html diffstat openjade docbook-style-dsssl docbook-style-xsl docbook-dtds docbook-utils sed bison bc glibc-devel gcc binutils pcre pcre-devel git quilt groff linuxdoc-tools patch linuxdoc-tools gcc gcc-c++ help2man"
</nowiki></pre>

=== CentOS 4.4 / Red Hat Enterprise Linux 4 ===

<pre><nowiki>
# yum install bison ccache coreutils cvs docbook-utils gawk git-core monotone \
python quilt rpmlib sed subversion tetex texinfo unzip wget
</nowiki></pre>

=== Gentoo instructions ===

<pre><nowiki>
emerge -n bitbake psyco ccache patch make sed dev-lang/python m4 bison cvs openjade quilt sgmltools-lite docbook-xml-dtd docbook-dsssl-stylesheets xmlto docbook-sgml-utils libpcre boost subversion monotone texi2html pysqlite diffstat
</nowiki></pre>

=== Ark Linux 2007.1 ===

<pre><nowiki>
apt-get install devel-core diffstat texi2html cvs subversion git texinfo psyco monotone python-devel python-encodings python-sqlite
</nowiki></pre>

=== Arch Linux (Duke) ===

<pre><nowiki>
sudo pacman -S psyco ccache patch make sed python m4 bison cvs quilt sgmltools-lite docbook-xml xmlto pcre boost monotone jade git texinfo
</nowiki></pre>

In Arch Linux the install command is in /bin/install. Since most of Linux distribution assume that install is located in /usr/bin/install, you have to create a symlink:

<pre><nowiki>
sudo ln -s /bin/install /usr/bin/install
</nowiki></pre>

You can build BitBake by using this PKGBUILD:
<pre><nowiki>
pkgname=bitbake
pkgver=1.8.4
pkgrel=1
pkgdesc="A simple tool for task execution derived from Gentoo's portage"
url="http://developer.berlios.de/projects/bitbake/"
arch=('i686')
license=('GPL' 'custom')
depends=('python')
source=(http://download.berlios.de/bitbake/${pkgname}-${pkgver}.tar.gz)
md5sums=('508d9a61c635d469be8facc95151158b')

build() {
cd ${startdir}/src/${pkgname}-${pkgver}
python setup.py install --root=${startdir}/pkg

# Install vim extensions
install -D -m644 ${startdir}/src/${pkgname}-${pkgver}/contrib/vim/ftdetect/bitbake.vim \
${startdir}/pkg/usr/share/vim/ftplugin/bitbake.vim
install -D -m644 ${startdir}/src/${pkgname}-${pkgver}/contrib/vim/syntax/bitbake.vim \
${startdir}/pkg/usr/share/vim/syntax/bitbake.vim

# Handle MIT license
install -D -m644 ${startdir}/src/${pkgname}-${pkgver}/doc/COPYING.MIT \
${startdir}/pkg/usr/share/licenses/${pkgname}/COPYING.MIT
}
</nowiki></pre>

= Repository Checkout =

== Bitbake ==

Go to the base directory of your [[OpenEmbedded]] environment and checkout bitbake:
<pre><nowiki>
$ cd /stuff/
$ svn co svn://svn.berlios.de/bitbake/branches/bitbake-1.8/ bitbake</nowiki></pre>
'''NOTE:''' for proxy handling, see [http://subversion.tigris.org/faq.html#proxy SVN FAQ]

== Open Embedded ==

=== Obtaining OpenEmbedded ===
Next, you'll need to obtain the actual Openembedded database. The OE database store all the OE metadata: build classes, configuration files, and packages. Then you can extract from this database the development branch(es) you want.

The Openembedded database is a [http://www.venge.net/monotone/ Monotone] database, which is the current SCM (Source Code Management) system for Openembedded. You can find monotone binaries and documentation at [http://www.venge.net/monotone/ Monotone official site].

To obtain Openembedded:
# Go to the base directory of your Openembedded environment
$ cd /stuff/
# Download and bunzip2 the OE database snapshot. '''Note: Unfortunately some monotone versions differ in database format. Check [http://www.openembedded.org/snapshots Snapshots] and download the one matching your monotone version.'''
$ wget http://www.openembedded.org/snapshots/OE.mtn.bz2
$ bunzip2 -d OE.mtn.bz2
This is the database you'll be using for all the work.

If you run into a problem at this stage, check to make sure you have version 0.32 (or newer) of monotone installed.

If you get further troubles in using monotone, there are two ways out:

* use the [http://openembedded.org/snapshots/ latest OE snapshot]
* use a static monotone image

Then you can checkout your local copy of the Openembedded tree.
$ cd /stuff
$ mtn --db=/stuff/OE.mtn checkout --branch=org.openembedded.dev
This extracts directories and files relating to the selected branch from the OE.mtn database and places them under <nowiki>/stuff/branchname</nowiki> (i.e. in <nowiki>/stuff/org.openembedded.dev</nowiki> in this guide)

IMPORTANT NOTE ! If mtn complains about an outdated database, you can migrate it using the following command :

<pre><nowiki>
mtn db migrate --db=/stuff/OE.mtn
</nowiki></pre>

You'll then have to do the checkout.
=== Create local configuration ===
It's now time to create your local configuration.
While you could copy the default local.conf.sample like that:

<pre><nowiki>
$ cd /stuff/
$ cp org.openembedded.dev/conf/local.conf.sample build/conf/local.conf
$ vi build/conf/local.conf
</nowiki></pre>

It is actually recommended to start smaller and keep local.conf.sample in the background and add entries from there step-by-step as you understand and need them. Please, do not just edit build/conf/local.conf.sample but actually READ it.

For building a .dev branch, in your <nowiki>local.conf</nowiki> file, you should have at least the following three entries. Example for the Angstrom distribution and the Openmoko gta01 machine:
<pre><nowiki>
BBFILES = "/stuff/org.openembedded.dev/packages/*/*.bb"
DISTRO = "angstrom-2008.1"
MACHINE = "om-gta01"
</nowiki></pre>

For a Freerunner, using an openmoko distro, you'll do that :

<pre><nowiki>
BBFILES = "/stuff/org.openembedded.dev/packages/*/*.bb"
DISTRO = "openmoko"
MACHINE = "om-gta02"
</nowiki></pre>

Don't forget to include the two following files :

<pre><nowiki>
require conf/distro/include/fso-autorev.inc
require conf/distro/include/moko-autorev.inc
</nowiki></pre>

=== Setup the environment ===
One of the four command sets below will need to be run every time you open a terminal for development. (You can automate this in ~/.profile, /etc/profile, or perhaps use a script to set the necessary variables for using [[BitBake]].)

If you followed the recommendation above to use an uninstalled [[BitBake]]:
<pre><nowiki>
$ export PATH=/stuff/bitbake/bin:$PATH
$ export BBPATH=/stuff/build:/stuff/org.openembedded.dev
</nowiki></pre>

If you installed [[BitBake]]:
<pre><nowiki>
$ export BBPATH=/stuff/build:/stuff/org.openembedded.dev
</nowiki></pre>

Alternative syntax for those using the tcsh shell (e.g FreeBSD):
<pre><nowiki>
$ setenv PATH "/stuff/bitbake/bin:"$PATH
$ setenv BBPATH "/stuff/build:/stuff/org.openembedded.dev:"$BBPATH
</nowiki></pre>

= Start building =

<pre><nowiki>
cd /stuff/build && bitbake fso-image
</nowiki></pre>
[[category:Technical]]
[[Category:Software (non openmoko)]]
[[category:FSO]]

= Configuration =

== GTK ==

Currently GTK is not well supported in the FSO build. To use GTK applications you'll most likely have to install the gtk library, and the Openmoko theme.

'''Step 1) Install the ipk-packages'''

opkg install moko-gtk-theme
opkg install openmoko-icon-theme-standard2

'''Step 2) Enable Theme'''

ln -s /usr/share/themes/Moko/gtk-2.0/gtkrc /etc/gtk-2.0/gtkrc

'''Step 3) Adjust fontsize and set icon theme'''

vi /etc/gtk-2.0/gtkrc

Add the two lines:
gtk-font-name = "Sans 5"
gtk-icon-theme-name="openmoko-standard"

(Thanks to [[User:Jtickle | Jtickle]] for pointing out how to set the font size on the [[Getting_Started_FAQ]]-Page)

Building FSO

2008-07-28T12:47:51Z

Kriss: /* Configuration */ - layout, gtkfontsize++

'''FSO is an abbreviation for FreeSmartphone.Org'''

See [[OpenmokoFramework]] for more information.

And [http://www.freesmartphone.org www.freesmartphone.org]

And also [http://trac.freesmartphone.org trac.freesmartphone.org]

''Note : The following is an essay in order to explain how to build FSO. Please mind the fact that it's a work in progress, done by someone fairly new to Open Embedded.''

''This information is taken as is from [http://wiki.openembedded.net/index.php/OEandYourDistro#Using_OpenEmbedded_on_Linux_systems OpenEmbedded Wiki]. Some commentaries are voluntarily stripped in order to keep this page simple, please look on OE Wiki for more information.''

= Getting Open Embedded =

== Mandatory Packages ==

=== Deb-based distributions ===

<pre><nowiki>
apt-get install ccache sed wget cvs subversion git-core monotone coreutils \
unzip texi2html texinfo libsdl1.2-dev docbook-utils gawk
</nowiki></pre>

=== rpm-based distributions ===

<pre><nowiki>
urpmi python python-devel python-psyco ccache patch m4 sed bison make wget bzip2 \
cvs gawk glibc-devel gcc-c++ subversion sharutils coreutils docbook-utils openjade \
quilt pcre-devel unzip
</nowiki></pre>

=== SuSE (9.1/9.2) instructions ===
Install [http://linux01.gwdg.de/apt4rpm/ apt4rpm], then follow Debian instructions.

python-dev and python-spyco are not in suse apt repository. python-spyco is not mandatory, so one can ignore it.
I suppose python-devel (suse) is python-dev (debian).

=== Fedora Core 2/3 ===

<pre><nowiki> yum install python patch m4 sed make docbook* openjade glibc-devel xmlto</nowiki></pre>

=== Fedora Core 4 ===

Apart from the usual (native) development packages like gcc and binutils, you should check that you have the following RPM's installed:

* bison
* ccache (not required, but advised to speed up building)
* docbook* packages
* libpcre
* m4
* make
* openjade
* patch
* PyQt
* python
* python-psyco
* sed
* xmlto
* quilt (not required as OE builds it by itself, but install it if you want to use gquilt)

Use apt, synaptic, up2date or yum to automagically retrieve these packages or download and install them manually (lots of work).

=== Fedora Core 5/6 ===

Commands I used to install OE pre-requisites on FC5/6

This long command will ensure all pre-requisites are installed (patch is 2.5.4, not 2.5.9, but appears to work).

<pre><nowiki>
su -c "yum install python m4 make wget curl ftp cvs monotone subversion tar bzip2 gzip unzip python-psyco ccache perl texinfo texi2html diffstat openjade docbook-style-dsssl docbook-style-xsl docbook-dtds docbook-utils sed bison bc glibc-devel gcc binutils pcre pcre-devel git quilt groff linuxdoc-tools patch gcc gcc-c++ python-sqlite2 help2man"
</nowiki></pre>

or download the metapackage http://www.openembedded.org/dl/packages/rpm/openembedded-essential-1.1-1.noarch.rpm (may be out of date).

then do

<pre><nowiki>
su -c "yum localinstall openembedded-essential-1.1-1.noarch.rpm"
</nowiki></pre>

=== Fedora 7 ===

This long command will ensure all pre-requisites are installed (patch is 2.5.4, not 2.5.9, but appears to work).

<pre><nowiki>
su -c "yum install python m4 make wget curl ftp cvs monotone subversion tar bzip2 gzip unzip python-psyco ccache perl texinfo texi2html diffstat openjade docbook-style-dsssl docbook-style-xsl docbook-dtds docbook-utils sed bison bc glibc-devel gcc binutils pcre pcre-devel git quilt groff linuxdoc-tools patch linuxdoc-tools gcc gcc-c++ help2man"
</nowiki></pre>

=== CentOS 4.4 / Red Hat Enterprise Linux 4 ===

<pre><nowiki>
# yum install bison ccache coreutils cvs docbook-utils gawk git-core monotone \
python quilt rpmlib sed subversion tetex texinfo unzip wget
</nowiki></pre>

=== Gentoo instructions ===

<pre><nowiki>
emerge -n bitbake psyco ccache patch make sed dev-lang/python m4 bison cvs openjade quilt sgmltools-lite docbook-xml-dtd docbook-dsssl-stylesheets xmlto docbook-sgml-utils libpcre boost subversion monotone texi2html pysqlite diffstat
</nowiki></pre>

=== Ark Linux 2007.1 ===

<pre><nowiki>
apt-get install devel-core diffstat texi2html cvs subversion git texinfo psyco monotone python-devel python-encodings python-sqlite
</nowiki></pre>

=== Arch Linux (Duke) ===

<pre><nowiki>
sudo pacman -S psyco ccache patch make sed python m4 bison cvs quilt sgmltools-lite docbook-xml xmlto pcre boost monotone jade git texinfo
</nowiki></pre>

In Arch Linux the install command is in /bin/install. Since most of Linux distribution assume that install is located in /usr/bin/install, you have to create a symlink:

<pre><nowiki>
sudo ln -s /bin/install /usr/bin/install
</nowiki></pre>

You can build BitBake by using this PKGBUILD:
<pre><nowiki>
pkgname=bitbake
pkgver=1.8.4
pkgrel=1
pkgdesc="A simple tool for task execution derived from Gentoo's portage"
url="http://developer.berlios.de/projects/bitbake/"
arch=('i686')
license=('GPL' 'custom')
depends=('python')
source=(http://download.berlios.de/bitbake/${pkgname}-${pkgver}.tar.gz)
md5sums=('508d9a61c635d469be8facc95151158b')

build() {
cd ${startdir}/src/${pkgname}-${pkgver}
python setup.py install --root=${startdir}/pkg

# Install vim extensions
install -D -m644 ${startdir}/src/${pkgname}-${pkgver}/contrib/vim/ftdetect/bitbake.vim \
${startdir}/pkg/usr/share/vim/ftplugin/bitbake.vim
install -D -m644 ${startdir}/src/${pkgname}-${pkgver}/contrib/vim/syntax/bitbake.vim \
${startdir}/pkg/usr/share/vim/syntax/bitbake.vim

# Handle MIT license
install -D -m644 ${startdir}/src/${pkgname}-${pkgver}/doc/COPYING.MIT \
${startdir}/pkg/usr/share/licenses/${pkgname}/COPYING.MIT
}
</nowiki></pre>

= Repository Checkout =

== Bitbake ==

Go to the base directory of your [[OpenEmbedded]] environment and checkout bitbake:
<pre><nowiki>
$ cd /stuff/
$ svn co svn://svn.berlios.de/bitbake/branches/bitbake-1.8/ bitbake</nowiki></pre>
'''NOTE:''' for proxy handling, see [http://subversion.tigris.org/faq.html#proxy SVN FAQ]

== Open Embedded ==

=== Obtaining OpenEmbedded ===
Next, you'll need to obtain the actual Openembedded database. The OE database store all the OE metadata: build classes, configuration files, and packages. Then you can extract from this database the development branch(es) you want.

The Openembedded database is a [http://www.venge.net/monotone/ Monotone] database, which is the current SCM (Source Code Management) system for Openembedded. You can find monotone binaries and documentation at [http://www.venge.net/monotone/ Monotone official site].

To obtain Openembedded:
# Go to the base directory of your Openembedded environment
$ cd /stuff/
# Download and bunzip2 the OE database snapshot. '''Note: Unfortunately some monotone versions differ in database format. Check [http://www.openembedded.org/snapshots Snapshots] and download the one matching your monotone version.'''
$ wget http://www.openembedded.org/snapshots/OE.mtn.bz2
$ bunzip2 -d OE.mtn.bz2
This is the database you'll be using for all the work.

If you run into a problem at this stage, check to make sure you have version 0.32 (or newer) of monotone installed.

If you get further troubles in using monotone, there are two ways out:

* use the [http://openembedded.org/snapshots/ latest OE snapshot]
* use a static monotone image

Then you can checkout your local copy of the Openembedded tree.
$ cd /stuff
$ mtn --db=/stuff/OE.mtn checkout --branch=org.openembedded.dev
This extracts directories and files relating to the selected branch from the OE.mtn database and places them under <nowiki>/stuff/branchname</nowiki> (i.e. in <nowiki>/stuff/org.openembedded.dev</nowiki> in this guide)

IMPORTANT NOTE ! If mtn complains about an outdated database, you can migrate it using the following command :

<pre><nowiki>
mtn db migrate --db=/stuff/OE.mtn
</nowiki></pre>

You'll then have to do the checkout.
=== Create local configuration ===
It's now time to create your local configuration.
While you could copy the default local.conf.sample like that:

<pre><nowiki>
$ cd /stuff/
$ cp org.openembedded.dev/conf/local.conf.sample build/conf/local.conf
$ vi build/conf/local.conf
</nowiki></pre>

It is actually recommended to start smaller and keep local.conf.sample in the background and add entries from there step-by-step as you understand and need them. Please, do not just edit build/conf/local.conf.sample but actually READ it.

For building a .dev branch, in your <nowiki>local.conf</nowiki> file, you should have at least the following three entries. Example for the Angstrom distribution and the Openmoko gta01 machine:
<pre><nowiki>
BBFILES = "/stuff/org.openembedded.dev/packages/*/*.bb"
DISTRO = "angstrom-2008.1"
MACHINE = "om-gta01"
</nowiki></pre>

For a Freerunner, using an openmoko distro, you'll do that :

<pre><nowiki>
BBFILES = "/stuff/org.openembedded.dev/packages/*/*.bb"
DISTRO = "openmoko"
MACHINE = "om-gta02"
</nowiki></pre>

Don't forget to include the two following files :

<pre><nowiki>
require conf/distro/include/fso-autorev.inc
require conf/distro/include/moko-autorev.inc
</nowiki></pre>

=== Setup the environment ===
One of the four command sets below will need to be run every time you open a terminal for development. (You can automate this in ~/.profile, /etc/profile, or perhaps use a script to set the necessary variables for using [[BitBake]].)

If you followed the recommendation above to use an uninstalled [[BitBake]]:
<pre><nowiki>
$ export PATH=/stuff/bitbake/bin:$PATH
$ export BBPATH=/stuff/build:/stuff/org.openembedded.dev
</nowiki></pre>

If you installed [[BitBake]]:
<pre><nowiki>
$ export BBPATH=/stuff/build:/stuff/org.openembedded.dev
</nowiki></pre>

Alternative syntax for those using the tcsh shell (e.g FreeBSD):
<pre><nowiki>
$ setenv PATH "/stuff/bitbake/bin:"$PATH
$ setenv BBPATH "/stuff/build:/stuff/org.openembedded.dev:"$BBPATH
</nowiki></pre>

= Start building =

<pre><nowiki>
cd /stuff/build && bitbake fso-image
</nowiki></pre>
[[category:Technical]]
[[Category:Software (non openmoko)]]
[[category:FSO]]

= Configuration =

== GTK ==

Currently GTK is not well supported in the FSO build. To use GTK applications you'll most likely hae to install the gtk library, and the Openmoko theme.

'''Step 1) Install the ipk-packages'''

opkg install moko-gtk-theme
opkg install openmoko-icon-theme-standard2

'''Step 2) Enable Theme'''

ln -s /usr/share/themes/Moko/gtk-2.0/gtkrc /etc/gtk-2.0/gtkrc

'''Step 3) Adjust the fontsize'''

vi /etc/gtk-2.0/gtkrc

Add the Line:
gtk-font-name = "Sans 5"

(Thanks to [[User:Jtickle | Jtickle]] for pointing that out on the [[Getting_Started_FAQ]]-Page)

'''Step 4) Enable the Icon Theme'''

ToDo --[[User:Kriss|kriss]] 12:46, 28 July 2008 (UTC)

Building FSO

2008-07-28T12:46:20Z

Kriss: Install and use GTK with FSO

'''FSO is an abbreviation for FreeSmartphone.Org'''

See [[OpenmokoFramework]] for more information.

And [http://www.freesmartphone.org www.freesmartphone.org]

And also [http://trac.freesmartphone.org trac.freesmartphone.org]

''Note : The following is an essay in order to explain how to build FSO. Please mind the fact that it's a work in progress, done by someone fairly new to Open Embedded.''

''This information is taken as is from [http://wiki.openembedded.net/index.php/OEandYourDistro#Using_OpenEmbedded_on_Linux_systems OpenEmbedded Wiki]. Some commentaries are voluntarily stripped in order to keep this page simple, please look on OE Wiki for more information.''

= Getting Open Embedded =

== Mandatory Packages ==

=== Deb-based distributions ===

<pre><nowiki>
apt-get install ccache sed wget cvs subversion git-core monotone coreutils \
unzip texi2html texinfo libsdl1.2-dev docbook-utils gawk
</nowiki></pre>

=== rpm-based distributions ===

<pre><nowiki>
urpmi python python-devel python-psyco ccache patch m4 sed bison make wget bzip2 \
cvs gawk glibc-devel gcc-c++ subversion sharutils coreutils docbook-utils openjade \
quilt pcre-devel unzip
</nowiki></pre>

=== SuSE (9.1/9.2) instructions ===
Install [http://linux01.gwdg.de/apt4rpm/ apt4rpm], then follow Debian instructions.

python-dev and python-spyco are not in suse apt repository. python-spyco is not mandatory, so one can ignore it.
I suppose python-devel (suse) is python-dev (debian).

=== Fedora Core 2/3 ===

<pre><nowiki> yum install python patch m4 sed make docbook* openjade glibc-devel xmlto</nowiki></pre>

=== Fedora Core 4 ===

Apart from the usual (native) development packages like gcc and binutils, you should check that you have the following RPM's installed:

* bison
* ccache (not required, but advised to speed up building)
* docbook* packages
* libpcre
* m4
* make
* openjade
* patch
* PyQt
* python
* python-psyco
* sed
* xmlto
* quilt (not required as OE builds it by itself, but install it if you want to use gquilt)

Use apt, synaptic, up2date or yum to automagically retrieve these packages or download and install them manually (lots of work).

=== Fedora Core 5/6 ===

Commands I used to install OE pre-requisites on FC5/6

This long command will ensure all pre-requisites are installed (patch is 2.5.4, not 2.5.9, but appears to work).

<pre><nowiki>
su -c "yum install python m4 make wget curl ftp cvs monotone subversion tar bzip2 gzip unzip python-psyco ccache perl texinfo texi2html diffstat openjade docbook-style-dsssl docbook-style-xsl docbook-dtds docbook-utils sed bison bc glibc-devel gcc binutils pcre pcre-devel git quilt groff linuxdoc-tools patch gcc gcc-c++ python-sqlite2 help2man"
</nowiki></pre>

or download the metapackage http://www.openembedded.org/dl/packages/rpm/openembedded-essential-1.1-1.noarch.rpm (may be out of date).

then do

<pre><nowiki>
su -c "yum localinstall openembedded-essential-1.1-1.noarch.rpm"
</nowiki></pre>

=== Fedora 7 ===

This long command will ensure all pre-requisites are installed (patch is 2.5.4, not 2.5.9, but appears to work).

<pre><nowiki>
su -c "yum install python m4 make wget curl ftp cvs monotone subversion tar bzip2 gzip unzip python-psyco ccache perl texinfo texi2html diffstat openjade docbook-style-dsssl docbook-style-xsl docbook-dtds docbook-utils sed bison bc glibc-devel gcc binutils pcre pcre-devel git quilt groff linuxdoc-tools patch linuxdoc-tools gcc gcc-c++ help2man"
</nowiki></pre>

=== CentOS 4.4 / Red Hat Enterprise Linux 4 ===

<pre><nowiki>
# yum install bison ccache coreutils cvs docbook-utils gawk git-core monotone \
python quilt rpmlib sed subversion tetex texinfo unzip wget
</nowiki></pre>

=== Gentoo instructions ===

<pre><nowiki>
emerge -n bitbake psyco ccache patch make sed dev-lang/python m4 bison cvs openjade quilt sgmltools-lite docbook-xml-dtd docbook-dsssl-stylesheets xmlto docbook-sgml-utils libpcre boost subversion monotone texi2html pysqlite diffstat
</nowiki></pre>

=== Ark Linux 2007.1 ===

<pre><nowiki>
apt-get install devel-core diffstat texi2html cvs subversion git texinfo psyco monotone python-devel python-encodings python-sqlite
</nowiki></pre>

=== Arch Linux (Duke) ===

<pre><nowiki>
sudo pacman -S psyco ccache patch make sed python m4 bison cvs quilt sgmltools-lite docbook-xml xmlto pcre boost monotone jade git texinfo
</nowiki></pre>

In Arch Linux the install command is in /bin/install. Since most of Linux distribution assume that install is located in /usr/bin/install, you have to create a symlink:

<pre><nowiki>
sudo ln -s /bin/install /usr/bin/install
</nowiki></pre>

You can build BitBake by using this PKGBUILD:
<pre><nowiki>
pkgname=bitbake
pkgver=1.8.4
pkgrel=1
pkgdesc="A simple tool for task execution derived from Gentoo's portage"
url="http://developer.berlios.de/projects/bitbake/"
arch=('i686')
license=('GPL' 'custom')
depends=('python')
source=(http://download.berlios.de/bitbake/${pkgname}-${pkgver}.tar.gz)
md5sums=('508d9a61c635d469be8facc95151158b')

build() {
cd ${startdir}/src/${pkgname}-${pkgver}
python setup.py install --root=${startdir}/pkg

# Install vim extensions
install -D -m644 ${startdir}/src/${pkgname}-${pkgver}/contrib/vim/ftdetect/bitbake.vim \
${startdir}/pkg/usr/share/vim/ftplugin/bitbake.vim
install -D -m644 ${startdir}/src/${pkgname}-${pkgver}/contrib/vim/syntax/bitbake.vim \
${startdir}/pkg/usr/share/vim/syntax/bitbake.vim

# Handle MIT license
install -D -m644 ${startdir}/src/${pkgname}-${pkgver}/doc/COPYING.MIT \
${startdir}/pkg/usr/share/licenses/${pkgname}/COPYING.MIT
}
</nowiki></pre>

= Repository Checkout =

== Bitbake ==

Go to the base directory of your [[OpenEmbedded]] environment and checkout bitbake:
<pre><nowiki>
$ cd /stuff/
$ svn co svn://svn.berlios.de/bitbake/branches/bitbake-1.8/ bitbake</nowiki></pre>
'''NOTE:''' for proxy handling, see [http://subversion.tigris.org/faq.html#proxy SVN FAQ]

== Open Embedded ==

=== Obtaining OpenEmbedded ===
Next, you'll need to obtain the actual Openembedded database. The OE database store all the OE metadata: build classes, configuration files, and packages. Then you can extract from this database the development branch(es) you want.

The Openembedded database is a [http://www.venge.net/monotone/ Monotone] database, which is the current SCM (Source Code Management) system for Openembedded. You can find monotone binaries and documentation at [http://www.venge.net/monotone/ Monotone official site].

To obtain Openembedded:
# Go to the base directory of your Openembedded environment
$ cd /stuff/
# Download and bunzip2 the OE database snapshot. '''Note: Unfortunately some monotone versions differ in database format. Check [http://www.openembedded.org/snapshots Snapshots] and download the one matching your monotone version.'''
$ wget http://www.openembedded.org/snapshots/OE.mtn.bz2
$ bunzip2 -d OE.mtn.bz2
This is the database you'll be using for all the work.

If you run into a problem at this stage, check to make sure you have version 0.32 (or newer) of monotone installed.

If you get further troubles in using monotone, there are two ways out:

* use the [http://openembedded.org/snapshots/ latest OE snapshot]
* use a static monotone image

Then you can checkout your local copy of the Openembedded tree.
$ cd /stuff
$ mtn --db=/stuff/OE.mtn checkout --branch=org.openembedded.dev
This extracts directories and files relating to the selected branch from the OE.mtn database and places them under <nowiki>/stuff/branchname</nowiki> (i.e. in <nowiki>/stuff/org.openembedded.dev</nowiki> in this guide)

IMPORTANT NOTE ! If mtn complains about an outdated database, you can migrate it using the following command :

<pre><nowiki>
mtn db migrate --db=/stuff/OE.mtn
</nowiki></pre>

You'll then have to do the checkout.
=== Create local configuration ===
It's now time to create your local configuration.
While you could copy the default local.conf.sample like that:

<pre><nowiki>
$ cd /stuff/
$ cp org.openembedded.dev/conf/local.conf.sample build/conf/local.conf
$ vi build/conf/local.conf
</nowiki></pre>

It is actually recommended to start smaller and keep local.conf.sample in the background and add entries from there step-by-step as you understand and need them. Please, do not just edit build/conf/local.conf.sample but actually READ it.

For building a .dev branch, in your <nowiki>local.conf</nowiki> file, you should have at least the following three entries. Example for the Angstrom distribution and the Openmoko gta01 machine:
<pre><nowiki>
BBFILES = "/stuff/org.openembedded.dev/packages/*/*.bb"
DISTRO = "angstrom-2008.1"
MACHINE = "om-gta01"
</nowiki></pre>

For a Freerunner, using an openmoko distro, you'll do that :

<pre><nowiki>
BBFILES = "/stuff/org.openembedded.dev/packages/*/*.bb"
DISTRO = "openmoko"
MACHINE = "om-gta02"
</nowiki></pre>

Don't forget to include the two following files :

<pre><nowiki>
require conf/distro/include/fso-autorev.inc
require conf/distro/include/moko-autorev.inc
</nowiki></pre>

=== Setup the environment ===
One of the four command sets below will need to be run every time you open a terminal for development. (You can automate this in ~/.profile, /etc/profile, or perhaps use a script to set the necessary variables for using [[BitBake]].)

If you followed the recommendation above to use an uninstalled [[BitBake]]:
<pre><nowiki>
$ export PATH=/stuff/bitbake/bin:$PATH
$ export BBPATH=/stuff/build:/stuff/org.openembedded.dev
</nowiki></pre>

If you installed [[BitBake]]:
<pre><nowiki>
$ export BBPATH=/stuff/build:/stuff/org.openembedded.dev
</nowiki></pre>

Alternative syntax for those using the tcsh shell (e.g FreeBSD):
<pre><nowiki>
$ setenv PATH "/stuff/bitbake/bin:"$PATH
$ setenv BBPATH "/stuff/build:/stuff/org.openembedded.dev:"$BBPATH
</nowiki></pre>

= Start building =

<pre><nowiki>
cd /stuff/build && bitbake fso-image
</nowiki></pre>
[[category:Technical]]
[[Category:Software (non openmoko)]]
[[category:FSO]]

= Configuration =

== GTK ==

Currently GTK is not well supported in the FSO build. To use GTK applications you'll most likely hae to install the gtk library, and the Openmoko theme.

=== GTK Theme ===

==== Step 1) Install the ipk-packages ====

opkg install moko-gtk-theme
opkg install openmoko-icon-theme-standard2

==== Step 2) Enable Theme ====

ln -s /usr/share/themes/Moko/gtk-2.0/gtkrc /etc/gtk-2.0/gtkrc

==== Step 3) Adjust the fontsize ====

vi /etc/gtk-2.0/gtkrc

Add the Line:
gtk-font-name = "Sans 4"

(Thanks to [[User:Jtickle | Jtickle]] for pointing that out on the [[Getting_Started_FAQ]]-Page)

==== Step 4) Enable the Icon Theme ====

ToDo --[[User:Kriss|kriss]] 12:46, 28 July 2008 (UTC)

Talk:Openmoko Local Groups: Berlin

2008-07-23T19:13:56Z

Kriss: /* Naechstes c-base-Treffen */

== Naechstes c-base-Treffen ==

<center>

'''23.07.2008 in der c-base'''

{| border=1
!Wer
!Wahrscheinlichkeit
!Neo1973
!Freerunner
|-
|[[User:Kriss|kriss]]
|05%
|1-2
|1
|-
|[[User:philippt|philippt]]
|
|0
|0
|-
|[[User:Sbusch|sbusch]]
|
|0
|0
|-
|[[User:Roh|roh]]
|ziemlich
|1
|1
|-
|[[User:Ejokisch|Eckhard]]
|sehr
|0
|0
|}

</center>

== Sammelbestellung ==
Ich werde 10 Geräte bestellen und auch das Administrative übernehmen. Das Angebot bei Pulster zu 299,- inkl. Goodies finde ich voll in Ordnung.
Wer will einen Freerunner?

--[[User:Ejokisch|Ejokisch]] 17:22, 13 July 2008 (UTC)

soweit ich weiß, sind bei pulster.de keine Goodies bei. --[[User:govindas|govindas]] 18:31, 22 Juli 2008 (UTC)

wer die Idee mit der Sammelbestellung noch nicht aufgegeben hat:

"Die Münchner Firma [http://www.handheld-linux.com/wiki.php?page=Neo%20Freerunner Goldelico] bietet Freerunner an. Die Goodies aus dem 10-Pack sind mit dabei und es gibt auch Gruppenrabatt. 1-4 Freerunner - 349 Euro 5-9 Freerunner - 332 Euro 10+ Freerunner - 314 Euro
Whoever: Ich würde vorschlagen bei den Preisen die Auslandsbestellung zu vergessen, da wir damit max. 10 Euro pro Freerunner sparen können. Im Gegenzug fallen aber alle Risiken weg. Ich habe schon mit der Firma telefoniert. Bei einer 10er Bestellung läuft die Abwicklung auch über einen einzigen Besteller. Geld einsammeln und Freerunner verteilen wäre also weiterhin bei einer Person. "
auszug http://wiki.openmoko.org/wiki/Openmoko_Local_Groups:_Munich

also ab 10 leuten gibts freerunner + tasche + head set für 314€/person!
ist auf jeden fall besser als direkt in china zu kaufen und bis jetzt das billigste Angebot in Deutschland!(das mir bekannt ist) ;)

--[[User:govindas|govindas]] 20:18, 27 June 2008 (UTC)

Bei [http://www.pulster.de/ pulster.de] soll '''ein''' Stück 299,- € kosten. Nach einer Sammelbestellung habe ich noch garnicht gefragt. Die nächste Lieferung gibt es aber erst ab dem 25.7.2008. Ich weiß nicht, ob ich das noch so lange durchhalte.

--[[User:Ott--|Ott--]] 14:11, 2 July 2008 (UTC)

...gibt's eigentlich noch Leute, die an einer Sammelbestellung interessiert wären? 25.07. ist zwar noch ein bißchen hin, aber wahrscheinlich wär's ganz gut, jetzt trotzdem schon mal langsam zu ordern, damit das mit der Lieferung dann auch klappt.

--[[User:philippt|philippt]] 01:45, 09 July 2008 (UTC +1 oder 2 ;-) )

Hallo alle zusammen,
ich bin zwar nicht in der Gruppe, aber ebenfalls aus Berlin und ich würde noch zwei Freerunner mitbestellen wollen, wenn das jetzt noch geht!
Vielleicht kriegen wir das Boot voll!
Das wäre schön.

--[[User:VanInwagen|vanInwagen]] 15:16, 22 July 2008 (UTC)

----

== Vorschlag Neuer Treffpunkt ==

hi.

ich schlage vor sich einfach am mittwoch abends in der c-base http://c-base.org/ zu treffen. zeitgleich mit den freifunkern. embedded linux und wifi devices bietet genauso wie eine bar mit bier und genug platz denke ich das passende ambiente.

--[[User:Roh|Roh]] 23:58, 26 June 2008 (UTC)

bin auch dafür --[[User:Torsten Grote|Torsten Grote]] 10:57, 27 June 2008 (UTC)

Jo, da wär ich auch dabei. Seh ich das richtig, daß einige von Euch schon stolze Besitzer sind?
--[[User:philippt|philippt]] 16:06, 27 June 2008 (UTC)

zwangslaeufig ;)
ich brings naechsten mittwoch einfach mal mit (mit fso milestone im nand)
--[[User:Roh|Roh]] 06:19, 2 July 2008 (UTC)
btw, das is heute.--[[User:Roh|Roh]] 06:27, 2 July 2008 (UTC)

grrr...heute klappt bei mir nicht, aber ich schreib mir mal nächsten Mittwoch in den Kalender meines mittlerweile verabscheuungswürdig primitiven Mobiltelefons. --[[User:philippt|philippt]] 19:00, 2 July 2008 (UTC)

hätte auch großes Interesse ... also ist heute Abend jemand dabei? Werde auf jeden Fall mal vorbeischauen. [[User:Sbusch|Sbusch]] 11:00, 9 July 2008 (UTC)

== Stammtisch eingeschlafen? ==

Hallo ihr,

wenn ich mir diese discussion Seite anschaue, scheint mir das ziemlich eingeschlafen zu sein.

Hätte den jemand Lust an irgendeinem hier erwähnten Ort einen Stammtisch mal abzuhalten und nach dem persönlichen Kennenlernen weitere Entwicklungen zu koordinieren?

----

== Stammtisch Berlin ==

Ich könnte mir einen Stammtisch vorstellen oder ein regelmäßiges Treffen.

Ich habe halt keine GTA01Bv4 und werd sie mir auch nicht kaufen können weil ich mir nur GTA02 oder GTA01Bv4 holen kann und die Wahl dann auf GTA02 fällt.... ;-)

Trotzdem würde ich gerne an der Entwicklung jetzt schon mitmachen, das fällt allerdings doch schwer ohne je einmal einen Neo in der Hand gehalten zu haben (Motivation...).

Zumal sich [[Bluetooth_powered_Multi-SIM_support|manche]] Sachen halt nur mit Gerät programmieren lassen...

Soweit ich informiert bin, war schon vor dem Developer launch in Berlin mindestens 2 Geräte vorhanden, bzw. eine kleine Entwicklervormacht.

Comments? --[[User:Minime|Minime]] 16:32, 13 July 2007 (CEST)

Talk:Openmoko Local Groups: Berlin

2008-07-23T17:24:14Z

Kriss: /* Naechstes c-base-Treffen */ - there is no user "free"

== Naechstes c-base-Treffen ==

<center>

'''23.07.2008 in der c-base'''

{| border=1
!Wer
!Wahrscheinlichkeit
!Neo1973
!Freerunner
|-
|[[User:Kriss|kriss]]
|20%
|1-2
|1
|-
|[[User:philippt|philippt]]
|
|0
|0
|-
|[[User:Sbusch|sbusch]]
|
|0
|0
|-
|[[User:Roh|roh]]
|ziemlich
|1
|1
|-
|[[User:Ejokisch|Eckhard]]
|sehr
|0
|0
|}

</center>

== Sammelbestellung ==
Ich werde 10 Geräte bestellen und auch das Administrative übernehmen. Das Angebot bei Pulster zu 299,- inkl. Goodies finde ich voll in Ordnung.
Wer will einen Freerunner?

--[[User:Ejokisch|Ejokisch]] 17:22, 13 July 2008 (UTC)

soweit ich weiß, sind bei pulster.de keine Goodies bei. --[[User:govindas|govindas]] 18:31, 22 Juli 2008 (UTC)

wer die Idee mit der Sammelbestellung noch nicht aufgegeben hat:

"Die Münchner Firma [http://www.handheld-linux.com/wiki.php?page=Neo%20Freerunner Goldelico] bietet Freerunner an. Die Goodies aus dem 10-Pack sind mit dabei und es gibt auch Gruppenrabatt. 1-4 Freerunner - 349 Euro 5-9 Freerunner - 332 Euro 10+ Freerunner - 314 Euro
Whoever: Ich würde vorschlagen bei den Preisen die Auslandsbestellung zu vergessen, da wir damit max. 10 Euro pro Freerunner sparen können. Im Gegenzug fallen aber alle Risiken weg. Ich habe schon mit der Firma telefoniert. Bei einer 10er Bestellung läuft die Abwicklung auch über einen einzigen Besteller. Geld einsammeln und Freerunner verteilen wäre also weiterhin bei einer Person. "
auszug http://wiki.openmoko.org/wiki/Openmoko_Local_Groups:_Munich

also ab 10 leuten gibts freerunner + tasche + head set für 314€/person!
ist auf jeden fall besser als direkt in china zu kaufen und bis jetzt das billigste Angebot in Deutschland!(das mir bekannt ist) ;)

--[[User:govindas|govindas]] 20:18, 27 June 2008 (UTC)

Bei [http://www.pulster.de/ pulster.de] soll '''ein''' Stück 299,- € kosten. Nach einer Sammelbestellung habe ich noch garnicht gefragt. Die nächste Lieferung gibt es aber erst ab dem 25.7.2008. Ich weiß nicht, ob ich das noch so lange durchhalte.

--[[User:Ott--|Ott--]] 14:11, 2 July 2008 (UTC)

...gibt's eigentlich noch Leute, die an einer Sammelbestellung interessiert wären? 25.07. ist zwar noch ein bißchen hin, aber wahrscheinlich wär's ganz gut, jetzt trotzdem schon mal langsam zu ordern, damit das mit der Lieferung dann auch klappt.

--[[User:philippt|philippt]] 01:45, 09 July 2008 (UTC +1 oder 2 ;-) )

Hallo alle zusammen,
ich bin zwar nicht in der Gruppe, aber ebenfalls aus Berlin und ich würde noch zwei Freerunner mitbestellen wollen, wenn das jetzt noch geht!
Vielleicht kriegen wir das Boot voll!
Das wäre schön.

--[[User:VanInwagen|vanInwagen]] 15:16, 22 July 2008 (UTC)

----

== Vorschlag Neuer Treffpunkt ==

hi.

ich schlage vor sich einfach am mittwoch abends in der c-base http://c-base.org/ zu treffen. zeitgleich mit den freifunkern. embedded linux und wifi devices bietet genauso wie eine bar mit bier und genug platz denke ich das passende ambiente.

--[[User:Roh|Roh]] 23:58, 26 June 2008 (UTC)

bin auch dafür --[[User:Torsten Grote|Torsten Grote]] 10:57, 27 June 2008 (UTC)

Jo, da wär ich auch dabei. Seh ich das richtig, daß einige von Euch schon stolze Besitzer sind?
--[[User:philippt|philippt]] 16:06, 27 June 2008 (UTC)

zwangslaeufig ;)
ich brings naechsten mittwoch einfach mal mit (mit fso milestone im nand)
--[[User:Roh|Roh]] 06:19, 2 July 2008 (UTC)
btw, das is heute.--[[User:Roh|Roh]] 06:27, 2 July 2008 (UTC)

grrr...heute klappt bei mir nicht, aber ich schreib mir mal nächsten Mittwoch in den Kalender meines mittlerweile verabscheuungswürdig primitiven Mobiltelefons. --[[User:philippt|philippt]] 19:00, 2 July 2008 (UTC)

hätte auch großes Interesse ... also ist heute Abend jemand dabei? Werde auf jeden Fall mal vorbeischauen. [[User:Sbusch|Sbusch]] 11:00, 9 July 2008 (UTC)

== Stammtisch eingeschlafen? ==

Hallo ihr,

wenn ich mir diese discussion Seite anschaue, scheint mir das ziemlich eingeschlafen zu sein.

Hätte den jemand Lust an irgendeinem hier erwähnten Ort einen Stammtisch mal abzuhalten und nach dem persönlichen Kennenlernen weitere Entwicklungen zu koordinieren?

----

== Stammtisch Berlin ==

Ich könnte mir einen Stammtisch vorstellen oder ein regelmäßiges Treffen.

Ich habe halt keine GTA01Bv4 und werd sie mir auch nicht kaufen können weil ich mir nur GTA02 oder GTA01Bv4 holen kann und die Wahl dann auf GTA02 fällt.... ;-)

Trotzdem würde ich gerne an der Entwicklung jetzt schon mitmachen, das fällt allerdings doch schwer ohne je einmal einen Neo in der Hand gehalten zu haben (Motivation...).

Zumal sich [[Bluetooth_powered_Multi-SIM_support|manche]] Sachen halt nur mit Gerät programmieren lassen...

Soweit ich informiert bin, war schon vor dem Developer launch in Berlin mindestens 2 Geräte vorhanden, bzw. eine kleine Entwicklervormacht.

Comments? --[[User:Minime|Minime]] 16:32, 13 July 2007 (CEST)

Talk:Openmoko Local Groups: Berlin

2008-07-23T17:23:39Z

Kriss: changed layout - meeting first point

== Naechstes c-base-Treffen ==

<center>

'''23.07.2008 in der c-base'''

{| border=1
!Wer
!Wahrscheinlichkeit
!Neo1973
!Freerunner
|-
|[[User:Kriss|kriss]]
|20%
|1-2
|1
|-
|free
|?
|?
|?
|-
|[[User:philippt|philippt]]
|
|0
|0
|-
|[[User:Sbusch|sbusch]]
|
|0
|0
|-
|[[User:Roh|roh]]
|ziemlich
|1
|1
|-
|[[User:Ejokisch|Eckhard]]
|sehr
|0
|0
|}

</center>

== Sammelbestellung ==
Ich werde 10 Geräte bestellen und auch das Administrative übernehmen. Das Angebot bei Pulster zu 299,- inkl. Goodies finde ich voll in Ordnung.
Wer will einen Freerunner?

--[[User:Ejokisch|Ejokisch]] 17:22, 13 July 2008 (UTC)

soweit ich weiß, sind bei pulster.de keine Goodies bei. --[[User:govindas|govindas]] 18:31, 22 Juli 2008 (UTC)

wer die Idee mit der Sammelbestellung noch nicht aufgegeben hat:

"Die Münchner Firma [http://www.handheld-linux.com/wiki.php?page=Neo%20Freerunner Goldelico] bietet Freerunner an. Die Goodies aus dem 10-Pack sind mit dabei und es gibt auch Gruppenrabatt. 1-4 Freerunner - 349 Euro 5-9 Freerunner - 332 Euro 10+ Freerunner - 314 Euro
Whoever: Ich würde vorschlagen bei den Preisen die Auslandsbestellung zu vergessen, da wir damit max. 10 Euro pro Freerunner sparen können. Im Gegenzug fallen aber alle Risiken weg. Ich habe schon mit der Firma telefoniert. Bei einer 10er Bestellung läuft die Abwicklung auch über einen einzigen Besteller. Geld einsammeln und Freerunner verteilen wäre also weiterhin bei einer Person. "
auszug http://wiki.openmoko.org/wiki/Openmoko_Local_Groups:_Munich

also ab 10 leuten gibts freerunner + tasche + head set für 314€/person!
ist auf jeden fall besser als direkt in china zu kaufen und bis jetzt das billigste Angebot in Deutschland!(das mir bekannt ist) ;)

--[[User:govindas|govindas]] 20:18, 27 June 2008 (UTC)

Bei [http://www.pulster.de/ pulster.de] soll '''ein''' Stück 299,- € kosten. Nach einer Sammelbestellung habe ich noch garnicht gefragt. Die nächste Lieferung gibt es aber erst ab dem 25.7.2008. Ich weiß nicht, ob ich das noch so lange durchhalte.

--[[User:Ott--|Ott--]] 14:11, 2 July 2008 (UTC)

...gibt's eigentlich noch Leute, die an einer Sammelbestellung interessiert wären? 25.07. ist zwar noch ein bißchen hin, aber wahrscheinlich wär's ganz gut, jetzt trotzdem schon mal langsam zu ordern, damit das mit der Lieferung dann auch klappt.

--[[User:philippt|philippt]] 01:45, 09 July 2008 (UTC +1 oder 2 ;-) )

Hallo alle zusammen,
ich bin zwar nicht in der Gruppe, aber ebenfalls aus Berlin und ich würde noch zwei Freerunner mitbestellen wollen, wenn das jetzt noch geht!
Vielleicht kriegen wir das Boot voll!
Das wäre schön.

--[[User:VanInwagen|vanInwagen]] 15:16, 22 July 2008 (UTC)

----

== Vorschlag Neuer Treffpunkt ==

hi.

ich schlage vor sich einfach am mittwoch abends in der c-base http://c-base.org/ zu treffen. zeitgleich mit den freifunkern. embedded linux und wifi devices bietet genauso wie eine bar mit bier und genug platz denke ich das passende ambiente.

--[[User:Roh|Roh]] 23:58, 26 June 2008 (UTC)

bin auch dafür --[[User:Torsten Grote|Torsten Grote]] 10:57, 27 June 2008 (UTC)

Jo, da wär ich auch dabei. Seh ich das richtig, daß einige von Euch schon stolze Besitzer sind?
--[[User:philippt|philippt]] 16:06, 27 June 2008 (UTC)

zwangslaeufig ;)
ich brings naechsten mittwoch einfach mal mit (mit fso milestone im nand)
--[[User:Roh|Roh]] 06:19, 2 July 2008 (UTC)
btw, das is heute.--[[User:Roh|Roh]] 06:27, 2 July 2008 (UTC)

grrr...heute klappt bei mir nicht, aber ich schreib mir mal nächsten Mittwoch in den Kalender meines mittlerweile verabscheuungswürdig primitiven Mobiltelefons. --[[User:philippt|philippt]] 19:00, 2 July 2008 (UTC)

hätte auch großes Interesse ... also ist heute Abend jemand dabei? Werde auf jeden Fall mal vorbeischauen. [[User:Sbusch|Sbusch]] 11:00, 9 July 2008 (UTC)

== Stammtisch eingeschlafen? ==

Hallo ihr,

wenn ich mir diese discussion Seite anschaue, scheint mir das ziemlich eingeschlafen zu sein.

Hätte den jemand Lust an irgendeinem hier erwähnten Ort einen Stammtisch mal abzuhalten und nach dem persönlichen Kennenlernen weitere Entwicklungen zu koordinieren?

----

== Stammtisch Berlin ==

Ich könnte mir einen Stammtisch vorstellen oder ein regelmäßiges Treffen.

Ich habe halt keine GTA01Bv4 und werd sie mir auch nicht kaufen können weil ich mir nur GTA02 oder GTA01Bv4 holen kann und die Wahl dann auf GTA02 fällt.... ;-)

Trotzdem würde ich gerne an der Entwicklung jetzt schon mitmachen, das fällt allerdings doch schwer ohne je einmal einen Neo in der Hand gehalten zu haben (Motivation...).

Zumal sich [[Bluetooth_powered_Multi-SIM_support|manche]] Sachen halt nur mit Gerät programmieren lassen...

Soweit ich informiert bin, war schon vor dem Developer launch in Berlin mindestens 2 Geräte vorhanden, bzw. eine kleine Entwicklervormacht.

Comments? --[[User:Minime|Minime]] 16:32, 13 July 2007 (CEST)

Talk:Openmoko Local Groups: Berlin

2008-07-23T17:22:31Z

Kriss: /* Naechstes c-base-Treffen */

== Sammelbestellung ==
Ich werde 10 Geräte bestellen und auch das Administrative übernehmen. Das Angebot bei Pulster zu 299,- inkl. Goodies finde ich voll in Ordnung.
Wer will einen Freerunner?

--[[User:Ejokisch|Ejokisch]] 17:22, 13 July 2008 (UTC)

soweit ich weiß, sind bei pulster.de keine Goodies bei. --[[User:govindas|govindas]] 18:31, 22 Juli 2008 (UTC)

wer die Idee mit der Sammelbestellung noch nicht aufgegeben hat:

"Die Münchner Firma [http://www.handheld-linux.com/wiki.php?page=Neo%20Freerunner Goldelico] bietet Freerunner an. Die Goodies aus dem 10-Pack sind mit dabei und es gibt auch Gruppenrabatt. 1-4 Freerunner - 349 Euro 5-9 Freerunner - 332 Euro 10+ Freerunner - 314 Euro
Whoever: Ich würde vorschlagen bei den Preisen die Auslandsbestellung zu vergessen, da wir damit max. 10 Euro pro Freerunner sparen können. Im Gegenzug fallen aber alle Risiken weg. Ich habe schon mit der Firma telefoniert. Bei einer 10er Bestellung läuft die Abwicklung auch über einen einzigen Besteller. Geld einsammeln und Freerunner verteilen wäre also weiterhin bei einer Person. "
auszug http://wiki.openmoko.org/wiki/Openmoko_Local_Groups:_Munich

also ab 10 leuten gibts freerunner + tasche + head set für 314€/person!
ist auf jeden fall besser als direkt in china zu kaufen und bis jetzt das billigste Angebot in Deutschland!(das mir bekannt ist) ;)

--[[User:govindas|govindas]] 20:18, 27 June 2008 (UTC)

Bei [http://www.pulster.de/ pulster.de] soll '''ein''' Stück 299,- € kosten. Nach einer Sammelbestellung habe ich noch garnicht gefragt. Die nächste Lieferung gibt es aber erst ab dem 25.7.2008. Ich weiß nicht, ob ich das noch so lange durchhalte.

--[[User:Ott--|Ott--]] 14:11, 2 July 2008 (UTC)

...gibt's eigentlich noch Leute, die an einer Sammelbestellung interessiert wären? 25.07. ist zwar noch ein bißchen hin, aber wahrscheinlich wär's ganz gut, jetzt trotzdem schon mal langsam zu ordern, damit das mit der Lieferung dann auch klappt.

--[[User:philippt|philippt]] 01:45, 09 July 2008 (UTC +1 oder 2 ;-) )

Hallo alle zusammen,
ich bin zwar nicht in der Gruppe, aber ebenfalls aus Berlin und ich würde noch zwei Freerunner mitbestellen wollen, wenn das jetzt noch geht!
Vielleicht kriegen wir das Boot voll!
Das wäre schön.

--[[User:VanInwagen|vanInwagen]] 15:16, 22 July 2008 (UTC)

----

== Vorschlag Neuer Treffpunkt ==

hi.

ich schlage vor sich einfach am mittwoch abends in der c-base http://c-base.org/ zu treffen. zeitgleich mit den freifunkern. embedded linux und wifi devices bietet genauso wie eine bar mit bier und genug platz denke ich das passende ambiente.

--[[User:Roh|Roh]] 23:58, 26 June 2008 (UTC)

bin auch dafür --[[User:Torsten Grote|Torsten Grote]] 10:57, 27 June 2008 (UTC)

Jo, da wär ich auch dabei. Seh ich das richtig, daß einige von Euch schon stolze Besitzer sind?
--[[User:philippt|philippt]] 16:06, 27 June 2008 (UTC)

zwangslaeufig ;)
ich brings naechsten mittwoch einfach mal mit (mit fso milestone im nand)
--[[User:Roh|Roh]] 06:19, 2 July 2008 (UTC)
btw, das is heute.--[[User:Roh|Roh]] 06:27, 2 July 2008 (UTC)

grrr...heute klappt bei mir nicht, aber ich schreib mir mal nächsten Mittwoch in den Kalender meines mittlerweile verabscheuungswürdig primitiven Mobiltelefons. --[[User:philippt|philippt]] 19:00, 2 July 2008 (UTC)

hätte auch großes Interesse ... also ist heute Abend jemand dabei? Werde auf jeden Fall mal vorbeischauen. [[User:Sbusch|Sbusch]] 11:00, 9 July 2008 (UTC)

== Naechstes c-base-Treffen ==

<center>

'''23.07.2008 in der c-base'''

{| border=1
!Wer
!Wahrscheinlichkeit
!Neo1973
!Freerunner
|-
|[[User:Kriss|kriss]]
|20%
|1-2
|1
|-
|free
|?
|?
|?
|-
|[[User:philippt|philippt]]
|
|0
|0
|-
|[[User:Sbusch|sbusch]]
|
|0
|0
|-
|[[User:Roh|roh]]
|ziemlich
|1
|1
|-
|[[User:Ejokisch|Eckhard]]
|sehr
|0
|0
|}

</center>

== Stammtisch eingeschlafen? ==

Hallo ihr,

wenn ich mir diese discussion Seite anschaue, scheint mir das ziemlich eingeschlafen zu sein.

Hätte den jemand Lust an irgendeinem hier erwähnten Ort einen Stammtisch mal abzuhalten und nach dem persönlichen Kennenlernen weitere Entwicklungen zu koordinieren?

----

== Stammtisch Berlin ==

Ich könnte mir einen Stammtisch vorstellen oder ein regelmäßiges Treffen.

Ich habe halt keine GTA01Bv4 und werd sie mir auch nicht kaufen können weil ich mir nur GTA02 oder GTA01Bv4 holen kann und die Wahl dann auf GTA02 fällt.... ;-)

Trotzdem würde ich gerne an der Entwicklung jetzt schon mitmachen, das fällt allerdings doch schwer ohne je einmal einen Neo in der Hand gehalten zu haben (Motivation...).

Zumal sich [[Bluetooth_powered_Multi-SIM_support|manche]] Sachen halt nur mit Gerät programmieren lassen...

Soweit ich informiert bin, war schon vor dem Developer launch in Berlin mindestens 2 Geräte vorhanden, bzw. eine kleine Entwicklervormacht.

Comments? --[[User:Minime|Minime]] 16:32, 13 July 2007 (CEST)

Getting Started with your Neo FreeRunner

2008-07-17T20:51:23Z

Kriss: /* Step 2. Flashing the Kernel */

{{Languages|Getting Started with your Neo FreeRunner}}

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #cccccc; background:#eeeeee; width:100%;floating="center"; "
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:75% " |
<div align="left">
Thank you for purchasing this Developer release of Neo FreeRunner. The [[Neo FreeRunner]] phone is the second hardware platform to take advantage of [[Openmoko]]. This guide will help you get to know your Neo FreeRunner and how to start using your Neo FreeRunner.
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:Freerunner box.png|200px|thumb|Neo FreeRunner Package]]
|}

== The Package Contents ==

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #ffffff; background:#ffffff; width:80%; floating="center"; "
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid ffffff; border:1px solid #ffffff; " |
<div align="left">
[[Image:GTA02ALL.png|400px|thumb|Inside package]]
|

: [[Image:Circle２.gif|10px]] Neo FreeRunner
: [[Image:Circle２.gif|10px]] Stylus
: [[Image:Circle２.gif|10px]] Battery
: [[Image:Circle２.gif|10px]] Charger
: [[Image:Circle２.gif|10px]] USB Cable
: [[Image:Circle２.gif|10px]] microSD Card 512MB & SD adapter
|}
</div>

==Getting To Know the Neo FreeRunner==

<div align-center>
<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: 25px; padding-left: 0.5em;">
</td>
<td style="width: 10px; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu8.jpg|370px|thumb|AUX Button and phone jack(From left to right)|center]]</td><td style="padding: 1px 1em 0; background: #ffffff;">
[[Image:menu9.jpg|365px|thumb|Power Button, USB and external GPS Antenna (From left to right)|center]]</td></tr></table>
</div>

<div align-center>
<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%; padding-left: 0.5em;">
</td>
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu12.jpg|233px|thumb|AUX Back side with battery|center]]</td><td style="padding: 1px 1em 0; background: #ffffff;">
[[Image:menu11.jpg|260px|thumb|Put the SIM card and SD card here|center]]</td></tr></table>
</div>

<div align-center>
<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%; padding-left: 0.5em;">
</td>
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|open case from this side |center]]</td><td style="padding: 1px 1em 0; background: #ffffff;">
[[Image:menu14.jpg|250px|thumb|Opened|center]]</td></tr></table>
</div>

===Installing the Micro-SD card, the SIM card, and the Battery ===

# Remove the rear cover of the Neo FreeRunner by first holding the Neo FreeRunner on the side and then use your fingernail to prise off the rear cover at the slot on top of the device.
# Now you should be able to locate the combined SIM and Micro-SD card holder at the bottom of the battery compartment.
# Unlock the SIM card holder by sliding the metal clip down, towards the USB socket, with your fingernail. Use caution, as these parts are delicate and could be damaged by forcing them in the wrong direction.
# Lift up on the SIM card holder.
# The Micro-SD card holder is held in place by a latch on either side. It is easiest to open the Micro-SD card holder by releasing these latches one at a time rather than by lifting from the middle, as lifting from the middle tends to increase the latching pressure. A small screwdriver or knife can be used for this.
# Insert the Micro-SD card into the Micro-SD card holder. Note that on the inside of metal part of the holder there are little holding tabs for the card. Slide the card in these holders (on the metal part) before closing the card holder. Note that the electrical contacts should face down and towards the edge of the Neo Freerunner.
# Close the Micro-SD card holder, making sure that both latches of the holder are securely fastened.
# Insert the SIM card into the SIM card holder, taking care to slide inside the two metal tabs in the cover. Note that the electrical contacts should face down and that the cut corner should be closest to the external GPS Antenna Socket.
# Close the SIM card holder and lock it by sliding the metal clip towards the external GPS Antenna Socket on the FreeRunner.
# Insert the battery into the battery compartment, aligning the electrical contacts on the battery with the electrical contacts in the battery compartment. Insert the side with the electrical contacts first.
# Replace the rear cover on the FreeRunner.

[[Image:FR_SIM_SD_open.jpg|457px|thumb|SIM and SD holders open, with cards in place|center]]

===Charging the Neo Freerunner===

When using the Neo Freerunner for the first time, you should charge the battery completely. The battery can be charged using the provided charger (at 1000mA) or from a powered USB port capable of providing 500mA worth of current. Most computers will be able to charge the FreeRunner without any problems.

Charging at 100mA takes 6-12 hours and at 500mA takes 1-2 hours. (from [http://openmoko.togaware.com/survivor/Charging.html openmoko.togaware.com])

===The Buttons===

====Power====
Tapping the power button exits the current application.

Holding the power button brings up a menu allowing you to power on and off the gps, wifi, gsm, and bluetooth antennae, and also to shutdown the device.

====Aux====

Holding the aux button for a second brings up a menu allowing you

* Toggle Fullscreen: Hide and show the title bar
* Swap Orientation: Rotate the screen contents for horizontal and vertical viewing
* Screenshot: Start an application to save an image file of the current screen contents

===Unlocking the screen===

When the screen is locked, you should see a Matrix-style green graphic with the Openmoko symbol in the middle of the bottom of the screen along with lock and unlock symbols. If you drag the Openmoko symbol to the unlock symbol at the top then the screen will become unlocked.

===Menus and Applications===

''Note:'' this section describes the interface used by the "2007.2" image, which is the current default image for Openmoko.

====Today Page====
[[Image:Todaypage_reduced_false.png|right|200px|]]
The first thing after you boot Openmoko should be the "Today" page. This is your home page. In the top row, you see icons that indicate the status of the phone. The second row are quick links to commonly-used applications such as the dialer. The main body of the screen is your home page, displaying a clock and other useful information. The bottom row consists of three tabs representing Today (the page you're viewing now), Launch Task Page, and Running Tasks Page.

See [[Today/2007.2]] for more information about the Today page and customization.<br clear=all />

====Launch Task Page====

{{stub}}

This page displays a menu of available applications. You may choose a category of applications to display to simplify the screen, or choose to display them all.

Current categories are [[PIM Suite]], [[Applications]], [[Games]], [[Utilities]], and All.

====Running Tasks Page====

{{stub}}

This page displays currently-running tasks. Any individual task may be terminated by selecting it and then clicking on the garbage-can icon to close it. All tasks may be terminated by clicking on any one of them and then clicking on the "folder" icon in the upper right (expect this to change in future releases). Any task may be rejoined by selecting it and then selecting the "return" icon at the middle top.

====Exiting an Application====

Any time an application is running, you can simply click the device's power button and the application will exit, returning you to the Today page.

Alternatively, you can switch tasks at any time by clicking the menu of tasks at the far upper-left of the screen, which will display a list of running tasks, allowing you to select one.

(''Note:'' If the task menu is not shown, use the [[#Aux|Aux]] button to bring up the Aux menu, and select "Toggle Fullscreen".)

===Adjusting the Volume===

As of this writing, there is no way to adjust the volume from the screen.

For now, run the terminal application or [[Getting_Started_with_your_Neo_FreeRunner#Connect_to_the_Neo_FreeRunner_By_USB_Networking|log in via usb]], and run the [[alsamixer]] application. The mixer is simpler than it looks. Just use the left and right arrow keys to select "headphone" or "PCM" and use the up and down arrow keys to adjust the volume. You can also adjust your microphone volume with the "mic2" adjustment. Press ESC when finished. Then exit the terminal application or log out of the USB login.

You may need to update configuration files in /usr/share/openmoko/scenarios/ to make the microphone setting permanent. Use
alsactl -f ''path-to-statefile'' store
to do this.

The default files are as follows (in /usr/share/openmoko/scenarios/):
:gsmhandset.state
:gsmheadset.state
:gsmspeakerout.state
:headset.state
:stereoout.state

These correspond to the various Sound Profiles accessible in the Debug Tool under Applications.

=== Accessing the microSD card ===

Mounted at /media/card

=== Importing contacts ===

If you can export your contacts to VCard format, either multiple files or single file containing all of them, you may use the script on [[Import Vcf Contacts]] page to bring them to Neo.

=== Where to go when things go wrong ===

You may ask for help on the support mailing list : more details at https://lists.openmoko.org/mailman/listinfo/support

[[Freerunner_Hardware_Issues]]

==Connect to the Neo FreeRunner By USB Networking==

Connect the Neo FreeRunner to a GNU/Linux host with the USB cable. For Mac OS X please refer to [[MacOS_X]]. For Windows XP and Vista please refer to [[Neo1973_and_Windows]] (which also works for the FreeRunner). After booting into the Openmoko image there will be a new interface, usb0, on your GNU/Linux host.

=====Manual Method=====
Type in the following commands in the terminal of a GNU/Linux host:

ifconfig usb0 192.168.0.200 netmask 255.255.255.0
ssh root@192.168.0.202

Press Enter to get by the password.

=====Automatic Method=====
*Debian and derivatives (Ubuntu, Sidux etc.)
Edit /etc/network/interfaces:

auto usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0

*Gentoo
Edit /etc/conf.d/net:

config_usb0="192.168.0.200/24"

Restart the networking service ('/etc/init.d/networking restart' for Debian-based systems) and then type the following command in the terminal of the GNU/Linux host:

ssh root@192.168.0.202

Press Enter to get by the password.

{{note|
If your network device is using the ip range 192.168.0.x you may have to use the following command before you are able to connect

route add -host 192.168.0.202 dev usb0 }}

=====Making things even more automatic=====
If you don't want to remember the IP address of your phone then you can create an alias by adding the following line to your /etc/hosts:

192.168.0.202 openmoko

Now it should be possible to connect to your phone using the following command:

ssh root@openmoko

The above only gets you a Secure Shell connection to the Openmoko device, it does not allow the Openmoko device to connect to the Internet. If you are interested in connecting the device to the internet then check out the [[USB_Networking]] section.

=====Allow FreeRunner to Connect to Internet via USB=====
For the FreeRunner to access the internet through the USB connection, you will also need to make modifications on the PC it is connecting through.

In Ubuntu:

Within /etc/network/interfaces, change your interface setup to this:

auto usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
up echo 1 > /proc/sys/net/ipv4/ip_forward &
up iptables -P FORWARD ACCEPT &
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &

In Fedora:

Set /etc/sysconfig/network-scripts/ifcfg-usb0 to this:
DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

Set /etc/sysconfig/network-scripts/ifup-usb to this:
#!/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 to this:
#!/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

=====Updating DNS=====

Once your PC is setup, then edit /etc/network/interfaces on your FreeRunner and modify the code from this:

iface usb0 inet static
address 192.168.0.202
netmask 255.255.255.0
network 192.168.0.0
gateway 192.168.0.200
up echo nameserver 192.168.0.200 > /etc/resolv.conf

to something that points to a real name server, like a public DNS system from OpenDNS, like this:

iface usb0 inet static
address 192.168.0.202
netmask 255.255.255.0
network 192.168.0.0
gateway 192.168.0.200
up echo nameserver 208.67.222.222 > /etc/resolv.conf
up echo nameserver 208.67.220.220 >> /etc/resolv.conf

Note: vi appears to be the only text editor available by default. See [http://www.cs.colostate.edu/helpdocs/vi.html basic vi commands] for help.

On the factory loaded OM2007.2 image, run the following to restart networking for the DNS changes to take effect:

/etc/rc0.d/K40networking restart

If your LAN also has the subnet 192.168.0.0/24, you will need to do the following on your PC, as root, in order to allow your PC to access both the FreeRunner and other hosts:

route add -host 192.168.0.202 dev usb0
route del -net 192.168.0.0 netmask 255.255.255.0 usb0

[[User:Linuxpaul|More information]] (includes more specific instructions for Mandriva)

==The Architecture==

There are three layers to the software on the FreeRunner:

===uBoot===

Think of u-boot as a combination of the BIOS and Grub on a PC.

===Kernel===

The Linux kernel.

===Root Filesystem===

The rest of the system

==Updating the software==

In order to keep the FreeRunner up-to-date with the latest features and bug-fixes, it is advisable update the software at regular intevals. There are two main methods of doing this.

===opkg===

Assuming that your FreeRunner can access the internet (see above), the kernel and other packages can be updated with

# opkg update
# opkg upgrade

The first updates the repository information, telling opkg what packages are available. The second upgrades all packages for which a newer version is available. '''At the moment, some signature files are missing (404 errors), which opkg complains about, but this is cosmetic.''' The repositories will still update with the missing signature files.

It will be possible in the future to update uboot with opkg, but this has not yet been implemented

===Flashing===

uboot, the kernel and the root filesystem can all be flashed to update them. See below for how. For uboot, this is the only possibility. The advantage of flashing the kernel, rather than using opkg seems to be speed.

The disadvantage of flashing the root file system is that it wipes out all local modifications, including /home. If /home is moved to the SD disk, this is no longer a problem.

==Un-crippling the 2007.2 image==

The stock [[Openmoko2007.2]] image flashed onto the Neo FreeRunner is really just the bare bones. For example, you don't have the clock and the quick-launch icons showing. Here's how you can change that:

# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false
# /etc/init.d/xserver-nodm restart

If you rather have a regular clock instead of the digital one, do this instead:

# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false
# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/digital_clock false
# /etc/init.d/xserver-nodm restart

More information about today screen customization at [[Today/2007.2]].

With either clock, you may wish to set the correct [[Date]] and [[Timezone]].

Also, if you prefer having a full keyboard, see [http://www.ginguppin.de/node/15 these instructions].

===GPS===

Simple guide to get going with GPS:

# opkg install gpsd
# echo "GPS_DEV=\"/dev/ttySAC1\"" > /etc/default/gpsd

and restart gpsd, the gps daemon, with

# /etc/init.d/gpsd restart

To test GPS, you can use agpsui:

# opkg install openmoko-agpsui

For a nice map, try tangoGPS:

# opkg install http://www.tangogps.org/downloads/tangogps_0.9.2-r1_armv4t.ipk

More information on [[GPS]] page.

=== GPRS ===

See [[Manually using GPRS]]. According to some [http://lists.openmoko.org/pipermail/support/2008-July/000003.html posts], GPRS might be broken currently (2007.2), though. Any updates welcome.

=== WLAN ===

See [[GTA02 WLAN]].

===Recommended software===

For a Media Player:

# opkg install openmoko-mediaplayer2
# wget http://abraxa.dyndns.org:81/random/openmoko-mediaplayer-theme.tar.bz2
# tar xjf openmoko-mediaplayer-theme.tar.bz2 -C /usr/share/themes/Moko/gtk-2.0
# rm openmoko-mediaplayer-theme.tar.bz2

If you want a basic image viewer, have a look at the one from the gpe suite:

# opkg install gpe-icons gpe-gallery

To obtain the standard web browser, use:

# opkg install openmoko-browser2

An alternative browser, minimo, offers many more features.
First download and unpack it on your GNU/Linux host:

# wget http://www.ginguppin.de/files/minimo.tar.bz2
# tar jvxf minimo.tar.bz2

Copy it over to the FreeRunner:
# scp minimo_* root@openmoko:/tmp

Then on the FreeRunner:
# opkg install /tmp/minimo_0.02\+cvs20070626-r0_armv4t.ipk

There are tons more apps you can install - check out the [[Repositories]] for a list of packages.

==Booting the Neo Freerunner==

You can boot your Neo FreeRunner in the following ways:

: [[Image:Circle２.gif|10px]] You can power it up into an Openmoko image directly (default, when powered-on for the first time).

: [[Image:Circle２.gif|10px]] You can boot it into the [[Bootloader|U-Boot bootloader]] via [[NAND Flash]].

: [[Image:Circle２.gif|10px]] You can boot it into U-Boot via NOR Flash.

Booting the device into NAND and NOR Flash allows you to update the kernel and root filesystem.

====Start the Openmoko Image====

<div align-center>
<table width="100%" 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: 25px; padding-left: 0.5em;">

</td>
<td style="width: 10px; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:Menu2.jpg|200px|right|thumb]]</td><td style="padding: 1px 1em 0; background: #eeeeee;">
Press and hold Power button for about 8 seconds, until the Openmoko splash screen turns up. You may now release the Power button and the Neo FreeRunner will continue to boot into the Openmoko Image.

</td></tr></table>
</div>

====Log into U-Boot in the NAND Flash====

<div align-center>
<table width="100%" 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: 25px; padding-left: 0.5em;">

</td>
<td style="width: 10px; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:Menu7.jpg|200px|right|thumb]]</td><td style="padding: 1px 1em 0; background: #eeeeee;">
Press and hold Power button, then press and hold AUX button for about 5 to 8 seconds. You should see the boot menu for the NAND Flash. Press the AUX button to select one of the options and then press the Power button to execute.
</td></tr></table>
</div>

====Log into U-Boot in the NOR Flash====

<div align-center>
<table width="100%" 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: 25px; padding-left: 0.5em;">

</td>
<td style="width: 10px; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:Menu6.jpg|200px|right|thumb]]</td><td style="padding: 1px 1em 0; background: #eeeeee;">

Press and hold the AUX button, then press and hold the Power button. Then, release the AUX button. You should see the boot menu for the NOR Flash. This option is usually used by developers or when flashing the FreeRunner. If you cannot log into U-Boot in NAND then you can log into U-Boot in the NOR Flash either.
</td></tr></table>
</div>

{{note| There are six options you can choose when you log into the NOR Flash.
1. Boot

2. [[Boot from sd card|Boot from MicroSD]]

3. Set console to USB

4. Set console to Serial

5. Reset

6. Power off}}

{{note|The term ''Logging in'' used in this context means to turn on the device using the described method, and leaving it at the U-Boot menu. To avoid the device automatically booting, tap the AUX key to move the selector bar. Note also that the device will '''not''' automatically turn off while flashing is in progress.
}}

==Flashing the Neo FreeRunner==
As Openmoko development continues, Openmoko regularly releases updated versions of the Openmoko root filesystem, the kernel, and the[[Bootloader| U-Boot]]. These may be programmed into the Flash memory of Neo FreeRunner. You can use the USB cable and Openmoko provided tool to flash Neo FreeRunner.

{{note|The Openmoko software team builds images daily. If you want to use the latest images, you can download the image from the daily build, but we recommend you download the most stable image from http://downloads.openmoko.org/releases/Freerunner/. Images here have been tested by the test team.

More about current Images: http://wiki.openmoko.org/wiki/Latest_Images}}

===Step 1. Download the DFU-util===

You can download the flashing tool from:
http://downloads.openmoko.org/releases/Freerunner/dfu-util

On the GNU/Linux host you can use the following command to download the dfu-util:
wget http://downloads.openmoko.org/releases/Freerunner/dfu-util

Afterwards you have to change the rights on the file:
chmod a+x dfu-util

===Step 2. Flashing the Kernel===

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:0px solid #ffffff; background:#ffffff; width:100%;floating="center";font-weight: normal; "
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid #ffffff; border:1px solid #ffffff; width:75%;font-weight: normal; " |
<div align="left">
[[Image:menu15.jpg|thumb|Log into U-Boot in NOR Flash, connect your Neo with Linux Host via USB cable]]

Before you execute the following command, please log into U-Boot in the NOR Flash. The Neo FreeRunner needs to be at the NOR boot menu for flashing. You will then need to connect your Neo with the GNU/Linux host via USB cable.

You can download the kernel from
http://downloads.openmoko.org/releases/Freerunner/

Type in the following command in the terminal on a GNU/Linux host. On some systems you need to be root before this will work and on Ubuntu you must preface the command with "sudo" or you will get the following error: "Cannot claim interface: could not claim interface 2: Operation not permitted"

./dfu-util -a (partion name) -R -D (download image file name)

ex:

sudo ./dfu-util -a kernel -R -D uImage-2.6.24+git20080424-om-gta02.bin

Press Enter to execute the command.

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!
|}

{{note| The meaning of the parameters you specified:
-a --alt alt Specify the altsetting of the DFU interface by name or by number<br>
-R --reset Issue USB Reset signalling once we're finished<br>
-D --download file Write firmware from<file> into device <br>
}}

===Step 3. Flashing the Root Filesystem ===
You can download the root filesystem from:
http://downloads.openmoko.org/releases/Freerunner/

Type the following command in the terminal of a GNU/Linux host. On some systems you will need to be root.

./dfu-util -a rootfs -R -D openmoko-devel-image-fic-gta02.jffs2

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!

==Appendix==
If you want to know more about the Neo FreeRunner then you can get more information in the following topics:

* [[GTA02 Openness]]
* [[Neo FreeRunner]]
* [[Neo FreeRunner GTA02 Hardware]]
* [[FreeRunner/Buttons and LEDs]]
* [[Latest Images]]
* [[Distributions]]

To search this wiki with Google, use the following search term:

<search term> site:http://wiki.openmoko.org/wiki/

An excellent tool for searching all the openmoko mailing lists is http://openmoko.markmail.org/

[[Category:GTA02 Hardware]]
[[Category:Guides]]
[[Category:User Guides]]

Main Page

2008-07-17T19:49:18Z

Kriss: removing emulation chroot-image <-- It's way outdated and I think offline - I did this mid 2007

__NOTOC__
__NOEDITSECTION__
{{Languages|Main Page}}
<br>
<DIV ALIGN=center><big>'''[[Openmoko]]™ - Open. Mobile. Free.'''</big><br></DIV>
<BR>

==<font color=75d806>Introduction to Openmoko</font>==

{{mainpage}}

[[Image:OpenmokoFramework08.png|250px|left|Openmoko Software Stack|thumb]]

[[Openmoko]]™ born as an [http://en.wikipedia.org/wiki/Open_source Open Source] project under [[License| GPL and LGPL license]] and dedicated to delivering an open software stack on mobile platforms, shipped its first product, the Neo 1973, on July 9 2007; and then, turned the project into a start-up company with one aim: create great mobile products using the Openmoko stack: Open. Mobile. Free.

The [[NeoSoftwareStack|Openmoko stack]], which includes a full [[Host-based development with Xoo and Xephyr|X server]], allows users and developers to transform mobile hardware platforms into unique products. Our licence gives developers and users freedom from the "iron to the eyeballs," freedom to cosmetically customize their device or radically remix it; change the wallpaper or rebuild the entire house! It grants them the freedom, for example, to transform a phone into a medical device or point of sale device or the freedom to simply install their own favorite software. Beyond freeing the software on our devices we have also released our CAD files under Creative Commons ShareAlike. By freeing the software under GPL, we enable the community of FOSS developers to "make it new." By freeing the [http://downloads.openmoko.org/CAD/ CAD] files we give industrial designers and engineers this same opportunity.

==<font color=75d806>Openmoko Products</font>==
{{Bar}}

[[Image:Freerunner02.gif|thumb|150px]]
The first Openmoko product, the [[Neo 1973]], sold exclusively through [http://www.openmoko.com/store.html Openmoko Online Shop]. It sold out in early February 2008.

Openmoko started selling the Neo FreeRunner (GTA02), the second generation of Neo, on July 3, 2008. Add your nickname to those interested buying the Neo FreeRunner at [[Buying_Interest_List|Buying Interest List]]. Also, look for a group to buy with at [[GroupSales]] for a discount and extra goodies. If you've just received your FreeRunner, check out [[Getting Started with your Neo FreeRunner]] for tips.

==<font color=75d806>Join Openmoko development</font>==

{| class="wikitable" cellspacing="4" cellpadding="6" width=100%
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600; " | <font color="white" >Developer Guides</font>
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600;" |<font color="white" >Test / Emulation and share project</font>
|-
|valign="top" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |
===<font color=white>Developer </font>===
* [[Toolchain|toolchain usage]]
* <font color=white>VMware</font>
* [[Python|python intro]]
* [[Openmoko under QEMU]]

===<font color=white>System Integration and customizing a distribution</font>===
* [[OpenEmbedded|OE-The distribution building framework]]
* [[MokoMakefile|Building Openmoko using the MokoMakefile ]]
* [[Opkg|Opkg]]
===<font color=white>Low level / system development</font>===
* <font color=white>Low-Level</font>
* [[u-boot]] <font color=white>-The bootloader we use, including docs to our modifications</font>
* [[kernel]] <font color=white>-The Linux Kernel we use, including docs to our modifications</font>
* [[gsmd]] <font color=white> -the GSM daemon managing the GSM Modem</font>
* [[agpsd]] <font color=white>-the AGPS (Assisted GPS) daemon</font>

|valign="top" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |
===<font color=white>Test</font>===
*[[Test Cases]]
<font color=white> ※</font> [[:Category: Test | See More About Test]]

===<font color=white>Emulation</font>===
*[[Getting Openmoko working on host with Xephyr]]

===<font color=white>Publish your project===
*[[CommunityRepository|Publish Your Project]]
|}

==<font color=75d806>Openmoko community</font>==
Anyone can join the Openmoko project and contribute to designing open products. Join us and collaborate through any of the [[Development resources | project resources]], including this Openmoko Wiki. See the [[Help:Contents | wiki editing help]]page for information on making contributions to this wiki.

You can start by using the [[introduction]] page, photos, videos and Openmoko Wiki Official Index Page. As always, the usual [[FAQ | Frequently Asked Questions]] (FAQ), [http://lists.openmoko.org/mailman/listinfo/| mailing list] pages and [[Discussion_Forums| Discussion Forums]] are helpful.

{| class="wikitable" cellspacing="4" cellpadding="6" width=100%
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600; " | <font color="white" >In News</font>
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600;" |<font color="white" >Community & Events</font>
|-
|valign="top" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |
==<font color=white>In News</font>==
*[[Getting Started with your Neo FreeRunner]]
*[[ASU Feature Plan]]
*[[CommunityRepository|Share your project]]
*[[GroupSales]]
*[[Why Openmoko|Why Openmoko is best: A Comparative Look]]
==<font color=white>Snapshot</font>==
*<font color=white>You can always download the latest build here.</font>
** <font color=white>For FreeRunner </font>[http://buildhost.openmoko.org/daily/freerunner/ http://buildhost.openmoko.org/daily/freerunner/]
** <font color=white>For Neo 1973 the link is</font> [http://buildhost.openmoko.org/daily/neo1973/ http://buildhost.openmoko.org/daily/neo1973/]
** <font color=white>Tools , like dfu-util and openocd :</font>[http://buildhost.openmoko.org/daily/tools/ http://buildhost.openmoko.org/daily/tools/]
*<font color=white>Reviews of the daily snapshot build are [[Snapshot_review|here]] and the recommended kernel and root image from the review will always be available [http://downloads.openmoko.org/recommended/ here].</font>
<font color=white>Note that the recommended set is not always the latest, but is the most stable, reliable, and functional.</font>
|valign="top" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |

==<font color=white> Community Update</font>==
<font color=white>For the latest status updates, see [[Community_Updates|Community Updates]]</font>

<font color=ffffff> ※</font>[[:Category:Community| See More About Community...]]

==<font color=white>Get the overview of wiki</font>==
*<font color=white>To get the overview of Openmoko Wiki, see [[Openmoko Wiki Official Index Page]].</font>
==<font color=white>Events</font>==
*[[Summer of Code 2008]]
*[[Openmoko Education/zh tw]]
*[[Events:FOSDEM 2008]]
*[[OpenLab]]

<font color=ffffff> ※</font>[[:Category:Event| See More About Event...]]

|}

==<font color=75d806>Getting started with Openmoko Wiki</font>==
The Openmoko Wiki is open. Everyone can join. You'll find information including: hardware and software documentation, bug lists, community news of Openmoko and much more. Join our wiki, edit the wiki, contribute valued content, and help others. For the full picture of Openmoko Wiki, please visit the [[Openmoko Wiki Official Index Page|Openmoko Wiki Official Index Page]].

* Please read our [[Openmoko Wiki Editing Guidelines]]
* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]
* [http://meta.wikimedia.org/wiki/Help:Wikitext_reference MediaWiki Wikitext Reference]
* If you add a new page, you can reference the [[Openmoko Wiki Categories Index Page|Openmoko Wiki Categories Index Page]] to put your page on the right category.
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]

<font color=426fdc>※</font>[[:Category: Help | See More About Help ]]

[[Category:Information| ]]

Openmoko Local Groups: Berlin

2008-07-04T10:46:07Z

Kriss: /* Meetings, Events */

See [[Talk:OpenMoko_Local_Groups:_Berlin|discussion]]

=== Mailing list ===
There will be mailing list soon (ETA 2008-07-01). Feel free to join us there!

=== Possible Participants ===
{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
!Has Device
!Has Debug Board
|-
|[[User:Minime|tim]]
|mostly web related
|No GTA01Bv4, waiting for GTA02.
|berlin.nord
|willing to organize stuff i.e. meeting location/whatever. [http://wiki.openmoko.org/index.php?title=User_talk:Minime&action=edit&section=new talk to me], or e-mail: OM DOT 5 DOT minime@xoxy.net
|
|
|-
|[[User:spag|spag]]
|too lazy
|patiently waiting for GTA02 with WLAN
|Marzahn
|I'm interested in VoIP applications on OpenMoko.
|
|
|-
|[[User:PH5|pH5]]
|Coding, RE, Uni
|OpenMoko, gsmd, GTA01, Magician
|Zehlendorf
|[http://projects.linuxtogo.org/projects/sphyrna Sphyrna]
|[[Image:Moko.jpg|center]]
|
|-
|[[User:Barmeier|barmeier]]
|Coding in C and Java
|GTA01, Magician
|Steglitz
|I'am interested in Sync, application integration and usability improvements
|
|
|-
|[[User:Kriss|kriss]]
|Coding
|
|Wedding
|
|[[Image:Moko.jpg|center]]
|[[Image:MokoBox.jpg|center]]
|-
|[[User:Roh|roh]]
|hw, sw
|
|mitte/pberg
|access to schematics
|GTA01bv4, GTA02v5, etc[[Image:Moko.jpg|center]]
|[[Image:MokoBox.jpg|center]]
|-
|[[User:proquar|chris]]
|travelling in time and space
|abusing the freerunner in every way imaginable
|Wedding
|Anyone in interested in group-order? see: http://lists.openmoko.org/pipermail/community/2008-April/015080.html at the bottom
|
|
|-
|[[User:einalex|einalex]]
|Coding, TU, cooking, soldering
|FreeRunner, syncing
|Hamburg / Frankfurt / München
|If you decide to order a 10pack I'd like to join the fun. Contact me at my email address alexander dot gabriel at tuhh dot de
|
|
|-
|[[User:fischel|fischel]]
|php, java, triathlon
|FreeRunner
|Charlottenburg
|interested in group-order
|A780
|
|-
|[[User:Torsten_Grote|Torsten]]
|coding, ui
|testing, minor coding, meeting
|Griebnitzsee
|let's initiate local user group meetings
|[[Image:Moko.jpg|center]] gta02v5
|
|-
|[[User:govindas|govindas]]
|perfect DAU simulator.
|freerunner, meetings
|Friedrichshain
|group order
|
|
|-
|[[User:philippt|philippt]]
|coding (java, python, perl, bash), linux stuff
|want to have a really smart phone
|Friedrichshain
|interested in group order, knowledge sharing and real-life experience with freerunner
|
|
|-
|[[User:ogai|ogai]]
|coding (java, groovy), linux stuff
|want to have a really smart phone
|Prenzlauer Berg
|interested in group order, knowledge sharing and real-life experience with freerunner
|
|
|-
|[[User:carcinoma|carcinoma]]
|coding (c++, progress), linux, Design
|free me from proprietary tools
|Weissen See (Pankow)
|interested in knowledge sharing, freetime usage, usage in Job/Professional
|Get GTA02 from Pulster, next big order will be mine(25.7.)
|
|-
|[[User:Ott--|ott--]]
|coding, Linux, even Windows
|I want to be free
|Schmöckwitz (Köpenick)
|interested in group order
|
|
|-
|[[User:dk|dk]]
|java
|Gta02
|moabit
|interested in group order
|
|
|-
|[[User:relet|relet]]
|code
|would read your feed
|moabit
|
|soon
|nak
|-
|...
|
|
|
|
|
|
|}

=== Meetings, Events ===
Meeting language is German ;-)
{|border=1
!Date
!Location
!Topic
!Who
|-
|8.-12. August 2007
|Flugplatz Finowfurt
|[https://events.ccc.de/camp/2007/Intro/ Chaos Communication Camp 2007] und [http://events.ccc.de/camp/2007/GSM_Village GSM Village]
|?
|-
|23.08.2007 / 18:00
|[https://berlin.ccc.de/wiki/CCC_Berlin CCCB] / [https://berlin.ccc.de/wiki/Club_Discordia Club Diskordia]
|First meeting. bring your hardware
|Roh, pH5, [[User:Minime|tim]](+ 2?), ? (please add yourself)
|-
|09.07.2008 / 20:00
|[http://wiki.c-base.org/coredump/WaveLoeten c-base (zusammen mit dem Freifunkertreffen)]
|Freerunner Release / Hands On
|[[User:Kriss|kriss]], ? (please add yourself)
|}

[[Category:Community]]
[[Category:Openmoko Local Groups]]

Openmoko Local Groups: Berlin

2008-07-04T10:45:23Z

Kriss: /* Meetings, Events */ - 09.07.2008 / 20:00

See [[Talk:OpenMoko_Local_Groups:_Berlin|discussion]]

=== Mailing list ===
There will be mailing list soon (ETA 2008-07-01). Feel free to join us there!

=== Possible Participants ===
{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
!Has Device
!Has Debug Board
|-
|[[User:Minime|tim]]
|mostly web related
|No GTA01Bv4, waiting for GTA02.
|berlin.nord
|willing to organize stuff i.e. meeting location/whatever. [http://wiki.openmoko.org/index.php?title=User_talk:Minime&action=edit&section=new talk to me], or e-mail: OM DOT 5 DOT minime@xoxy.net
|
|
|-
|[[User:spag|spag]]
|too lazy
|patiently waiting for GTA02 with WLAN
|Marzahn
|I'm interested in VoIP applications on OpenMoko.
|
|
|-
|[[User:PH5|pH5]]
|Coding, RE, Uni
|OpenMoko, gsmd, GTA01, Magician
|Zehlendorf
|[http://projects.linuxtogo.org/projects/sphyrna Sphyrna]
|[[Image:Moko.jpg|center]]
|
|-
|[[User:Barmeier|barmeier]]
|Coding in C and Java
|GTA01, Magician
|Steglitz
|I'am interested in Sync, application integration and usability improvements
|
|
|-
|[[User:Kriss|kriss]]
|Coding
|
|Wedding
|
|[[Image:Moko.jpg|center]]
|[[Image:MokoBox.jpg|center]]
|-
|[[User:Roh|roh]]
|hw, sw
|
|mitte/pberg
|access to schematics
|GTA01bv4, GTA02v5, etc[[Image:Moko.jpg|center]]
|[[Image:MokoBox.jpg|center]]
|-
|[[User:proquar|chris]]
|travelling in time and space
|abusing the freerunner in every way imaginable
|Wedding
|Anyone in interested in group-order? see: http://lists.openmoko.org/pipermail/community/2008-April/015080.html at the bottom
|
|
|-
|[[User:einalex|einalex]]
|Coding, TU, cooking, soldering
|FreeRunner, syncing
|Hamburg / Frankfurt / München
|If you decide to order a 10pack I'd like to join the fun. Contact me at my email address alexander dot gabriel at tuhh dot de
|
|
|-
|[[User:fischel|fischel]]
|php, java, triathlon
|FreeRunner
|Charlottenburg
|interested in group-order
|A780
|
|-
|[[User:Torsten_Grote|Torsten]]
|coding, ui
|testing, minor coding, meeting
|Griebnitzsee
|let's initiate local user group meetings
|[[Image:Moko.jpg|center]] gta02v5
|
|-
|[[User:govindas|govindas]]
|perfect DAU simulator.
|freerunner, meetings
|Friedrichshain
|group order
|
|
|-
|[[User:philippt|philippt]]
|coding (java, python, perl, bash), linux stuff
|want to have a really smart phone
|Friedrichshain
|interested in group order, knowledge sharing and real-life experience with freerunner
|
|
|-
|[[User:ogai|ogai]]
|coding (java, groovy), linux stuff
|want to have a really smart phone
|Prenzlauer Berg
|interested in group order, knowledge sharing and real-life experience with freerunner
|
|
|-
|[[User:carcinoma|carcinoma]]
|coding (c++, progress), linux, Design
|free me from proprietary tools
|Weissen See (Pankow)
|interested in knowledge sharing, freetime usage, usage in Job/Professional
|Get GTA02 from Pulster, next big order will be mine(25.7.)
|
|-
|[[User:Ott--|ott--]]
|coding, Linux, even Windows
|I want to be free
|Schmöckwitz (Köpenick)
|interested in group order
|
|
|-
|[[User:dk|dk]]
|java
|Gta02
|moabit
|interested in group order
|
|
|-
|[[User:relet|relet]]
|code
|would read your feed
|moabit
|
|soon
|nak
|-
|...
|
|
|
|
|
|
|}

=== Meetings, Events ===
Meeting language is German ;-)
{|border=1
!Date
!Location
!Topic
!Who
|-
|8.-12. August 2007
|Flugplatz Finowfurt
|[https://events.ccc.de/camp/2007/Intro/ Chaos Communication Camp 2007] und [http://events.ccc.de/camp/2007/GSM_Village GSM Village]
|?
|-
|23.08.2007 / 18:00
|[https://berlin.ccc.de/wiki/CCC_Berlin CCCB] / [https://berlin.ccc.de/wiki/Club_Discordia Club Diskordia]
|First meeting. bring your hardware
|Roh, pH5, [[User:Minime|tim]](+ 2?), ? (please add yourself)
|-
|09.07.2008 / 20:00
|[http://wiki.c-base.org/coredump/WaveLoeten c-base (zusammen mit dem Freifunkertreffen)]
|Freerunner Release / Hands On
|[[User:Kriss kriss]], ? (please add yourself)
|}

[[Category:Community]]
[[Category:Openmoko Local Groups]]

Talk:Openmoko Local Groups: Berlin

2008-07-04T10:40:15Z

Kriss: /* Vorschlag Neuer Treffpunkt */

== Sammelbestellung ==

wer die Idee mit der Sammelbestellung noch nicht aufgegeben hat:

"Die Münchner Firma [http://www.handheld-linux.com/wiki.php?page=Neo%20Freerunner Goldelico] bietet Freerunner an. Die Goodies aus dem 10-Pack sind mit dabei und es gibt auch Gruppenrabatt. 1-4 Freerunner - 349 Euro 5-9 Freerunner - 332 Euro 10+ Freerunner - 314 Euro
Whoever: Ich würde vorschlagen bei den Preisen die Auslandsbestellung zu vergessen, da wir damit max. 10 Euro pro Freerunner sparen können. Im Gegenzug fallen aber alle Risiken weg. Ich habe schon mit der Firma telefoniert. Bei einer 10er Bestellung läuft die Abwicklung auch über einen einzigen Besteller. Geld einsammeln und Freerunner verteilen wäre also weiterhin bei einer Person. "
auszug http://wiki.openmoko.org/wiki/Openmoko_Local_Groups:_Munich

also ab 10 leuten gibts freerunner + tasche + head set für 314€/person!
ist auf jeden fall besser als direkt in china zu kaufen und bis jetzt das billigste Angebot in Deutschland!(das mir bekannt ist) ;)

--[[User:govindas|govindas]] 20:18, 27 June 2008 (UTC)

Bei [http://www.pulster.de/ pulster.de] soll '''ein''' Stück 299,- € kosten. Nach einer Sammelbestellung habe ich noch garnicht gefragt. Die nächste Lieferung gibt es aber erst ab dem 25.7.2008. Ich weiß nicht, ob ich das noch so lange durchhalte.

--[[User:Ott--|Ott--]] 14:11, 2 July 2008 (UTC)

----

== Vorschlag Neuer Treffpunkt ==

hi.

ich schlage vor sich einfach am mittwoch abends in der c-base http://c-base.org/ zu treffen. zeitgleich mit den freifunkern. embedded linux und wifi devices bietet genauso wie eine bar mit bier und genug platz denke ich das passende ambiente.

--[[User:Roh|Roh]] 23:58, 26 June 2008 (UTC)

hört sich gut an!
pulster.de will ab dem 5.7. liefern - erstes treffen 9.7.?? ;)

--[[User:govindas|govindas]] 12:18, 27 June 2008 (UTC)

bin auch dafür --[[User:Torsten Grote|Torsten Grote]] 10:57, 27 June 2008 (UTC)

Jo, da wär ich auch dabei. Seh ich das richtig, daß einige von Euch schon stolze Besitzer sind?
--[[User:philippt|philippt]] 16:06, 27 June 2008 (UTC)

zwangslaeufig ;)
ich brings naechsten mittwoch einfach mal mit (mit fso milestone im nand)
--[[User:Roh|Roh]] 06:19, 2 July 2008 (UTC)
btw, das is heute.--[[User:Roh|Roh]] 06:27, 2 July 2008 (UTC)

grrr...heute klappt bei mir nicht, aber ich schreib mir mal nächsten Mittwoch in den Kalender meines mittlerweile verabscheuungswürdig primitiven Mobiltelefons. --[[User:philippt|philippt]] 19:00, 2 July 2008 (UTC)

== Erstes c-base-Treffen ==

<center>

'''09.07.2008 in der c-base'''

{| border=1
!Wer
!Wahrscheinlichkeit
!Neo1973
!Freerunner
|-
|[[User:Kriss|kriss]]
|75%
|1-2
|0
|-
|free
|?
|?
|?
|}

</center>

== Stammtisch eingeschlafen? ==

Hallo ihr,

wenn ich mir diese discussion Seite anschaue, scheint mir das ziemlich eingeschlafen zu sein.

Hätte den jemand Lust an irgendeinem hier erwähnten Ort einen Stammtisch mal abzuhalten und nach dem persönlichen Kennenlernen weitere Entwicklungen zu koordinieren?

----

== Stammtisch Berlin ==

Ich könnte mir einen Stammtisch vorstellen oder ein regelmäßiges Treffen.

Ich habe halt keine GTA01Bv4 und werd sie mir auch nicht kaufen können weil ich mir nur GTA02 oder GTA01Bv4 holen kann und die Wahl dann auf GTA02 fällt.... ;-)

Trotzdem würde ich gerne an der Entwicklung jetzt schon mitmachen, das fällt allerdings doch schwer ohne je einmal einen Neo in der Hand gehalten zu haben (Motivation...).

Zumal sich [[Bluetooth_powered_Multi-SIM_support|manche]] Sachen halt nur mit Gerät programmieren lassen...

Soweit ich informiert bin, war schon vor dem Developer launch in Berlin mindestens 2 Geräte vorhanden, bzw. eine kleine Entwicklervormacht.

Comments? --[[User:Minime|Minime]] 16:32, 13 July 2007 (CEST)

Openmoko under QEMU

2008-05-01T23:08:17Z

Kriss: /* Setting up USB connection */ Kernel 2.6.25 - "USB Network Adapters" now in " Network device support"

QEMU can be used in at least three ways to run [[Openmoko]]. Depending on the purpose that you are going to use the emulator for, you should decide on the target platform.

*''PC'' - Openmoko can be built to run on regular i386 hardware, 32- or 64-bit and this is probably the fastest way to get OpenMoko running if you want to get an impression of how it looks. In this scenario QEMU would only serve for isolating your [[OpenMoko]] installation from your normal system, or, if you're not on a UNIX system, QEMU provides a non-intrusive way to get Linux up quickly. More information can be found in the [[FAQ]] and [[Getting Openmoko working on host with Xoo|here]].

*''Integrator/CP'' - this is the default ARM-based machine that QEMU knows about. This target is used with MACHINE="qemuarm" and it is sufficient to run the original OpenMoko rootfs image, although it doesn't emulate any of the [[:Category:Neo1973 Hardware | Neo1973 Hardware]] except the very CPU core. Read more in the [[FAQ#Q:_Is_there_an_emulator_available_for_OpenMoko.3F|FAQ]].

*''Neo1973'' - the QEMU tree available from OpenMoko repositories is also capable of emulating most of the actual [[Neo1973]] (GTA01) hardware, although not all of it. Additionally, Neo FreeRunner emulation is a work-in-progress. When all of the emulator parts are more mature our code is going to be submitted and merged to the main QEMU development tree.

== Neo1973 emulation ==

This target will (obviously) run original OpenMoko rootfs images, but then it should also be able to run the original u-boot and kernel images, the same ones that a real Neo1973 (GTA01) uses. Among other differences you will notice between this approach and the Integrator/CP target is you also get correct screen resolution, some (fake) battery readings, and other goodness. Currently missing parts of the GTA01 emulator are: [[Hardware:AGPS|AGPS]] and [[Bluetooth]] - these things will still be worked on, as well as general usability. Even with these things missing, QEMU should provide substantial help in debugging kernel and u-boot issues to developers.

What QEMU can '''*not*''' be used for, and probably no other emulator can, is speed measures and getting the general feel of OpenMoko performance. Code running in qemu runs with the maximum speed your host computer can provide with an overhead of translating target code to host code, and this overhead is not uniform across different instructions. This means that even if your virtual Neo reports near 100 BogoMIPS (which is the speed of a real Neo), different actions performed in the emulator will not run with the same speed. On most PCs you will notice the virtual Neo running faster than a real one (Audio related operations may be one of the exceptions).

=== What hardware is supported ===

Rough status for each of the components that need emulation, following the outline of [[:Category:Neo1973 Hardware | Neo1973 Hardware]] page.
{|
! Hardware !! Status !! Usage notes
|- style="background-color:#eeeedd;"
! colspan="3"|S3C2410A Processor
|-
|ARM920T core || Works || Already in mainline QEMU.
|-
|Basic guts || Work || This includes GPIO interface, DMA, Interrupt Controller, Timers, NAND controller, MMC/SD host, [[I2C]] and IIS interfaces, Memory & Clock & Power management controllers, RAM.
|-
|Serial ports || Works || Use the "-serial" switch (maybe be specified multiple times) to tell QEMU where serial input/output should go to. GSM module will be connected on UART0.
|-
|RTC || Works || On start QEMU will load it with current time/date - the Neo1973 [[kernel]] doesn't use it for time/date source currently.
|-
|SPI || Works || The guest kernel can drive it using either the SPI interface or raw GPIO bitbanging.
|-
|LCD || Works || The virtual LCD will display contents in QEMU window unless "-nographic" is specified on command line.
|-
|ADC || Works || Mouse events in QEMU window generate what would be touchscreen events on a Neo1973 and are passed to the guest OS through the on-chip ADC.
|-
|OHCI USB || Works || This part is in mainline QEMU. Use the "-usb" switch to enable the controller and "usb_add" in QEMU monitor to attach new virtual or physical USB devices.
|-
|Slave USB || Works || Linux's dummy HCD in conjunction with gadget filesystem API is used to make the virtual Neo appear as a real one connected to the host computer. See [[#Setting up USB connection|Setting up USB connection]] below. (Experimental)
|-
|Watchdog || Works || This is one of the less important on-chip peripherals in S3C2410. It is however used by Linux for rebooting the board.
|- style="background-color:#eeeedd;"
! colspan="3"|[[I2C]] bus peripherals
|-
|[[PCF50606]] || Works || (Aka PMU) Fakes the battery charge level (set at 88%), POWER button, etc. Also contains an RTC, also unused by Linux.
|-
|[[LM4857]] || Works
|-
|[[WM8753L]] || Works || The CODEC is also connect to the CPU's IIS port. Basic [[Neo1973 Audio Subsystem|audio functionality]] is supported - see QEMU documentation on getting audio input/output from the emulator. Volume control has no effects.
|- style="background-color:#eeeedd;"
! colspan="3"|Other peripherals
|-
|NAND Flash || Works || However, some pieces are not confirmed to be completely compatible with the real hardware because of lack thereof. Use "-mtdblock flashimagefilenamehere" switch to point QEMU to your flash image. The file should be at least 69206016 bytes big.
|-
|JBT6K74-AS(PI) || Works || (Aka LCM) Wired to the SPI channel 1
|-
|Buttons || Work || Enter is the AUX button, Space is the POWER button. Wired to on-chip GPIO and PCF50606.
|-
|SD card || Works || This part is already in mainline QEMU. Use the "-sd cardimagegoeshere" switch to point QEMU to the card image. The regular QEMU monitor commands for removable media can also be used. The card works, however the on-chip host controller gave block length errors on heavy I/O despite working as described in specification. I suspect the kernel driver. DMA operation is not tested.
|-
|Bluetooth
|style="background-color:#ffffcc;"|Works
|A generic Bluetooth HCI (just like the BlueCore4 chip) is connected to internal USB hub (just like the Delta DBFM dongle). Currently qemu emulates no other bluetooth devices, so the dongle behaves as if there was no BT-enabled slaves around, being the only device on the piconet, i.e. is not really useful. Likely a Bluetooth keyboard will be emulated. A physical Bluetooth dongle can also be attached to the emulator (see USB documentation in QEMU).
|-
|[[GSM]] || Works || A fake modem is connected to UART0 understanding a (currently quite limited) subset of AT commands. Ultimately it should support as much functionality as possible (basic AT command set, fake GPRS connections, dialing and SMS send/receive). This way all parts of the phone subsystem (CALYPSO, TWL3014, TRF6151) will not have to be emulated. There is a possibility to wire a real GSM modem to QEMU's serial port, or the [http://doc.trolltech.com/qtopia-4.3-snapshot/fd-ModemSimulator.html phonesim] modem simulator from the ''Qtopia'' project (use the --enable-phonesim switch to ./configure) as well as the [http://doc.trolltech.com/qtopia-4.3-snapshot/modem-emulator.html atinterface] modem emulator, also from Qtopia.
|-
|[[Hardware:AGPS|AGPS]]
|style="background-color:#ffcccc;"|To Do
|There are obvious difficulties emulating the chip, but hopefully it can be made to present the guest OS with some fixed coordinates later when more is known about the chip. Again a real chip could be connected to QEMU's serial port.
|}

Current development is aiming for [[:Category:Neo1973_Hardware#GTA01Bv4 | GTA01Bv4]] compatibility; [[:Category:Neo1973_Hardware#GTA01Bv3 | earlier revisions]] can also be emulated if needed. The differences between the hardware revisions currently only manifest themselves in GPIO wiring. Hardware emulation is implemented in a clean-room manner using official specifications where possible.

== Neo FreeRunner emulation ==

The second line of OpenMoko phones, the Neo FreeRunner (GTA02) saw various hardware changes and improvements since Neo1973 (GTA01). QEMU has fullest support for the GTA01 (the first model), but partial GTA02 emulation is also planned. This will only include the hardware components which were added in GTA02 and were not present in GTA01:

* The u-blox GPS chip (i.e. raw NMEA protocol).
* The Atheros AR6001 WLAN / WiFi chip (and SDIO bus).
* The two LIS accelerometers.

What that means is that the emulated machine will internally not be exactly like Neo FreeRunner, but will be functionally the same. That in turn means that it needs a custom kernel because it's neither a GTA01 nor GTA02 internally. This kernel source will be provided as part of qemu. The bootloader used will be the GTA01 build of u-boot.

This approach is called paravirtualisation and is often used as an emulation solution for mobile platforms. For a userspace programmer (Application developers) the machine will be visible as a genuine GTA02. For a kernel hacker it will be a custom board.

If there's an initiative among the users, to emulate GTA02 hardware to a bigger extent than explained here, patches / improvements will be always welcome because the QEMU projects seeks to emulate the real hardware and stay always as close as possible to physical hardware (in other words, full emulation is preferred over paravirtualisation in the QEMU upstream).

=== What hardware is supported ===

Below is a rough status information for each of the components.
{|
! Hardware !! Status !! Usage notes
|- style="background-color:#eeeedd;"
! colspan="3"|GTA01 hardware
|-
|Processor, on-chip and external peripherals || Work || See the GTA01 supported hardware chart above. This hardware is at the base of the Neo FreeRunner emualtor. The same usage notes apply.
|- style="background-color:#eeeedd;"
! colspan="3"|GTA02 components
|-
|GPS || Works || A virtual GPS chip is connected to the second serial port of the virtual machine, exactly like on the Neo FreeRunner.
|-
|WLAN
|style="background-color:#ffffcc;"|Partial support
|The Atheros AR6001 (second firmware revision) is emulated to an extent that it gets detected by the kernel SDIO stack and registered as a network interface by the Atheros driver. It doesn't allow for actual network communication yet. The basic SDIO bus emulation is complete.
|-
|Accelerometers || Work || Two dummy accelerometers are connected to the virtual machine's I2C bus. They provide a constant 1G reading at the moment. One improvement idea to be implemented when there's some software available for testing, is to pass Qemu's SDL window movements as input to the virtual accelerometers, i.e. dragging the X window around would generate motion sensor events. These events would be two-dimensional but should be enough for Application developers to test their programs' interactions with the movements.
|}

== How to get it running ==

These instructions talk about the GTA01 emulator (default).

=== Using MokoMakefile ===

This is arguably the easiest way of building qemu-neo1973 since you won't need to deal with the compiling and flashing processes yourself. See [[Using_QEMU_with_MokoMakefile|MokoMakefile]] for details.

If you *just* build QEMU and use the official images by typing "make qemu" only (as opposed to setting up monotone and openembedded and building an entire new image for yourself with MokoMakefile), then the build takes less time than the manual instructions below (since it's all done automatically).

=== Manual setup ===

To obtain the latest source code for the emulator, you will want to do something like the following:
<pre>
$ svn checkout https://svn.openmoko.org/trunk/src/host/qemu-neo1973
$ cd qemu-neo1973
</pre>
Now, we're going to configure and build the emulator (Note [[#Requirements|Requirements]] below):
<pre>
$ ./configure --target-list=arm-softmmu # GCC 3.x will be required, see --cc=
$ make
</pre>
See other available options for the configure script by appending "--help".
Now you should have a working emulator under the name "arm-softmmu/qemu-system-arm". To run OpenMoko you will also need to somehow install OpenMoko on your virtual phone, which is totally clean of any software at this moment. There are several block devices to choose from, the best option is probably to do exactly what the Neo1973 manufacturer does before it ships the device to the final user. This process is described in [[Bootloader]], [[Kernel]], [[NAND bad blocks]] and [[Devirginator]] but you don't need to know all the details. Two scripts are provided to generate a firmware for your phone, as realistic as possible. First run
<pre>$ openmoko/download.sh</pre>
which will look up the list of latest available OpenMoko snapshot builds from buildhost.openmoko.org and choose the most recent [[u-boot]], Kernel, and root filesystem images, and download the images (unless they are already found in the openmoko/ directory). These binaries will be used by the flash.sh script. First make sure you have the netpbm package installed for some graphics conversion utilities. On Ubuntu this can be done by:
<pre>sudo apt-get install netpbm</pre>
Then run:
<pre>$ openmoko/flash.sh</pre>
which runs the emulator, loads u-boot into it and then uses u-boot's capability to program the Flash memory to install all the necessary parts of the system into the virtual Flash. It will also set up all the bootloading process including a boot menu (ENTER is [AUX] and SPACE is [POWER]), splash, u-boot environment and some default kernel parameters. If everything goes OK, the script should print a command which you can use to start using the emulator.

QEMU has '''*tons*''' of commandline switches and things that can be configured. You can look them up in [http://www.qemu.org/user-doc.html QEMU user docs]. You will probably want to use the "-snapshot" switch, among other ones. Saving and restoring emulation state at any point (unrelated to "-snapshot") should work as per QEMU user docs too. In addition the monitor commands "help" and "info" are of great help. The monitor usually sits in second virtual console, thus ctrl-alt-2 and ctrl-alt-1 switch to monitor and back.

=== Pre-built binaries ===

Win32 binaries shipped with firmware can be downloaded from [http://mdk.linux.org.tw/~jserv/openmoko/openmoko-emulator-win32-bin-20070625.zip openmoko-emulator-win32-bin-20070625.zip] ([http://snakesoftruth.com/openmoko-emulator-win32-bin-20070625.zip or a mirror here]). Tested on MS Windows XP and Vista Business.

=== Neo FreeRunner (GTA02) ===

The instructions for running the emulator are the same for FreeRunner, but the final command line to invoke qemu changes. Instead of "-M gta01" as the machine name "-M gta02fake" has to be used.

The kernel supporting GTA02 emulator is obtained by applying the ''openmoko/linux-gta02-pseudo.patch'' patch found in qemu-neo1973 sources, to the 2.6.24 openmoko kernel (vanilla linux-2.6.24 + the openmoko patchset from http://svn.openmoko.org/branches/src/target/kernel/2.6.24.x/patches/). Since the GTA02 kernel support is still under heavy development, please refer to the openmoko/README file contained in qemu-neo1973 sources for the latest instructions on building the kernel.

If a normal OpenMoko kernel is used under Neo FreeRunner emulator, it will simply run as if the machine was a GTA01 and not detect any of the new peripherals.

== Convenient Scripts ==

* openmoko/qemu-auto.sh

launches qemu and opens a unix socket for communication. All additional parameters are passed to qemu. (e.g. openmoko/qemu-auto.sh -nographic launches the virtual machine with no graphics etc.).

* openmoko/qemu-upload.sh <filename>

produces a SD card image with one partition with the given file(s) on it (you can pass a list of files) and inserts it into the phone. The OpenMoko kernel should detect the event and the automounter should mount the partition. openmoko/qemu-auto.sh must be running already. If you pass no parameters, it ejects the media (the OM kernel is too dumb to detect this unfortunately). This will only work with gta01 emulation because gta02 has no SD.

* openmoko/qemu-quit.sh

powers the VM down cleanly.

* openmoko/qemu-gadget.sh

attempts to connect target's S3C USB slave to host's dummy HCD (if present and gadgetfs is mounted).

== Requirements ==

This QEMU tree has only been tested on GNU/Linux. To get graphical (not counting VNC) and/or audio output from the emulator you will need either SDL or Cocoa installed on your computer. To enable audio, see the available switches to the ./configure script.

The scripts that sit in openmoko/ require lynx, wget, python, netpbm and most GNU base utilities installed in standard locations. The netpbm package contains tools necessary for bootsplash image conversion.

All of the build-time and run-time requirements listed in [http://www.qemu.org/user-doc.html QEMU documentation] apply. This includes zlib, etc. On distributions that use binary packages, remember that you need the packages ending in '''-dev''' or '''-devel'''.

== QEMU and GNU debugger ==

QEMU lets you debug operating system kernels and bootloaders like you debug all other programs. To do this you will need a debugger that speaks the GDB remote debugging protocol - [http://sourceware.org/gdb/ GDB] is the obvious choice. Some cross toolchains come with GDB already set up. Otherwise building cross-GDB yourself is quick and easy (compared to building binutils and cross-gcc).

To debug u-boot, load the file "u-boot" into gdb (not "u-boot.bin") that is produced by "make" when building u-boot. To debug a Linux kernel, load the file "vmlinux" from the main source directory into gdb. These files are in ELF format and contain all the symbol information and are not stripped of debugging data until you run "strip" on them, unlike "u-boot.bin" and "Image"/"zImage"/"uImage". Next, tell QEMU to enable the gdbserver by appending the "-s" switch or issuing "gdbserver" in the monitor. Use the command <pre>(gdb) target remote localhost:1234</pre> to make a connection to the emulator. From there you should be able to use all the usual GDB commands, including stepping instructions, setting breakpoints, watchpoints, inspecting stack, variables, registers and more. If gdb is running in the same directory from which it grabbed the ELF executable, the "edit" command should work so you can jump right to the source line which is executing.

== Simple network connection with pppd ==

One simple way to get a network connection from the emulated Neo is via an emulated serial port and [[pppd]]. Add ''-serial vc -serial pty'' to the [[QEMU command line]], and QEMU prints a device name on a line like "char device redirected to /dev/pts/12".

On the Neo side, open a terminal and run the command "pppd nodetach debug /dev/ttySAC1".

On the host computer side, open a root terminal and run the command "pppd nodetach debug 192.168.68.1:192.168.68.2 noauth /dev/pts/12", substituting the actual device name from above.

Now on the host computer side, you should be able to "ping 192.168.68.2" and "ssh root@192.168.68.2".

NB : If you see in pppd trace something like this "Received bad configure-rej: 12 06 00 00 00 00" again and again, you will ping but no application will work. It is probably the compression protocol (ccp) negotiation which fail. Add "noccp" to the two pppd commands like "pppd nodetach debug noccp /dev/ttySAC1".

== Setting up Internet connection for your qemu neo ==
Before you start, you have to have a working pppd or USB connection, ([[#Simple_network_connection_with_pppd|see the previous chapter]] and [[#Setting up USB connection|the next chapter]])

(I assume that your local ip-adress is 192.168.0.100 and your router is 192.168.0.1)

In qemu terminal (or via ssh) type:

<pre>
$ ifdown usb0
$ route add default gw 192.168.68.1
</pre>

Edit /etc/resolv.conf:
nameserver 192.168.0.1

On the host-computer type:

<pre>
$ echo 1 >> /proc/sys/net/ipv4/ip_forward
$ echo 1 >> /proc/sys/net/ipv4/ip_dynaddr

$ modprobe ip_tables
$ modprobe iptable_nat
$ modprobe ipt_MASQUERADE

$ iptables -t filter -F
$ iptables -t nat -F

$ iptables -t filter -P INPUT ACCEPT
$ iptables -t filter -P FORWARD ACCEPT
$ iptables -t filter -P OUTPUT ACCEPT
$ iptables -t nat -P PREROUTING ACCEPT
$ iptables -t nat -P POSTROUTING ACCEPT

$ iptables -t nat -A POSTROUTING -o eth0 -s 192.168.68.0/24 -j MASQUERADE
</pre>

(Where eth0 is your network interface connected to the router)

Thats it - now you can enjoy internet in qemu.

== Setting up USB connection ==

It is possible (although not very straight forward, probably about the complexity of tun-tap networking) to connect the virtual, emulated Neo1973 to the Linux PC on which the emulator is running, and work with it as if a real Neo1973 was plugged into the computer's USB port, but no twiddling with cables is needed. If you're testing your applications on the Neo, it may be worth setting up this kind of connection because it lets you enable normal [[USB_Networking|networking between the PC and the phone and ssh into it]] (which is much more comfortable than typing commands into the OpenMoko's terminal emulator via on-screen keyboard). Here's what you will need in order to get this working:

A Linux host with a 2.6 series kernel. The following drivers compiled-in or in modules: dummy_hcd, gadgetfs, usbnet, cdc_ether. [[Building Gadget USB Module|A detailed guide to building the necessary modules is available (primarily Ubuntu focused).]] Generic instructions follow.

Note that you need root access to perform most actions described here. Here's how to enable the drivers in menuconfig.

Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Gadget Support''' -> '''Support for USB Gadgets'''

Find '''Device Drivers''' -> '''USB support''' -> '''USB Gadget Support''' -> '''USB Peripheral Controller''' and set it to '''Dummy HCD (DEVELOPMENT)'''

Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Gadget Support''' -> '''Gadget Filesystem (EXPERIMENTAL)''' (this one is good to have as a module)

Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Network Adapters''' -> '''Multi-purpose USB Networking Framework'''

(in 2.6.25 (from ???) '''Device Drivers''' -> '''Network device support''' -> '''USB Network Adapters''' -> '''Multi-purpose USB Networking Framework''')

Find and enable '''Device Drivers''' -> '''USB support''' -> '''USB Network Adapters''' -> '''Multi-purpose USB Networking Framework''' -> '''CDC Ethernet support (smart devices such as cable modems)'''

(in 2.6.25 (from ???) '''Device Drivers''' -> '''Network device support''' -> '''USB Network Adapters''' -> '''Multi-purpose USB Networking Framework''' -> '''CDC Ethernet support (smart devices such as cable modems)''')

These last two drivers are the same [[Getting Started with your Neo1973#By using Ethernet emulation over a USB cable|drivers that you need to work with a real Neo over USB network]]. After you've built the drivers, make sure that the copy of kernel headers in /usr/include/linux is up to date. In particular the file /usr/include/linux/usb_gadgetfs.h needs to be present and if your distribution came with headers older than 2.6.18 or so, then you need tell the package manager to update them, or you can do that manually with
<pre> # cp -a /usr/src/linux/include/linux/* /usr/include/linux/</pre>
(assuming that your kernel sources are in /usr/src/linux). It is important that this is done before building qemu because the build system checks if these headers are functional and in case they aren't found it will disable the USB Slave functionality. Run "grep CONFIG_GADGETFS config-host.h" in qemu build directory to make sure that the detection succeeded. If it didn't, correct your linux headers and reconfigure qemu.

After building qemu and before running it, make sure that the modules are loaded into the kernel. I found it useful to load gadgetfs with the following command:
<pre> # modprobe gadgetfs default_uid=1000 # assuming my User ID is 1000</pre>
and added the following line to my /etc/fstab:
<pre>gadget /dev/gadget gadgetfs noauto,user,group 0 0</pre>
Make sure that the mountpoint /dev/gadget exists:
<pre> # mkdir -p /dev/gadget</pre>
After that the rest of the procedure can be performed from your regular user account. Mounting gadgetfs is done with:
<pre> $ mount /dev/gadget</pre>
The "default_uid" parameter changes the ownership on all files under /dev/gadget to your own and since the files there are created and destroyed dynamically, there's no easy way to have that performed by ''udev''. Now running qemu as you usually do but appending "-usb -usbgadget" (in the current version of the [[MokoMakefile]] this is not included) should enable the USB Slave functionality. The qemu monitor commands "info usbslave" and "usb_add gadget" will be useful. The former instruction asks the OS running under the emulator (OpenMoko) to describe its slave features (that's what ''lsusb'' does after a Neo1973 is connected to a PC). You can see the available USB configurations in this command's output. Since gadgetfs allows only one configuration, we will need to choose the desired configuration - most device have only one such configuration, in which case you can use just "usb_add gadget" to connect to host; CDC ethernet devices however usually include a second configuration for RNDIS networking (i.e. Ms Windows compatibility) and so does OpenMoko when using the g_ether driver. Hence, to get this right, wait for OpenMoko to fully boot up and execute the following in QEMU monitor:
<pre>
QEMU 0.9.0 monitor - type 'help' for more information
(qemu) info usbslave
USB2.2 device 1457:5122:
Manufacturer: Linux 2.6.20.7-moko8/s3c2410_udc
Product: RNDIS/Ethernet Gadget
Configuration 0: RNDIS
Configuration 1: CDC Ethernet
(qemu)
(qemu) usb_add gadget:1
</pre>
If qemu gives "couldn't add device gadget:1", double-check that it was built against gadgetfs - the file config-host.h must contain the line "#define CONFIG_GADGETFS 1".

The "1" in "usb_add gadget:N" is the number of the USB configuration that we want to use. If everything went correctly - you can check that in dmesg - you should now have a new network interface called ''usb0'' on the PC, through which you can talk to the OpenMoko running in QEMU:
<pre>
$ dmesg | tail
<6>gadgetfs: bound to dummy_udc driver
<7>hub 3-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
<6>usb 3-1: new high speed USB device using dummy_hcd and address 3
<6>gadgetfs: connected
<7>usb 3-1: default language 0x0409
<7>usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0
<6>usb 3-1: Product: RNDIS/Ethernet Gadget
<6>usb 3-1: Manufacturer: Linux 2.6.20.7-moko8/s3c2410_udc
<6>usb 3-1: configuration #1 chosen from 1 choice
<7>usb 3-1: adding 3-1:1.0 (config #1, interface 0)
<7>usb 3-1:1.0: uevent
<7>cdc_ether 3-1:1.0: usb_probe_interface - got id
<7>cdc_ether 3-1:1.0: status ep3in, 16 bytes period 14
<7>usb 3-1: adding 3-1:1.1 (config #1, interface 1)
<7>usb 3-1:1.1: uevent
$ su -
Password:
# tail /var/log/everything/current
May 8 19:25:32 [kernel] gadgetfs: connected
May 8 19:25:32 [kernel] gadgetfs: disconnected
May 8 19:25:32 [kernel] gadgetfs: configuration #1
May 8 19:25:32 [kernel] usb0: register 'cdc_ether' at usb-dummy_hcd-1, CDC Ethernet Device, 52:e7:eb:76:0a:d0
# lsusb -vvv
Bus 003 Device 003: ID 1457:5122
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1457
idProduct 0x5122
bcdDevice 2.12
iManufacturer 1 Linux 2.6.20.7-moko8/s3c2410_udc
iProduct 2 RNDIS/Ethernet Gadget
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 80
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 7 CDC Ethernet
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 6 Ethernet Networking
bInterfaceProtocol 0
iInterface 5 CDC Communications Control
CDC Header:
bcdCDC 1.10
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Ethernet:
iMacAddress 3 52E7EB760AD0
bmEthernetStatistics 0x00000000
wMaxSegmentSize 1514
wNumberMCFilters 0x0000
bNumberPowerFilters 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 14
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 10 Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 10 Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 4 Ethernet Data
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1

# ifconfig usb0 inet 192.168.0.200 netmask 255.255.255.0
# exit
$ ssh root@192.168.0.202
The authenticity of host '192.168.0.202 (192.168.0.202)' can't be established.
RSA key fingerprint is de:21:87:93:52:1c:6b:c7:69:29:6c:af:66:50:02:02.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.0.202' (RSA) to the list of known hosts.
root@192.168.0.202's password:
root@fic-gta01:~$ uname -a
Linux fic-gta01 2.6.20.7-moko8 #1 PREEMPT Wed Apr 25 11:13:52 UTC 2007 armv4tl unknown
</pre>

== Connecting to the serial port/Communicating with u-boot ==
If you add the option ''-serial telnet:localhost:1200,server'' to QEMU will create a telnet server on port 1200 that you can connect to as the serial port.<br>
This will allow you to experiment with u-boot configuration without risking to brick the real device.<br>
<br>
Please note that QEMU will wait for you to connect to the telnet server at port 1200 before starting the emulation.<br>
(use the command ''telnet localhost 1200'' to establish the connection)

== See also ==
*[[Building Gadget USB Module]] - Helpful guide
*[[Xephyr]] - OpenMoko on i386
*[[Xoo]] - OpenMoko on i386

{{Languages|OpenMoko_under_QEMU}}

[[Category:Application Developer]]
[[Category:Guides]]

Community Member of the Week

2008-04-02T11:29:53Z

Kriss: /* Week 1: Monday, 31 March */ - added vote and text for josch

=Purpose=

Michael Shiloh proposed in a [http://lists.openmoko.org/pipermail/community/2008-March/014580.html mail] to make a poll for the Openmoko "Community Member of the Week".

"The intent is clearly to identify and appreciate those of you who have
made and continue to make substantial contributions, and also to
encourage that extra bit of work required to turn a good application
into an excellent one, with a nicely polished GUI, a well written user
guide, etc."

I'm not sure, how the voting should be handled. However, I want to start with a nomination.

=Nomination=
== Week 1: Monday, 31 March ==
{| border="1"
! Nominee !! Reason !! Votes
|-
| [[User:Kevin_Dean|Kevin]]
| Kevin writes the (almost) daily [[Snapshot_review|Snapshot review]] and reports on the progress and problems of the current software. Since I'm not an owner of a GTA01, I can't test the software by myself. Therefore any information about Openmoko makes the waiting for the Freerunner less bitter. I'm reading the different mailing lists very carefully and come to know of solved bugs and new features. However, Kevin gives with his reviews an impression of the software from a users point of view. And when the Freerunner is released, I hope Kevin will continue with his reviews so I always know what snapshot is safe to use.
|[[USER:Avanc|Avanc]]; [[User:Treviño|Treviño]]; [[User:Iandouglas|Iandouglas]]; [[User:GaidinTS|GaidinTS]]; [[User:Tingo|Tingo]]; [[User:Wedge|Wedge]];[[User:Dolson|Dolson]];[[User:Wurp|Wurp]]
|-
| [[User:JoSch|Josch]]
| Josch has done the really cool hack of getting a full [[debian]] installation, complete with XOrg and touch screen support, up and running on a Neo 1973. Also he is a very active member and site-admin at the #neo1973-germany community.
|[[User:Cb22|Cb22]]; [[User:Jluis|Jluis]]; [[User:Marcel_Moczo|Marcel_Moczo]]; [[User:Gau-net|fgau]]; [[User:Buz|buz]]; [[User:emdete|emdete]]; Dunedan; ctypp;[[User:TRIsoft|TRIsoft]]; [[User:Kriss|kriss]]
|-
| [[User:ScaredyCat|ScaredyCat]]
| ScaredyCat generates his own daily images and publishes them. In these images he "plays around" with alternatives such as the GTK theme. This provides some insight into technical alternatives that can improve Openmoko. He's also quite willing to check for the existance and repeatability of bugs and is constantly active on IRC.
|[[User:Kevin_Dean|Kevin Dean]]
|-
| example nominee
| project description
| voter a; voter b; voter c
|-
|}

If you run out of votes in any week, you could look at [[Community_nominees_for_GTA02_P0]] for ideas ...

[[category:Community]]

SettingsGUI

2008-03-16T02:14:50Z

Kriss: Added Project Homepage

{{InProgress}}
[[Image:SettingsGUI-0.8-screen.png|thumb|SettingsGUI - Screen Settings]]
[[Image:SettingsGUI-0.8-audio.png|thumb|SettingsGUI - Audio Settings]]
[[Image:SettingsGUI-0.8-gsm.png|thumb|SettingsGUI - GSM Settings]]
[[Image:SettingsGUI-0.8-gprs.png|thumb|SettingsGUI - GPRS Settings]]
[[Image:SettingsGUI-0.8-bluetooth.png|thumb|SettingsGUI - Blueooth Settings]]

== Overview ==
Until [[OpenMoko]] releases an official GUI-Tool to change settings, SettingsGUI allows you to set various settings of the [[gta01]].

This program is written in [[Python]] using pygtk. It can be used only if those are present in your environment (see [[SettingsGUI#Environment]]).

== Current Features ==

* Screen (Backlight enable/disable, Backlight brightness, Screen Orientation)
* Audio (profile selection, volume, mute, save to profile)
* [[GSM]] (restart [[gsmd]], signal strength, provider, status)
* [[GPRS]] (load and save settings from and to /etc/ppp/peers/, connect, set APN, User, Password, Number)
* [[Bluetooth]] (enable/disable, set-up/monitor PAN connections, scan for peers)

== Planned Features ==

* GSM (Provider selection)
* [[Bluetooth]] (signal strength)
* GPRS (display transfer rate, activate GPRS router)
* [[Battery]] (show capacity, voltage, charger-status)

== Comment on GSM Support ==

* As there are no gsmd python bindings available at the time, SettingGUI uses python-subprocess and threads to communicate to the commandline of [[Gsmd#libgsmd-tool | libgsmd-tool]] for the time being.

* To prevent interference with the GSM modem you have to expicitly power-up and register the modem by toggeling the "GSM State" checkboxes.

* If you manually register to the gsm network (by toggeling the "Register" checkbox) SettingsGUI will sometimes not notice when the connection is established. Just toggle the init checkbox after about 3 seconds. (this seems to be due to a bug in gsmd...)

{{note|From Version 0.7 the atcmd mode of libgsmd-tool is used. To use it revision 2957 (2007-09-12) or later of gsmd is needed. If you have an older version of gsmd - or an older OpenMoko image - use the upgrade function of [[ipkg]], install a newer jffs2 image or use version 0.6 of SettingsGUI.}}

* When the GPRS connection is still active ([[pppd]] running on the system) you should close the connection as gsmd can't start up while pppd is using the modem connection - chose "Yes" in the dialog:

[[Image:SettingsGUI-0.7-close gprs.png|170px]]

== Comment on GPRS Support ==

If you have problems connecting check:

* If the modem is initialized and registered to a network (Start gsmd and register)
* If your login data (mostly APN and User are okay)

* When the gsmd still running you should close the connection as gsmd will interfere with pppd - chose "Yes" in the dialog:

[[Image:SettingsGUI-0.7-terminate-gsmd.png|150px]]

The connection will be terminated when you quit the application.
However saved peer configurations can be called independently using:

pppd debug call gprs # where gprs is the peer

Default configuration files are defined in GlobalConfiguration.py. The peer configuration, a connect- and disconnect chat script are written to /etc/ppp/peers/ on first startup if you don't already have a peer in /etc/ppp/peers/. When the connect button is pressed SettingsGUI will create latest_* files in /etc/ppp/peers/ and start the pppd with this latest_* peer.

SettingsGUI also brings a default Nameserver in case you don't have a valid /etc/resolve.conf. The IP is from the OpenDNS Project and will only work if your GPRS provider allows DNS access to this server.

If you have to change anything else than APN, user, password or dial in number for your provider please leave a note at the Discussion Page.

For details and background information on GPRS see [[Manually using GPRS]].

== Comment on Bluetooth Support ==

With SettingsGUI you can only connect using PAN. Due to display real estate problems Version 0.8 does not support HID pairing yet.

The IP address for your PAN connection will be generated from a configurable mask (see GlobalConfiguration.py) and the last byte of the Bluetooth Address (think of MAC address). Default IP is 10.0.0.x.

For details and background information on Bluetooth see [[Manually using Bluetooth]].

== Download ==
=== Releases ===
{|border=1
! Version
! Download
! Release Focus
! Release Date
|-
| 0.8 ('''current''')
| [http://mput.de/~kristian/.openmoko/settingsgui-0.8.tar.bz2 settingsgui-0.8.tar.bz2]
| bluetooth settings, reorganized package structure ("settingsgui" python package included, startscript is named "settings" now)
| 2008-03-16
|-
| 0.7b
| [http://mput.de/~kristian/.openmoko/settingsgui-0.7b.tar.bz2 settingsgui-0.7b.tar.bz2]
| bugfix on GSM page, bug prevented detection of gsmd connection (emerged with libgsmd-tool update)
| 2007-10-02
|-
| 0.7
| [http://mput.de/~kristian/.openmoko/settingsgui-0.7.tar.bz2 settingsgui-0.7.tar.bz2]
| cleanups, using AT mode, distutils, ATDT -> ATD
| 2007-09-21
|-
| 0.6
| [http://mput.de/~kristian/.openmoko/SettingsGUI-0.6.tar.gz SettingsGUI-0.6.tar.gz]
| audio settings (mute, save), gprs settings (all new)
| 2007-09-06
|-
| older
| [http://mput.de/~kristian/.openmoko/ Directory listing]
|}
=== SVN ===
Access the current SVN version at: http://neo1973-germany.de/svn/SettingsGUI/
=== Packages ===
The Package is now buildable by bitbake. Download the latest .ipk from: [http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/ipk/armv4t/settingsgui_0.7+0.8-beta-r0_armv4t.ipk settingsgui_0.7+0.8-beta-r0_armv4t.ipk]

Thanks to [[User:Alessandro | Alessandro]] there still is the inofficial .ipk and a .bb file. Have a look at his user site.

== Environment ==

:''For more, see [[Python]].''

The following archives will have to be installed (source packages: python python-pygtk python-pycairo python-pygobject):

* python-core
* python-misc
* python-lang
* python-pygtk
* python-subprocess
* python-threading (should be a dependency of python-subprocess - todo: fix)
* python-pygobject (should be a dependency of python-pygtk - todo: fix)

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

== Installation / Execution ==

=== from package ===
* add Alessandros repository as a [[ipkg]] source

vi /etc/ipkg/alessandro.conf

* insert

src/gz aiurlano-armv4t http://aiurlano.netsons.org/OpenMoko/ipk/armv4t
src/gz aiurlano-all http://aiurlano.netsons.org/OpenMoko/ipk/all

* update your db

ipkg update

* install latest settingsgui

ipkg install settingsgui

=== from source ===
* download file to Neo (e.g. using wget)
* Uncompress tar.bz2 file (e.g. e.g. tar -xjvf file.tar.bz2)
* install:
cd settingsgui-x.x
mv settingsgui settingsgui.py
mkdir settingsgui
mv * settingsgui
mv settingsgui/settingsgui.py ./

* run:
export DISPLAY=:0.0
python settingsgui.py &

=== Comment on Installation ===

From Version 0.7 Python distutils is used. So you could also use the setup.py script to install the package:
python settingsgui-x.x/setup.py install

For Version 0.8beta (I didn't test for 0.7), don't change any names, just unpack and then:
cd settingsgui-x.x
python setup.py install

But to do this you'll also have to install the packages:
python-compile python-devel python-stringold python-distutils

==References==
* [http://www.mput.de/projects/code/settingsgui/ Project Homepage]

[[Category:Software]]
[[Category:Application]]
[[Category:OpenMoko]]
[[Category:Guides]]

SettingsGUI

2008-03-16T01:00:54Z

Kriss: 0.8 - bluetooth settings

{{InProgress}}
[[Image:SettingsGUI-0.8-screen.png|thumb|SettingsGUI - Screen Settings]]
[[Image:SettingsGUI-0.8-audio.png|thumb|SettingsGUI - Audio Settings]]
[[Image:SettingsGUI-0.8-gsm.png|thumb|SettingsGUI - GSM Settings]]
[[Image:SettingsGUI-0.8-gprs.png|thumb|SettingsGUI - GPRS Settings]]
[[Image:SettingsGUI-0.8-bluetooth.png|thumb|SettingsGUI - Blueooth Settings]]

== Overview ==
Until [[OpenMoko]] releases an official GUI-Tool to change settings, SettingsGUI allows you to set various settings of the [[gta01]].

This program is written in [[Python]] using pygtk. It can be used only if those are present in your environment (see [[SettingsGUI#Environment]]).

== Current Features ==

* Screen (Backlight enable/disable, Backlight brightness, Screen Orientation)
* Audio (profile selection, volume, mute, save to profile)
* [[GSM]] (restart [[gsmd]], signal strength, provider, status)
* [[GPRS]] (load and save settings from and to /etc/ppp/peers/, connect, set APN, User, Password, Number)
* [[Bluetooth]] (enable/disable, set-up/monitor PAN connections, scan for peers)

== Planned Features ==

* GSM (Provider selection)
* [[Bluetooth]] (signal strength)
* GPRS (display transfer rate, activate GPRS router)
* [[Battery]] (show capacity, voltage, charger-status)

== Comment on GSM Support ==

* As there are no gsmd python bindings available at the time, SettingGUI uses python-subprocess and threads to communicate to the commandline of [[Gsmd#libgsmd-tool | libgsmd-tool]] for the time being.

* To prevent interference with the GSM modem you have to expicitly power-up and register the modem by toggeling the "GSM State" checkboxes.

* If you manually register to the gsm network (by toggeling the "Register" checkbox) SettingsGUI will sometimes not notice when the connection is established. Just toggle the init checkbox after about 3 seconds. (this seems to be due to a bug in gsmd...)

{{note|From Version 0.7 the atcmd mode of libgsmd-tool is used. To use it revision 2957 (2007-09-12) or later of gsmd is needed. If you have an older version of gsmd - or an older OpenMoko image - use the upgrade function of [[ipkg]], install a newer jffs2 image or use version 0.6 of SettingsGUI.}}

* When the GPRS connection is still active ([[pppd]] running on the system) you should close the connection as gsmd can't start up while pppd is using the modem connection - chose "Yes" in the dialog:

[[Image:SettingsGUI-0.7-close gprs.png|170px]]

== Comment on GPRS Support ==

If you have problems connecting check:

* If the modem is initialized and registered to a network (Start gsmd and register)
* If your login data (mostly APN and User are okay)

* When the gsmd still running you should close the connection as gsmd will interfere with pppd - chose "Yes" in the dialog:

[[Image:SettingsGUI-0.7-terminate-gsmd.png|150px]]

The connection will be terminated when you quit the application.
However saved peer configurations can be called independently using:

pppd debug call gprs # where gprs is the peer

Default configuration files are defined in GlobalConfiguration.py. The peer configuration, a connect- and disconnect chat script are written to /etc/ppp/peers/ on first startup if you don't already have a peer in /etc/ppp/peers/. When the connect button is pressed SettingsGUI will create latest_* files in /etc/ppp/peers/ and start the pppd with this latest_* peer.

SettingsGUI also brings a default Nameserver in case you don't have a valid /etc/resolve.conf. The IP is from the OpenDNS Project and will only work if your GPRS provider allows DNS access to this server.

If you have to change anything else than APN, user, password or dial in number for your provider please leave a note at the Discussion Page.

For details and background information on GPRS see [[Manually using GPRS]].

== Comment on Bluetooth Support ==

With SettingsGUI you can only connect using PAN. Due to display real estate problems Version 0.8 does not support HID pairing yet.

The IP address for your PAN connection will be generated from a configurable mask (see GlobalConfiguration.py) and the last byte of the Bluetooth Address (think of MAC address). Default IP is 10.0.0.x.

For details and background information on Bluetooth see [[Manually using Bluetooth]].

== Download ==
=== Releases ===
{|border=1
! Version
! Download
! Release Focus
! Release Date
|-
| 0.8 ('''current''')
| [http://mput.de/~kristian/.openmoko/settingsgui-0.8.tar.bz2 settingsgui-0.8.tar.bz2]
| bluetooth settings, reorganized package structure ("settingsgui" python package included, startscript is named "settings" now)
| 2008-03-16
|-
| 0.7b
| [http://mput.de/~kristian/.openmoko/settingsgui-0.7b.tar.bz2 settingsgui-0.7b.tar.bz2]
| bugfix on GSM page, bug prevented detection of gsmd connection (emerged with libgsmd-tool update)
| 2007-10-02
|-
| 0.7
| [http://mput.de/~kristian/.openmoko/settingsgui-0.7.tar.bz2 settingsgui-0.7.tar.bz2]
| cleanups, using AT mode, distutils, ATDT -> ATD
| 2007-09-21
|-
| 0.6
| [http://mput.de/~kristian/.openmoko/SettingsGUI-0.6.tar.gz SettingsGUI-0.6.tar.gz]
| audio settings (mute, save), gprs settings (all new)
| 2007-09-06
|-
| older
| [http://mput.de/~kristian/.openmoko/ Directory listing]
|}
=== SVN ===
Access the current SVN version at: http://neo1973-germany.de/svn/SettingsGUI/
=== Packages ===
The Package is now buildable by bitbake. Download the latest .ipk from: [http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/ipk/armv4t/settingsgui_0.7+0.8-beta-r0_armv4t.ipk settingsgui_0.7+0.8-beta-r0_armv4t.ipk]

Thanks to [[User:Alessandro | Alessandro]] there still is the inofficial .ipk and a .bb file. Have a look at his user site.

== Environment ==

:''For more, see [[Python]].''

The following archives will have to be installed (source packages: python python-pygtk python-pycairo python-pygobject):

* python-core
* python-misc
* python-lang
* python-pygtk
* python-subprocess
* python-threading (should be a dependency of python-subprocess - todo: fix)
* python-pygobject (should be a dependency of python-pygtk - todo: fix)

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

== Installation / Execution ==

=== from package ===
* add Alessandros repository as a [[ipkg]] source

vi /etc/ipkg/alessandro.conf

* insert

src/gz aiurlano-armv4t http://aiurlano.netsons.org/OpenMoko/ipk/armv4t
src/gz aiurlano-all http://aiurlano.netsons.org/OpenMoko/ipk/all

* update your db

ipkg update

* install latest settingsgui

ipkg install settingsgui

=== from source ===
* download file to Neo (e.g. using wget)
* Uncompress tar.bz2 file (e.g. e.g. tar -xjvf file.tar.bz2)
* install:
cd settingsgui-x.x
mv settingsgui settingsgui.py
mkdir settingsgui
mv * settingsgui
mv settingsgui/settingsgui.py ./

* run:
export DISPLAY=:0.0
python settingsgui.py &

=== Comment on Installation ===

From Version 0.7 Python distutils is used. So you could also use the setup.py script to install the package:
python settingsgui-x.x/setup.py install

For Version 0.8beta (I didn't test for 0.7), don't change any names, just unpack and then:
cd settingsgui-x.x
python setup.py install

But to do this you'll also have to install the packages:
python-compile python-devel python-stringold python-distutils

[[Category:Software]]
[[Category:Application]]
[[Category:OpenMoko]]
[[Category:Guides]]

File:SettingsGUI-0.8-bluetooth.png

2008-03-16T00:32:22Z

Kriss:

File:SettingsGUI-0.8-gprs.png

2008-03-16T00:32:14Z

Kriss:

File:SettingsGUI-0.8-gsm.png

2008-03-16T00:32:07Z

Kriss:

File:SettingsGUI-0.8-audio.png

2008-03-16T00:31:53Z

Kriss:

File:SettingsGUI-0.8-screen.png

2008-03-16T00:31:31Z

Kriss:

PyPenNotes

2008-03-13T17:13:39Z

Kriss: /* Download */ - Added SVN

{{InProgress}}

[[Image:PyPenNotes-0.3.png|thumb|pyPenNotes 0.3]]

== Overview ==
Little tool to write notes using pen and touchscreen.

This program is written in [[Python]] using pygtk. It can be used only if those are present in your environment (see [[PyPenNotes#Environment]]).

== Current Features ==

* Change color and size of pen
* Change background color (even on used notebook pages)
* Undo
* Save and Restore
** Using the file '''~/.penNotes.strokes_data'''
** You may symlink that to your SD-Card if you like...
* As many Notes as you like
** (1-9999, or no RAM left ;-) )
** 200 simple Notes may take about 10 MByte (should be less with Version 0.3 - so this is a vague estimate)

== Planned Features ==

* Manage different notebooks (choose place to save them)

== Download ==
=== Releases ===
{|border=1
! Version
! Download
! Release Focus
|-
| 0.3b ('''current''')
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.3b.tar.bz2 pyPenNotes-0.3b.tar.bz2]
| bugfix release - ignore non existent strokes-file; speed up strokes-file loading a bit
|-
| 0.3
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.3.tar.bz2 pyPenNotes-0.3.tar.bz2]
| 2nd Toolbar + Togglebutton, Undo, Save, Restore, Autosave/-load on exit and start, serious redraw speed up
|-
| 0.2
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.2.tar.bz2 pyPenNotes-0.2.tar.bz2]
| color, thickness and note selection, notes won't get saved to FLASH yet
|-
| 0.1
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.1.tar.bz2 pyPenNotes-0.1.tar.bz2]
| initial release - can do nothing yet. :-)
|}
=== SVN ===
Access the current SVN version at: http://neo1973-germany.de/svn/pyPenNotes/

== Environment ==

:''For more, see [[Python]].

The following archives will have to be installed (source packages: python python-pygtk python-pycairo python-pygobject):

python-core python-misc python-lang python-pygtk

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

[[Category:Software ]]
[[Category:Applications]]

[[Category:In_progress]]

PyFeedRead

2008-03-13T17:13:33Z

Kriss: /* Download */ - Added SVN

[[Image:PyFeedRead-0.2-feed content-om.png|thumb|pyFeedRead - lists a feed]]

== Overview ==
Little Python tool to read text only RSS feeds. Developed as a proof of concept and by special request it has no intention to replace the [[Feed Reader]].
The initial project goal was to see what can be done in 3 hours of Python programming (see [http://mput.de/~kristian/.openmoko/pyFeedRead-0.1.tar.gz Version 0.1] for the result).

== Download ==
=== Release ===
[http://mput.de/~kristian/.openmoko/pyFeedRead-0.2.tar.gz pyFeedRead-0.2.tar.gz.tar.gz]
=== SVN ===
Access the current SVN version at: http://neo1973-germany.de/svn/pyFeedRead/

== Environment ==
* needs Python, pyGTK and other stuff:

python-core python-misc python-lang python-pygtk python-netclient
[[Category:Software ]]
[[Category:Application Developer]]
[[Category:OpenMoko]]

SMSTool

2008-03-13T17:13:29Z

Kriss: /* Download */ - Added SVN

{{InProgress}}
[[Image:SMSTool-0.3.png|thumb|SMSTool - SMS Tool]]

== Overview ==
Until OpenMoko releases an official GUI-Tool to send SMS you can use SMSTool for that task.

This programm is written in Python using pygtk. It can be used only if those are present in your environment.

(see [[SMSTool#Environment]])

== Current Features ==

* Send SMS
** The default number is mine. - Leave a message if you like. ;-) --[[User:Kriss|kriss]] 22:54, 9 September 2007 (CEST)

== Planned Features ==

* Receive SMS
* Move to python-gsmd

== Comment on GSM Support ==

* As there are no gsmd python bindings available at the time, SMSTool uses python-subprocess and threads to communicate to the commandline of [[Gsmd#libgsmd-tool | libgsmd-tool]] for the time being.

We have some basic support for gsmd bindings in python. (Move this to discussion if necessary, apologies for the noise)
http://projects.openmoko.org/plugins/scmsvn/viewcvs.php/?root=python-openmoko -- Sudharsh

== Download ==
=== Release ===
[http://mput.de/~kristian/.openmoko/SMSTool-0.3c.tar.bz2 SMSTool-0.3c.tar.bz2]
=== SVN ===
Access the current SVN version at: http://neo1973-germany.de/svn/SMSTool/
=== Package ===
An SMSTool package is available from the repository at [[User:Alessandro | Alessandro]]'s user page.

== Environment ==

The following archives will have to be installed:

* python-core
* python-misc
* python-lang
* python-pygtk
* python-subprocess
* python-threading (should be a dependency of python-subprocess - todo: fix)
* python-pygobject (should be a dependency of python-pygtk - todo: fix)

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

== Installation / Execution ==

* download file to Neo (e.g. using wget)
* Uncompress tar.gz file (e.g. tar -xzvf file.tar.gz)
* run:
export DISPLAY=:0.0
python SMSTool-x.x/SMSTool.py &

[[Category:Software ]]
[[Category:Application Developer]]
[[Category:In_progress]]

SettingsGUI

2008-03-13T17:13:24Z

Kriss: /* Download */ - Added SVN, Added official Package (thanks to Mickey) - Mirror is offline now

{{InProgress}}
[[Image:SettingsGUI-0.7-screen.png|thumb|SettingsGUI - Screen Settings]]
[[Image:SettingsGUI-0.7-audio.png|thumb|SettingsGUI - Audio Settings]]
[[Image:SettingsGUI-0.7-gsm.png|thumb|SettingsGUI - GSM Settings]]
[[Image:SettingsGUI-0.7-gprs.png|thumb|SettingsGUI - GPRS Settings]]

== Overview ==
Until [[OpenMoko]] releases an official GUI-Tool to change settings, SettingsGUI allows you to set various settings of the [[gta01]].

This program is written in [[Python]] using pygtk. It can be used only if those are present in your environment (see [[SettingsGUI#Environment]]).

== Current Features ==

* Screen (Backlight enable/disable, Backlight brightness, Screen Orientation)
* Audio (profile selection, volume, mute, save to profile)
* [[GSM]] (restart [[gsmd]], signal strength, provider, status)
* [[GPRS]] (load and save settings from and to /etc/ppp/peers/, connect, set APN, User, Password, Number)

== Planned Features ==

* GSM (Provider selection)
* [[Bluetooth]] (device scanning, connection, signal strength)
* GPRS (display transfer rate, activate GPRS router)
* [[Battery]] (show capacity, voltage, charger-status)

== Comment on GSM Support ==

* As there are no gsmd python bindings available at the time, SettingGUI uses python-subprocess and threads to communicate to the commandline of [[Gsmd#libgsmd-tool | libgsmd-tool]] for the time being.

* To prevent interference with the GSM modem you have to expicitly power-up and register the modem by toggeling the "GSM State" checkboxes.

* If you manually register to the gsm network (by toggeling the "Register" checkbox) SettingsGUI will sometimes not notice when the connection is established. Just toggle the init checkbox after about 3 seconds. (this seems to be due to a bug in gsmd...)

{{note|From Version 0.7 the atcmd mode of libgsmd-tool is used. To use it revision 2957 (2007-09-12) or later of gsmd is needed. If you have an older version of gsmd - or an older OpenMoko image - use the upgrade function of [[ipkg]], install a newer jffs2 image or use version 0.6 of SettingsGUI.}}

* When the GPRS connection is still active ([[pppd]] running on the system) you should close the connection as gsmd can't start up while pppd is using the modem connection - chose "Yes" in the dialog:

[[Image:SettingsGUI-0.7-close gprs.png|170px]]

== Comment on GPRS Support ==

If you have problems connecting check:

* If the modem is initialized and registered to a network (Start gsmd and register)
* If your login data (mostly APN and User are okay)

* When the gsmd still running you should close the connection as gsmd will interfere with pppd - chose "Yes" in the dialog:

[[Image:SettingsGUI-0.7-terminate-gsmd.png|150px]]

The connection will be terminated when you quit the application.
However saved peer configurations can be called independently using:

pppd debug call gprs # where gprs is the peer

Default configuration files are defined in GlobalConfiguration.py. The peer configuration, a connect- and disconnect chat script are written to /etc/ppp/peers/ on first startup if you don't already have a peer in /etc/ppp/peers/. When the connect button is pressed SettingsGUI will create latest_* files in /etc/ppp/peers/ and start the pppd with this latest_* peer.

SettingsGUI also brings a default Nameserver in case you don't have a valid /etc/resolve.conf. The IP is from the OpenDNS Project and will only work if your GPRS provider allows DNS access to this server.

If you have to change anything else than APN, user, password or dial in number for your provider please leave a note at the Discussion Page.

For details and background information on GPRS see [[Manually using GPRS]].

== Download ==
=== Releases ===
{|border=1
! Version
! Download
! Release Focus
|-
| 0.7b ('''current''')
| [http://mput.de/~kristian/.openmoko/settingsgui-0.7b.tar.bz2 SettingsGUI-0.7b.tar.bz2]
| bugfix on GSM page, bug prevented detection of gsmd connection (emerged with libgsmd-tool update)
|-
| 0.7
| [http://mput.de/~kristian/.openmoko/settingsgui-0.7.tar.bz2 SettingsGUI-0.7.tar.bz2]
| cleanups, using AT mode, distutils, ATDT -> ATD
|-
| 0.6
| [http://mput.de/~kristian/.openmoko/SettingsGUI-0.6.tar.gz SettingsGUI-0.6.tar.gz]
| audio settings (mute, save), gprs settings (all new)
|-
| older
| [http://mput.de/~kristian/.openmoko/ Directory listing]
|
|}
=== SVN ===
Access the current SVN version at: http://neo1973-germany.de/svn/SettingsGUI/
=== Packages ===
The Package is now buildable by bitbake. Download the latest .ipk from: [http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/ipk/armv4t/settingsgui_0.7+0.8-beta-r0_armv4t.ipk settingsgui_0.7+0.8-beta-r0_armv4t.ipk]

Thanks to [[User:Alessandro | Alessandro]] there still is the inofficial .ipk and a .bb file. Have a look at his user site.

== Environment ==

:''For more, see [[Python]].''

The following archives will have to be installed (source packages: python python-pygtk python-pycairo python-pygobject):

* python-core
* python-misc
* python-lang
* python-pygtk
* python-subprocess
* python-threading (should be a dependency of python-subprocess - todo: fix)
* python-pygobject (should be a dependency of python-pygtk - todo: fix)

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

== Installation / Execution ==

=== from package ===
* add Alessandros repository as a [[ipkg]] source

vi /etc/ipkg/alessandro.conf

* insert

src/gz aiurlano-armv4t http://aiurlano.netsons.org/OpenMoko/ipk/armv4t
src/gz aiurlano-all http://aiurlano.netsons.org/OpenMoko/ipk/all

* update your db

ipkg update

* install latest settingsgui

ipkg install settingsgui

=== from source ===
* download file to Neo (e.g. using wget)
* Uncompress tar.bz2 file (e.g. e.g. tar -xjvf file.tar.bz2)
* install:
cd settingsgui-x.x
mv settingsgui settingsgui.py
mkdir settingsgui
mv * settingsgui
mv settingsgui/settingsgui.py ./

* run:
export DISPLAY=:0.0
python settingsgui.py &

=== Comment on Installation ===

From Version 0.7 Python distutils is used. So you could also use the setup.py script to install the package:
python settingsgui-x.x/setup.py install

For Version 0.8beta (I didn't test for 0.7), don't change any names, just unpack and then:
cd settingsgui-x.x
python setup.py install

But to do this you'll also have to install the packages:
python-compile python-devel python-stringold python-distutils

[[Category:Software]]
[[Category:Application]]
[[Category:OpenMoko]]
[[Category:Guides]]

Video Player

2008-02-22T00:03:45Z

Kriss: /* Playback using 480x640 / 640x480 */

Not a proper 'app' page, just an overview of my understanding. --[[User:Speedevil|Speedevil]] 17:39, 16 February 2007 (CET)

----

Video is problematic.

On the minus side.
*The CPU is certainly not fast enough to decode 480*640 video.
*The display is portrait, which means that an additional rotation step is needed for most landscape video, adding to CPU usage.
*Downloading an arbitrary video, and playing it without transcoding it, then playing it later will not be possible.
However.

On the positive side.
*The LCD can be switched to a 240*320 stretch mode, which is much less taxing.
*Re-encoding video to rotate it, and scale to 320*240, and encoding with a low CPU use codec such as MPEG-1 may well make half-screen doubled videos playable at 25fps.
*If not, then it almost certainly will be possible at 12fps.
*Playing most very small - postage stamp - videos as are sent by many phones should be possible.
*1G of storage should give several hours of mpeg4 video, as the quality can be reduced somewhat without being visible on the screen.

From a conversation with XorA, in the [irc://freenode.com/#openmoko IRC channel].

400kbps mpeg4 works on a 200Mhz neo (without sound) on prerotated 240*320 ffmpeg codec videos, at 25fps, using stock mplayer.

With sound, this drops to 18fps.

There are optimisations for mplayer that look promising to get 25fps with sound.

For switching between QVGA and VGA mode do the following with a compatible kernel:
chvt 4 && echo qvga-normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset qvga
vice versa:
echo normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset vga && chvt 3
taken from http://lists.openmoko.org/pipermail/neo1973-hardware/2007-October/000267.html

To make your videos/DVDs neo1973 compatible use mencoder like this:
Find out the -vf cropping parameters with
mplayer input.avi -vf cropdetect
let it run a few seconds and insert the given cropping values into this command
mencoder input.avi -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output2.avi
To encode a DVD first find out the -vf cropping parameters with
mplayer -dvd-device /path/to/dvd dvd:// -vf cropdetect -sb 50000000
let it run a few seconds and insert the given cropping values into this command
mencoder -dvd-device /path/to/dvd dvd:// -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output.avi
This will rotate the video/DVD, scale it and encode it to mpeg4 with a bitrate of 300kBit/s. Works like a charm.

To avoid console blanking type
echo -e '\033[9;0]' > /dev/ttyX
where 'X' is your terminal number - for example if you did chvt 4 then /dev/tty4 is your terminal.

To avoid kernel output in vt do
echo 0 > /proc/sys/kernel/printk

== Playback using 480x640 / 640x480 ==

To get best speed on GTA01 (best size-speed-resolution-codec trade-off I could find - doesn't mean it's perfect though) crosscode using:
mencoder <sourcefile> -o <targetfile.avi> -ofps 13 -vf scale -zoom -xy 240 -af channels=1:0:0:1:0 -oac lavc -ovc lavc -lavcopts acodec=mp3:vcodec=h263p:autoaspect=1:vbitrate=300:abitrate=32

Also working okay:
mencoder <sourcefile> -o <targetfile.avi> -ofps 13 -vf scale -zoom -xy 352 -af channels=1:0:0:1:0 -oac lavc -ovc lavc -lavcopts acodec=mp3:vcodec=h263p:autoaspect=1:vbitrate=200:abitrate=32

You can playback the file using:
mplayer -sws 0 -nodouble -vo sdl -fs -framedrop <tagetfile.avi>

You may also want to use:
-autosync 30 -vf scale -zoom -xy 640 -vf rotate=1

[[Category:Software]]
[[Category:Neo1973 Hardware]]

Video Player

2008-02-21T23:49:54Z

Kriss: /* Playback using 480x640 / 640x480 */

Not a proper 'app' page, just an overview of my understanding. --[[User:Speedevil|Speedevil]] 17:39, 16 February 2007 (CET)

----

Video is problematic.

On the minus side.
*The CPU is certainly not fast enough to decode 480*640 video.
*The display is portrait, which means that an additional rotation step is needed for most landscape video, adding to CPU usage.
*Downloading an arbitrary video, and playing it without transcoding it, then playing it later will not be possible.
However.

On the positive side.
*The LCD can be switched to a 240*320 stretch mode, which is much less taxing.
*Re-encoding video to rotate it, and scale to 320*240, and encoding with a low CPU use codec such as MPEG-1 may well make half-screen doubled videos playable at 25fps.
*If not, then it almost certainly will be possible at 12fps.
*Playing most very small - postage stamp - videos as are sent by many phones should be possible.
*1G of storage should give several hours of mpeg4 video, as the quality can be reduced somewhat without being visible on the screen.

From a conversation with XorA, in the [irc://freenode.com/#openmoko IRC channel].

400kbps mpeg4 works on a 200Mhz neo (without sound) on prerotated 240*320 ffmpeg codec videos, at 25fps, using stock mplayer.

With sound, this drops to 18fps.

There are optimisations for mplayer that look promising to get 25fps with sound.

For switching between QVGA and VGA mode do the following with a compatible kernel:
chvt 4 && echo qvga-normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset qvga
vice versa:
echo normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset vga && chvt 3
taken from http://lists.openmoko.org/pipermail/neo1973-hardware/2007-October/000267.html

To make your videos/DVDs neo1973 compatible use mencoder like this:
Find out the -vf cropping parameters with
mplayer input.avi -vf cropdetect
let it run a few seconds and insert the given cropping values into this command
mencoder input.avi -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output2.avi
To encode a DVD first find out the -vf cropping parameters with
mplayer -dvd-device /path/to/dvd dvd:// -vf cropdetect -sb 50000000
let it run a few seconds and insert the given cropping values into this command
mencoder -dvd-device /path/to/dvd dvd:// -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output.avi
This will rotate the video/DVD, scale it and encode it to mpeg4 with a bitrate of 300kBit/s. Works like a charm.

To avoid console blanking type
echo -e '\033[9;0]' > /dev/ttyX
where 'X' is your terminal number - for example if you did chvt 4 then /dev/tty4 is your terminal.

To avoid kernel output in vt do
echo 0 > /proc/sys/kernel/printk

== Playback using 480x640 / 640x480 ==

To get best speed on GTA01 (best size-speed-resolution-codec trade-off I could find - doesn't mean it's perfect though) crosscode using:
mencoder <sourcefile> -o <targetfile.avi> -ofps 13 -vf scale -zoom -xy 240 -af channels=1:0:0:1:0 -oac lavc -ovc lavc -lavcopts acodec=mp3:vcodec=h263p:autoaspect=1:vbitrate=300:abitrate=32

You can playback the file using:
mplayer -sws 0 -nodouble -vo sdl -fs -framedrop <tagetfile.avi>

You may also want to use:
-autosync 30 -vf scale -zoom -xy 640 -vf rotate=1

[[Category:Software]]
[[Category:Neo1973 Hardware]]

Video Player

2008-02-21T23:41:46Z

Kriss: crosscode and playback for best speed on GTA01 (640x480)

Not a proper 'app' page, just an overview of my understanding. --[[User:Speedevil|Speedevil]] 17:39, 16 February 2007 (CET)

----

Video is problematic.

On the minus side.
*The CPU is certainly not fast enough to decode 480*640 video.
*The display is portrait, which means that an additional rotation step is needed for most landscape video, adding to CPU usage.
*Downloading an arbitrary video, and playing it without transcoding it, then playing it later will not be possible.
However.

On the positive side.
*The LCD can be switched to a 240*320 stretch mode, which is much less taxing.
*Re-encoding video to rotate it, and scale to 320*240, and encoding with a low CPU use codec such as MPEG-1 may well make half-screen doubled videos playable at 25fps.
*If not, then it almost certainly will be possible at 12fps.
*Playing most very small - postage stamp - videos as are sent by many phones should be possible.
*1G of storage should give several hours of mpeg4 video, as the quality can be reduced somewhat without being visible on the screen.

From a conversation with XorA, in the [irc://freenode.com/#openmoko IRC channel].

400kbps mpeg4 works on a 200Mhz neo (without sound) on prerotated 240*320 ffmpeg codec videos, at 25fps, using stock mplayer.

With sound, this drops to 18fps.

There are optimisations for mplayer that look promising to get 25fps with sound.

For switching between QVGA and VGA mode do the following with a compatible kernel:
chvt 4 && echo qvga-normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset qvga
vice versa:
echo normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset vga && chvt 3
taken from http://lists.openmoko.org/pipermail/neo1973-hardware/2007-October/000267.html

To make your videos/DVDs neo1973 compatible use mencoder like this:
Find out the -vf cropping parameters with
mplayer input.avi -vf cropdetect
let it run a few seconds and insert the given cropping values into this command
mencoder input.avi -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output2.avi
To encode a DVD first find out the -vf cropping parameters with
mplayer -dvd-device /path/to/dvd dvd:// -vf cropdetect -sb 50000000
let it run a few seconds and insert the given cropping values into this command
mencoder -dvd-device /path/to/dvd dvd:// -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output.avi
This will rotate the video/DVD, scale it and encode it to mpeg4 with a bitrate of 300kBit/s. Works like a charm.

To avoid console blanking type
echo -e '\033[9;0]' > /dev/ttyX
where 'X' is your terminal number - for example if you did chvt 4 then /dev/tty4 is your terminal.

To avoid kernel output in vt do
echo 0 > /proc/sys/kernel/printk

== Playback using 480x640 / 640x480 ==

To get best speed on GTA01 (best size-speed-resolution-codec trade-off I could find - doesn't mean it's perfect though) crosscode using:
mencoder <sourcefile> -o <targetfile.avi> -ofps 13 -vf scale -zoom -xy 240 -af channels=1:0:0:1:0 -oac lavc -ovc lavc -lavcopts acodec=mp3:vcodec=h263p:autoaspect=1:vbitrate=300:abitrate=32

You can playback the file using:
mplayer -sws 0 -nodouble -vo sdl -fs -framedrop <tagetfile.avi>

[[Category:Software]]
[[Category:Neo1973 Hardware]]

Manually using Bluetooth

2008-02-20T20:19:53Z

Kriss: /* Being able to use HID devices */ + apple wireless keyboard (original)

{{InProgress}}
Bluetooth is one of the core functions of the Neo1973, however it is basically unimplemented on the software side at the moment.
Hardware problems in the P1 phone mean that the CPU has to be active in order to wake on external bluetooth events, which will reduce the battery life to some 2 days at best in standby.

This page details how to use bluetooth from the command line.
We have quite a lot of plans about what exactly Bluetooth should be used for.

== Power it up ==

Power up the adapter by clicking on the bluetooth icon in the top bar and selecting power on.

The old way to do it is a shell command:

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

At the shell, "hciconfig" should print information about the adapter if it powered up properly:

hciconfig

The devices should show as UP. If not you can use

hciconfig <device> up

== Bluetooth Functions ==

===Configuring Bluetooth on OpenMoko 2007.2 (August 27 snapshot with kernel 2.6.21.6-moko11) ===

In file /etc/bluetooth/hcid.conf you should change the passkey from BlueZ to something numeric. For testing you may use "0000". Also, you can set the name to "Neo (%d)".

=== Scanning for bluetooth devices ===

hcitool scan

This will list the addresses of any discoverable bluetooth devices in the vicinity

=== passkey agent example ===

There should be a passkey agent built into openmoko, but for now you can start up the example passkey agent and set the pin code there. This will allow for new pairings to be made when you attempt a connection.

passkey-agent --default 0000 &

Note: the passkey-agent is not required in OpenMoko 2007.2 with kernel 2.6.21.6 as of at least since August 27 (maybe earlier).

=== HID (Human Input Device) ===

==== Being able to use HID devices ====

We want to be able to use a bluetooth keyboard to type into the various applications of our Neo1973.
To use a Bluetooth Keyboard type: (11:22:33:44:55:66 is the Address of your BT-Keyboard)

hidd --connect 11:22:33:44:55:66

and press "Connect" on your BT-KB. Alternately, if you know that only one BT-Keyboard is within range, you can just:

hidd --search

to find and connect to any BT-Keyboard.

Tested on:
* [http://www.logitech.com/index.cfm/products/details/US/EN,CRID=2166,CONTENTID=10717 Logitech Dinovo Edge]
* [http://www.logitech.com/index.cfm/keyboards/keyboard_mice_combos/devices/164&cl=us,en Logitech Dinovo Media Desktop (keyboard)]
* [http://www.nokia.es/A4181580 Nokia SU-8W]. Switched on the BT keyboard, scanned for BT address and ran the connect statement above. Works fine.
* [http://blog.russnelson.com/chordite Chordite]. This keyboard uses the Broadcom BCM2042 BT keyboard controller along with a custom driver.
* [http://www.apple.com/keyboard/ Apple's Aluminum Keyboard]. You may have to add 'auth enable; encrypt enable;' to device {} in hcid.conf. Run the passkey agent the first time. --search works to pair and every time after.
* [http://www.apple.com/support/keyboard/ Apple's white "Wireless Keyboard (original)"] - details may be the same as above. (tested some time ago)
* [http://freedominput.com The freedom keyboard] and its many rebranded models (they look like this: [http://rabenfrost.net/openmoko/keyboard.jpg]) need 'modprobe uinput' to circumvent the 'Can't open input device: No such file or directory (2)' error of 'hidd --search'. It works as of february 7th 2008.
* [http://www.nextag.com/Playstation-3-Logitech-Cordless-564345667/prices-html?nxtg=f8320a24052a-7789F8FE732FF6E3 Logitech Playstation 3 Keyboard] Works well, Mouse pad works.

==== Acting as HID device ====

We want to be able to use the Neo1973 as a HID device, being able to use it as controller for presentations.

=== RFCOMM ===

Here's how to connect to an external Bluetooth GPS and read NMEA data (Tested with a Holux GPSSlim236 and a Nokia LD-3W ).

First, switch on the GPS and identify the BT address:

hcitool scan

Then, edit /etc/bluetooth/rfcomm.conf, which by default has all settings commented out, to something like this:

rfcomm0 {
# Automatically bind the device at startup
bind no;
# Bluetooth address of the device
device 00:11:22:33:44:55;
# RFCOMM channel for the connection (check your GPS docs for details)
channel 1;
# Description of the connection
comment "Bluetooth GPS";
}

Restart the BT services:

root@neo:~$ /etc/init.d/bluetooth stop
root@neo:~$ /etc/init.d/bluetooth start

You should now be able to bind the GPS to /dev/rfcomm0, like this:

root@neo:~$ rfcomm bind 0

Confirm the connect:

root@neo:~$ rfcomm
rfcomm0: 00:11:22:33:44:55 channel 1 clean

... and watch the NMEA strings coming from your GPS:

root@neo:~$ cat /dev/rfcomm0
$GPGGA,111748.000,5907.6964,N,01121.1787,E,1,06,1.2,57.7,M,40.1,M,,0000*6F
$GPRMC,111748.000,A,5907.6964,N,01121.1787,E,0.00,94.94,160807,,,A*50
$GPVTG,94.94,T,,M,0.00,N,0.0,K,A*3D

If you have nothing better to do, you can now pinpoint my office :-).

=== OBEX ===

=== Networking ===

=== Bluetooth networking with a Linux system ===

Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.

On the laptop

* Start bluetooth
elara /home/alphaone # /etc/init.d/bluetooth start

* Start pand as server
elara /home/alphaone # pand -s

* As soon as pand is started on the phone configure your IP address
elara /home/alphaone # ip a add 10.0.0.1/24 dev bnep0
elara /home/alphaone # ip l set bnep0 up

* Configure IP forwarding and masquerading to your liking (see [[USB_Networking]]). You can even set up Udev rules to do this for you once the bnep0 interface appears.

On the Neo

* There is a little script that does the steps below (and retries the pand -c command; I had issues with it not working the first time every time) at [[Bt-net-script]] You shouldn't need the other steps below if you use the script.

* Power on bluetooth (see above)

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

* Connect to the laptop pand
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8

* Configure your IP address
ip a add 10.0.0.2/24 dev bnep0
ip r add default via 10.0.0.1

* Enjoy

=== Bluetooth networking with a MacOS X system ===

Please refer to [[MacOS_X#Bluetooth_2]]

For using the Neo as a dialup Bluetooth server and the Mac as the client, please see below at [[Manually_using_Bluetooth#PPP_Networking]]

=== Bluetooth networking with a Windows XP system ===

This was tested with a Windows XP SP2 on a IBM Thinkpad T41 with the Widcomm BT stack

* Start bluetooth on Windows XP

* Enable "Network Access" in the Bluetooth configuration

* Scan for the Neo and pair with the Neo (right click, select pair)

On the Neo

* Enable PAN support on the Neo by changing Autostart from false to true in /etc/bluetooth/network.service

* Power on bluetooth (see above)

* Scan for the laptop
root@fic-gta01:~$ hcitool scan
Scanning ...
<laptop_bt_address> Thinkpad
...

* Connect to the laptop pand
pand -c <laptop_bt_address> -r PANU -d NAP -e bnep0 -A -E -S
(add '-n' to see the pand status messages until you get it right)

For some reason, I was not able to initiate PAN connections from the Neo, I got 'Permission denied (13)' even when I had explicitly allowed the Neo to connect (right click on Neo icon, set properties, on Authorization tab). But initiating 'PAN User' from Windows worked when executing on Neo:
pand -l -r PANU -d NAP -e bnep0 -A -E -S
(add '-n' to see the pand status messages until you get it right)

* Configure your IP address. It should work like when connecting to Linux:
ip a add 10.0.0.2/24 dev bnep0
ip r add default via 10.0.0.1
If this does not work, the IP stacks may have auto-assigned network addresses to themselves. You can look this up with 'ifconfig' on the Neo and with 'ipconfig' on Windows.

* You should now be able to ssh/putty from Windows to your Neo. Enjoy!
By setting up the Windows Bluetooth connection properly, it should also be possible to share the Internet Connection of the Windows box with the Neo.

=== PPP Networking ===

If you are unable to use the 'BNEP' method described above, you may be able to use [[PPP]] and a DUN (dialup-networking) emulation mode. On the Neo:

* Edit the /etc/default/bluetooth file and set the following options:
RFCOMM_ENABLE=true
DUND_ENABLE=true
DUND_OPTIONS="--listen --persist call dun"

* Create an /etc/ppp/peers/dun file with options like the following:
115200
192.168.2.202:192.168.2.200
passive
local
noipdefault
noauth
nodefaultroute

* Restart bluetooth (/etc/init.d/bluetooth stop ; /etc/init.d/bluetooth start)

To connect from a MacOS 10.3 client:

* Open "Applications/Utilities/Bluetooth Serial Utility"

* Click on "New"

* Choose a name, then click "Choose Device"

* Locate your Neo, then select the "LAN Access Point" service. If your device is not found, or if this service does not show up, then you will need to troubleshoot and fix that before continuing. Bluetooth is designed for short-range communication, so make sure that the devices are physically close to each other.

* Select "Port type: RS-232" and "Show in Network Preferences". Click OK.

* Open the Network Preferences page then "Show: Network Port Configurations". Enable the new device that you defined in the previous step and drag it to the bottom of the device list (so that it will not interfere with your other network connections)

* Choose "Show: <your-device-name>", then click "Modem"

* Select "Null Modem 115200" from the list of available devices. Uncheck "Wait for dial tone" and "Enable error correction and compression in modem". Optionally check "Show modem status in menu bar".

* Click "Connect". If everything worked, you will end up with a 'ppp0' device on your Mac with a local address of 192.168.2.200 and you will be able to access your Neo at 192.168.2.202.

=== A2DP quickie ===

It's now possible (if a little hackish) to stream mp3 to a bluetooth headset. It's a known problem that the playback rate changes (pitch varies). Timing issues are also likely the reason for gaps in playback.

If the bluez packages are recent enough, you can use a shortcut. I'll document it here and leave the longer version below (the long version also demonstrates the API used by the GUI to manage headsets)

Create /etc/asound.conf with your bluetooth headset's address filled in:

pcm.!default {
type bluetooth
device "xx:xx:xx:xx:xx:xx"
}

then play a song

madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay

or for smoother results...

madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:song.wav
aplay song.wav

=== A2DP ===

If that doesn't work... all the more hackish... install required packages:

echo "src/gz python http://www.angstrom-distribution.org/unstable/feed/armv4t/python/" >> /etc/ipkg/angstrom-python.conf
echo "src/gz base http://www.angstrom-distribution.org/unstable/feed/armv4t/base/" >> /etc/ipkg/angstrom-base.conf
ipkg update ; ipkg install python-core python-xml python-dbus bluez-utils bluez-utils-alsa

Create /etc/asound.conf:

pcm.!default {
type bluetooth
}
ctl.!default {
type bluetooth
}
pcm.bluetooth {
type bluetooth
}
ctl.bluetooth {
type bluetooth
}

Run the passkey agent (see above in this page)

Fill in your bluetooth headset address below and execute the python script (with your headset turned on)

#!/usr/bin/python
import dbus
bus = dbus.SystemBus()
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')
conn = manager.ActivateService('audio')
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')
path = audio.CreateDevice('00:0D:3C:44:33:22')
audio.ChangeDefaultDevice(path)
sink = dbus.Interface(bus.get_object(conn, path), 'org.bluez.audio.Sink')
sink.Connect()

FINALLY: play a song

madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay

=== Headset Audio ===

[[Neo1973_Audio_Subsystem]] has detail about alsa settings and a proposal for audio scenario management.

To try this out, follow the instructions in the a2dp section to install software and run the passkey agent.

Remove or disable the stuff you put in asound.conf. When using a voice headset, the application uses the regular system audio device and it gets routed to bluetooth in the codec.

Put the headset in pairing mode. Replace the bluetooth address below with your headset's and run the python script:

#!/usr/bin/python
import dbus
bus = dbus.SystemBus()
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')
conn = manager.ActivateService('audio')
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')
path = audio.CreateHeadset('00:0B:2E:39:33:22')
audio.ChangeDefaultHeadset(path)
headset = dbus.Interface (bus.get_object(conn, path), 'org.bluez.audio.Headset')
headset.Connect()
headset.Play()

Now place a call and try to route it to bluetooth (after it's in progress):

alsactl -f /etc/gsmbluetooth.state restore

You may also be able to listen to system audio given the right state file:

alsactl -f /etc/systembluetooth.state restore
madplay song.mp3

=== Bluetooth networking with a Linux system - More secure way ===

''Check this, probably needs some corrections''

Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.

On the laptop

* check these options in /etc/bluetooth/hcid.conf
security auto;
passkey "your pin";
lm master;

* Start bluetooth
# /etc/init.d/bluetooth start

* Start pand as server
pand --listen --role NAP --encrypt

* Add in /etc/network/interfaces (see [[USB_Networking]])
auto bnep0
iface bnep0 inet static
address 192.168.1.1
netmask 255.255.255.0
network 192.168.1.0
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.1.0/24
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT

On the Neo

* Power on bluetooth (see above)

* Scan for the laptop
root@fic-gta01:~$ hcitool scan
Scanning ...
00:20:E0:5A:FE:C8 laptop

* Set pin
root@fic-gta01:~$ passkey-agent 'your pin' 00:20:E0:5A:FE:C8 &

* Connect to the laptop pand
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8

* Configure your IP address
root@fic-gta01:~$ ifconfig bnep0 192.168.1.2
root@fic-gta01:~$ route add default gateway 192.168.1.1

* Enjoy

== Further reading ==

http://www.holtmann.org/papers/bluetooth/ols2006_slides.pdf
http://wiki.bluez.org/wiki/Audio#org.bluez.Audio

{{Languages|Manually_using_Bluetooth}}
[[Category:Neo1973 Hardware]]
[[Bluetooth]]

Navit

2008-01-31T21:49:25Z

Kriss: /* Setting up Navit */ - osm2navit also in target - typo fixed

http://navit.sourceforge.net/

<div align="center">[[Image:Screenshot-3.png | Navit-0.0.4+cvs]]</div>

Thanks to [[User:Alessandro | Alessandro]], stefan_schmidt, cp15 and all Navit developers I have done a small ("not really working") preview of Navit on Neo1973 at [http://www.telemobilityforum.com/eng/ Telemobility Forum 2007]. Thanks to [http://gfoss.it GFoss] guys to invite me.
''[[User:Tyrael | Tyrael]]''

==Setting up Navit==
I got navit set up and configured to the point where it follows me on the map. It doesn't have street names or any other information, just the map and the cursor showing the location and direction. Here's what I did:
* Install navit ipkg on NEO
** Build using a local environment: make build-package-navit
** Download from [[User:Alessandro]] repo (http://aiurlano.netsons.org/OpenMoko/ipk/armv4t/)
* Set up your local maps
** Openstreetmap - follow directions at http://wiki.navit-project.org/index.php/OpenStreetMaps
** Here's an example of what I did to get the maps for the area around Seattle, Wa where I live:
*** figured out map coordinates using http://informationfreeway.org/?lat=47.520270037501454&lon=-122.20130713167327&zoom=9&layers=B000F000
*** Downloaded 4 regions from openstreetmaps ([[Navit#Script_to_download_OSM_maps|see below]] for a script to do this for you automatically for largish areas)
wget -O map1.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.2,47.5,-122,47.7
wget -O map2.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.4,47.5,-122.2,47.7
wget -O map3.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.4,47.3,-122.2,47.5
wget -O map4.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.2,47.3,-122,47.5
*** Made a navit binary map file using the osm2navit binary that comes with the navit package on my linux box (it is also installing to the target from the .ipk)
cat *.osm | bin/osm2navit --dedupe-ways > mymap.bin
*** Copied the map to the NEO
scp mymap.bin root@neo:/home/root/card/map
*** Changed the navit.xml file on the NEO to use the new map
vi /usr/share/navit/navit.xml
<map type="binfile" enabled="yes" data="/home/root/card/map/mymap.bin" />
* Run navit
** Start gllin
** Start gpsd ( gpsd /tmp/nmeaNP )
** Start navit

== News ==

=== Street names ===
They are now displayed on OpenMoko using the CVS version of Navit (20071217).

=== Point selection by pen ===
Easier using the CVS version (20071217).

=== Route > Destination ===
The Route > Destination menu item crashes the software (20071217).

A current fix is to set the LANG variable before calling navit. For example:
export LANG=fr_FR.UTF-8; navit

Note that a short syntax (e.g. LANG=fr) would not work.

http://trac.navit-project.org/ticket/51

=== Speech ===
Navit can speak if you install eSpeak + speech-dispatcher and updates your navit.xml file.

For adventurous people, one way to do this:

* mokoTTS aims to integrate these packages in OM:
http://projects.openmoko.org/projects/mokotts/

install espeak, dotconf, and then speech-dispatcher.

* change the speech tag in navit.xml:
<speech type="cmdline" data="spd-say '%s'" />

or "spd-say -l fr '%s'" for using the French voice for example.

=== Script to download OSM maps ===
[[User:Wurp|Wurp]] wrote a little python script to download all OSM maps within a lat/long rectangle. Just copy the script to a file called dlOSM.sh, chmod +x it, and run it like
dlOSM.sh <minimum latitude> <maximum latitude> <minimum longitude> <maximum longitude>

It takes a long time for large maps. I could optimize it some by having it try to get a big section at once, then if it fails, break it into smaller pieces and recurse. I'm not sure when/if I'll get around to that...

dlOSM.sh:
<pre>
#!/usr/bin/python

import os
import sys
#import math

def doIt(cmd):
os.system(cmd)

def getOsms(basename, minLat, maxLat, minLon, maxLon):
'''basename - base name of map, maps are named {basename}{count}.osm
minLat - latitude of the west side of the map
maxLat - latitude of the east side of the map
minLon - longitude of the north side of the map
maxLon - longitude of the south side of the map'''

wgetCmdTemplate = 'wget -O %s%s.osm http://www.openstreetmap.org/api/0.5/map?bbox=%s,%s,%s,%s'

currLat = minLat
mapCount = 0
while currLat < maxLat:
nextLat = min(currLat + 0.1, maxLat)

currLon = minLon
while currLon < maxLon:
nextLon = min(currLon + 0.1, maxLon)

doIt(wgetCmdTemplate % (basename, mapCount, currLat, currLon, nextLat, nextLon))

currLon = nextLon
mapCount = mapCount + 1

currLat = nextLat

(minLat, maxLat, minLon, maxLon) = map(float, sys.argv[1:])
getOsms('map', minLat, maxLat, minLon, maxLon)
</pre>

Navit

2008-01-31T21:48:18Z

Kriss: /* Setting up Navit */

http://navit.sourceforge.net/

<div align="center">[[Image:Screenshot-3.png | Navit-0.0.4+cvs]]</div>

Thanks to [[User:Alessandro | Alessandro]], stefan_schmidt, cp15 and all Navit developers I have done a small ("not really working") preview of Navit on Neo1973 at [http://www.telemobilityforum.com/eng/ Telemobility Forum 2007]. Thanks to [http://gfoss.it GFoss] guys to invite me.
''[[User:Tyrael | Tyrael]]''

==Setting up Navit==
I got navit set up and configured to the point where it follows me on the map. It doesn't have street names or any other information, just the map and the cursor showing the location and direction. Here's what I did:
* Install navit ipkg on NEO
** Build using a local environment: make build-package-navit
** Download from [[User:Alessandro]] repo (http://aiurlano.netsons.org/OpenMoko/ipk/armv4t/)
* Set up your local maps
** Openstreetmap - follow directions at http://wiki.navit-project.org/index.php/OpenStreetMaps
** Here's an example of what I did to get the maps for the area around Seattle, Wa where I live:
*** figured out map coordinates using http://informationfreeway.org/?lat=47.520270037501454&lon=-122.20130713167327&zoom=9&layers=B000F000
*** Downloaded 4 regions from openstreetmaps ([[Navit#Script_to_download_OSM_maps|see below]] for a script to do this for you automatically for largish areas)
wget -O map1.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.2,47.5,-122,47.7
wget -O map2.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.4,47.5,-122.2,47.7
wget -O map3.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.4,47.3,-122.2,47.5
wget -O map4.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.2,47.3,-122,47.5
*** Made a navit binary map file using the osm2navit binary that comes with the navit package on my linux box (it is also stalling to the target from the .ipk)
cat *.osm | bin/osm2navit --dedupe-ways > mymap.bin
*** Copied the map to the NEO
scp mymap.bin root@neo:/home/root/card/map
*** Changed the navit.xml file on the NEO to use the new map
vi /usr/share/navit/navit.xml
<map type="binfile" enabled="yes" data="/home/root/card/map/mymap.bin" />
* Run navit
** Start gllin
** Start gpsd ( gpsd /tmp/nmeaNP )
** Start navit

== News ==

=== Street names ===
They are now displayed on OpenMoko using the CVS version of Navit (20071217).

=== Point selection by pen ===
Easier using the CVS version (20071217).

=== Route > Destination ===
The Route > Destination menu item crashes the software (20071217).

A current fix is to set the LANG variable before calling navit. For example:
export LANG=fr_FR.UTF-8; navit

Note that a short syntax (e.g. LANG=fr) would not work.

http://trac.navit-project.org/ticket/51

=== Speech ===
Navit can speak if you install eSpeak + speech-dispatcher and updates your navit.xml file.

For adventurous people, one way to do this:

* mokoTTS aims to integrate these packages in OM:
http://projects.openmoko.org/projects/mokotts/

install espeak, dotconf, and then speech-dispatcher.

* change the speech tag in navit.xml:
<speech type="cmdline" data="spd-say '%s'" />

or "spd-say -l fr '%s'" for using the French voice for example.

=== Script to download OSM maps ===
[[User:Wurp|Wurp]] wrote a little python script to download all OSM maps within a lat/long rectangle. Just copy the script to a file called dlOSM.sh, chmod +x it, and run it like
dlOSM.sh <minimum latitude> <maximum latitude> <minimum longitude> <maximum longitude>

It takes a long time for large maps. I could optimize it some by having it try to get a big section at once, then if it fails, break it into smaller pieces and recurse. I'm not sure when/if I'll get around to that...

dlOSM.sh:
<pre>
#!/usr/bin/python

import os
import sys
#import math

def doIt(cmd):
os.system(cmd)

def getOsms(basename, minLat, maxLat, minLon, maxLon):
'''basename - base name of map, maps are named {basename}{count}.osm
minLat - latitude of the west side of the map
maxLat - latitude of the east side of the map
minLon - longitude of the north side of the map
maxLon - longitude of the south side of the map'''

wgetCmdTemplate = 'wget -O %s%s.osm http://www.openstreetmap.org/api/0.5/map?bbox=%s,%s,%s,%s'

currLat = minLat
mapCount = 0
while currLat < maxLat:
nextLat = min(currLat + 0.1, maxLat)

currLon = minLon
while currLon < maxLon:
nextLon = min(currLon + 0.1, maxLon)

doIt(wgetCmdTemplate % (basename, mapCount, currLat, currLon, nextLat, nextLon))

currLon = nextLon
mapCount = mapCount + 1

currLat = nextLat

(minLat, maxLat, minLon, maxLon) = map(float, sys.argv[1:])
getOsms('map', minLat, maxLat, minLon, maxLon)
</pre>

Manually using GPRS

2008-01-20T23:50:38Z

Kriss: /* Some APN names for reference */

You need to have [[GSM]] parts already initialized, with modem logged in to the network, for this to work. It is best to test it by doing test call. The GPRS connection is made using the PPP protocol to a server identified by an "APN" at the network operator.

The program that implements PPP on Linux is [[pppd]], which we need to configure and run to get a connection. When that is working, we can configure pppd to wait until it's needed before it connects, and to disconnect if the connection becomes idle. Further, we can start pppd in the background during the boot process.

== Configuring pppd for manual connections ==

You'll need /etc/ppp/peers/gprs:
<pre>
/dev/ttySAC0 115200
connect /etc/ppp/gprs-connect-chat
crtscts
lock
hide-password
defaultroute
usepeerdns
disconnect /etc/ppp/gprs-disconnect-chat
holdoff 3
ipcp-accept-local
lcp-echo-failure 8
lcp-echo-interval 3
noauth
noipdefault
novj
novjccomp
replacedefaultroute
persist
lcp-echo-interval 3
lcp-echo-failure 12
</pre>

This options where mentioned before with that strange comment. Mine worked fine for me without those.

<pre>
# very long timeouts (unwise?)
lcp-echo-interval 300
lcp-echo-failure 40000
</pre>

Depending on the APN, you may need password authentication using CHAP or PAP. You can add the following default line for "password-less" connections:

<pre>
# client server secret IP addresses
* * "" *
</pre>

For CHAP, lines in /etc/ppp/chap-secrets are used. For PAP, the lines are in /etc/ppp/pap-secrets. The client should match the "user" option in pppd the config file (below). You can use * to mean any here, but the option user "" doesn't mean empty!

For example:

<pre>
# Secrets for authentication using CHAP
# client server secret IP addresses
"user" * "password" *
</pre>

For this you need the following options in /etc/ppp/peers/gprs:

<pre>
# username to use for authentication, should match "client" in /etc/ppp/{chap,pap}-secrets
user "user"
</pre>

And you'll need /etc/ppp/gprs-connect-chat (needs "chmod +x"):

<pre>
#!/bin/sh -e
exec chat -v\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 3\
"" ATZ\
OK-\\k\\k\\k\\d+++ATH-OK ATE1\
OK AT+CFUN=0\
OK \\dAT+CFUN=1\
ERROR AT+CPIN\?\
"+CPIN: READY-AT+CPIN=\"2222\"-OK" AT\
TIMEOUT 60\
OK AT+COPS\
OK AT+CGDCONT=1,\"IP\",\"internet\"\
OK ATD*99#\
CONNECT \d\c
</pre>

You will need to adjust the APN name "internet" in at+cgdcont line to match what your network operator provides. See below in the table "Some APN names for reference" for the right settings for your operator.

Also good to have is /etc/ppp/gprs-disconnect-chat (needs "chmod +x"):

<pre>
#!/bin/sh -e
/usr/sbin/chat -v\
ABORT OK\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO CARRIER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 12\
"" \\k\\k\\k\\d+++ATH\
"NO CARRIER-AT-OK" ""
</pre>

You need a proper /etc/resolv.conf:

<pre>
ln -sf /var/run/resolv.conf /etc
</pre>

If needed put your nameserver for usb-net into /var/run/resolv.conf, not in /etc.

=== Required fixes ===

The image does not set a correct resolv.conf. i do so with an

<pre>
echo nameserver 192.168.0.201 > /var/run/resolv.conf
</pre>

in the right place. because a post-up in /etc/network/interfaces is not supported i do that in /etc/network/if-up.d/08setupdns

another problem is pppd's /etc/ppp/ip-down.d/92removedns which does not properly remove the link when shuting down ppp. my fix is this script:

<pre>
#!/bin/sh
ACTUALCONF=/var/run/resolv.conf
PPPCONF=/var/run/ppp/resolv.conf
if [ -f $PPPCONF ] ; then
if [ -f $ACTUALCONF ] ; then
if [ ! -h $ACTUALCONF -o ! "`readlink $ACTUALCONF 2>&1`" = "$PPPCONF" ] ; then
mv $ACTUALCONF $ACTUALCONF.ppporig
fi
fi

ln -sf $PPPCONF $ACTUALCONF
fi
</pre>

=== Starting pppd ===

Then, after initializing GSM, you should be able to initialize GPRS by `pppd call gprs`. Good luck!

To dial in - and get verbose output on the terminal - use pppd
<pre>
pppd debug nodetach call gprs
</pre>

The config above will establish a 'persist'ant link over gprs. The battery will run low in less than an hour. See an example for an on-demand config below.

=== Some APN names for reference ===

{| border="1"
! Country
! Carrier
! Plan
! APN
! user/password if required
! Working pppd scripts
|-
| Finland || Saunalahti || Any || internet.saunalahti || ||
|-
| Finland || Sonera || Any, behind NAT || internet || ||
|-
| Finland || Sonera || Any, public IP || prointernet || ||
|-
| Germany || E-Plus || BASE (and others?) || internet.eplus.de || eplus gprs ||
|-
| Germany || T-Mobile || || internet.t-mobile || ||
|-
| Germany || Vodafone || Any, behind NAT || web.vodafone.de || ||
|-
| Switzerland || Swisscom || e.g. Natel Basic Liberty, behind NAT || gprs.swisscom.ch || ||
|-
| UK || T-Mobile|| || general.t-mobile.uk || ||
|-
| UK || [http://www.filesaveas.com/gprs.html other providers] || || || ||
|-
| USA || Cingular (AT&T) || Less than full internet || wap.cingular || ||
|-
| USA || T-mobile || Anything less than full internet || wap.voicestream.com || ||
|-
| USA || T-mobile || Regular internet plan || internet2.voicestream.com || || [[T-Mobile pppd scripts]]
|-
| USA || T-mobile || "VPN" internet plan || internet3.voicestream.com || ||
|-
|}

== Starting pppd automatically ==

Once you have finished debugging your gprs-connect-chat and gprs options files, you may wish to automatically connect whenever needed and hang up when finished. Make sure you understand the impact of this change to your carrier plan billing. This is not recommended unless you have a large-use or unlimited data plan. These scripts do NOT prompt you before connecting.

=== On-demand connection settings ===

Additional settings are needed if you want the actual connection to be up only while there is traffic. In the 'gprs' file above, insert the following, making sure 'nodetach' is commented out. If 'nodetach' is on, the boot process will stop when it starts pppd. Also remove the option 'persist' mentioned above.

<pre>

# Wait until needed before connecting
demand

# Disconnect if idle for given amount of seconds
idle 20

</pre>

=== Start on boot (method 1) ===

Add the following definition to /etc/network/interfaces:
<pre>
auto ppp0
iface ppp0 inet ppp
provider gprs
</pre>

That should be it. Now you can use 'ifup ppp0' and 'ifdown ppp0' manually too.

=== Start on boot (method 2) ===

Create the following file as /etc/ppp/ppp_on_boot (needs chmod +x). The /etc/init.d/ppp script will call it to set up the daemon.
<pre>
#!/bin/sh
#
# Rename this file to ppp_on_boot and pppd will be fired up as
# soon as the system comes up, connecting to `provider'.
#
# If you also make this file executable, and replace the first line
# with just "#!/bin/sh", the commands below will be executed instead.
#

# The location of the ppp daemon itself (shouldn't need to be changed)
PPPD=/usr/sbin/pppd

# The default provider to connect to
$PPPD call gprs

# Additional connections, which would just use settings from
# /etc/ppp/options.<tty>
#$PPPD ttyS0
#$PPPD ttyS1
#$PPPD ttyS2
#$PPPD ttyS3
</pre>

Finally, you need to add the /etc/init.d/ppp script to the init process by creating symbolic links from the appropriate directories. I chose the following:

<pre>
/etc/rc0.d/K25ppp
/etc/rc1.d/K45ppp
/etc/rc2.d/S45ppp
/etc/rc3.d/S45ppp
/etc/rc4.d/S45ppp
/etc/rc5.d/S45ppp
/etc/rc6.d/K25ppp
</pre>

== See also ==
* [[pppd]]
* [[Manually using GSM]]
* [[Manually using Bluetooth]]

{{Languages|Manually_using_GPRS}}
[[Category:Documentation]]
[[Category:Developer software]]

[[Category:Guides]]

Manually using GPRS

2008-01-20T23:43:09Z

Kriss: /* Some APN names for reference */ - added swisscom - thanks Tonnerre

You need to have [[GSM]] parts already initialized, with modem logged in to the network, for this to work. It is best to test it by doing test call. The GPRS connection is made using the PPP protocol to a server identified by an "APN" at the network operator.

The program that implements PPP on Linux is [[pppd]], which we need to configure and run to get a connection. When that is working, we can configure pppd to wait until it's needed before it connects, and to disconnect if the connection becomes idle. Further, we can start pppd in the background during the boot process.

== Configuring pppd for manual connections ==

You'll need /etc/ppp/peers/gprs:
<pre>
/dev/ttySAC0 115200
connect /etc/ppp/gprs-connect-chat
crtscts
lock
hide-password
defaultroute
usepeerdns
disconnect /etc/ppp/gprs-disconnect-chat
holdoff 3
ipcp-accept-local
lcp-echo-failure 8
lcp-echo-interval 3
noauth
noipdefault
novj
novjccomp
replacedefaultroute
persist
lcp-echo-interval 3
lcp-echo-failure 12
</pre>

This options where mentioned before with that strange comment. Mine worked fine for me without those.

<pre>
# very long timeouts (unwise?)
lcp-echo-interval 300
lcp-echo-failure 40000
</pre>

Depending on the APN, you may need password authentication using CHAP or PAP. You can add the following default line for "password-less" connections:

<pre>
# client server secret IP addresses
* * "" *
</pre>

For CHAP, lines in /etc/ppp/chap-secrets are used. For PAP, the lines are in /etc/ppp/pap-secrets. The client should match the "user" option in pppd the config file (below). You can use * to mean any here, but the option user "" doesn't mean empty!

For example:

<pre>
# Secrets for authentication using CHAP
# client server secret IP addresses
"user" * "password" *
</pre>

For this you need the following options in /etc/ppp/peers/gprs:

<pre>
# username to use for authentication, should match "client" in /etc/ppp/{chap,pap}-secrets
user "user"
</pre>

And you'll need /etc/ppp/gprs-connect-chat (needs "chmod +x"):

<pre>
#!/bin/sh -e
exec chat -v\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 3\
"" ATZ\
OK-\\k\\k\\k\\d+++ATH-OK ATE1\
OK AT+CFUN=0\
OK \\dAT+CFUN=1\
ERROR AT+CPIN\?\
"+CPIN: READY-AT+CPIN=\"2222\"-OK" AT\
TIMEOUT 60\
OK AT+COPS\
OK AT+CGDCONT=1,\"IP\",\"internet\"\
OK ATD*99#\
CONNECT \d\c
</pre>

You will need to adjust the APN name "internet" in at+cgdcont line to match what your network operator provides. See below in the table "Some APN names for reference" for the right settings for your operator.

Also good to have is /etc/ppp/gprs-disconnect-chat (needs "chmod +x"):

<pre>
#!/bin/sh -e
/usr/sbin/chat -v\
ABORT OK\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO CARRIER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 12\
"" \\k\\k\\k\\d+++ATH\
"NO CARRIER-AT-OK" ""
</pre>

You need a proper /etc/resolv.conf:

<pre>
ln -sf /var/run/resolv.conf /etc
</pre>

If needed put your nameserver for usb-net into /var/run/resolv.conf, not in /etc.

=== Required fixes ===

The image does not set a correct resolv.conf. i do so with an

<pre>
echo nameserver 192.168.0.201 > /var/run/resolv.conf
</pre>

in the right place. because a post-up in /etc/network/interfaces is not supported i do that in /etc/network/if-up.d/08setupdns

another problem is pppd's /etc/ppp/ip-down.d/92removedns which does not properly remove the link when shuting down ppp. my fix is this script:

<pre>
#!/bin/sh
ACTUALCONF=/var/run/resolv.conf
PPPCONF=/var/run/ppp/resolv.conf
if [ -f $PPPCONF ] ; then
if [ -f $ACTUALCONF ] ; then
if [ ! -h $ACTUALCONF -o ! "`readlink $ACTUALCONF 2>&1`" = "$PPPCONF" ] ; then
mv $ACTUALCONF $ACTUALCONF.ppporig
fi
fi

ln -sf $PPPCONF $ACTUALCONF
fi
</pre>

=== Starting pppd ===

Then, after initializing GSM, you should be able to initialize GPRS by `pppd call gprs`. Good luck!

To dial in - and get verbose output on the terminal - use pppd
<pre>
pppd debug nodetach call gprs
</pre>

The config above will establish a 'persist'ant link over gprs. The battery will run low in less than an hour. See an example for an on-demand config below.

=== Some APN names for reference ===

{| border="1"
! Country
! Carrier
! Plan
! APN
! user/password if required
! Working pppd scripts
|-
| Finland || Saunalahti || Any || internet.saunalahti || ||
|-
| Finland || Sonera || Any, behind NAT || internet || ||
|-
| Finland || Sonera || Any, public IP || prointernet || ||
|-
| Germany || E-Plus || BASE (and others?) || internet.eplus.de || eplus gprs ||
|-
| Germany || T-Mobile || || internet.t-mobile || ||
|-
| Germany || Vodafone || Any, behind NAT || web.vodafone.de || ||
|-
| Swiss || Swisscom || ??? || gprs.swisscom.ch || ||
|-
| UK || T-Mobile|| || general.t-mobile.uk || ||
|-
| UK || [http://www.filesaveas.com/gprs.html other providers] || || || ||
|-
| USA || Cingular (AT&T) || Less than full internet || wap.cingular || ||
|-
| USA || T-mobile || Anything less than full internet || wap.voicestream.com || ||
|-
| USA || T-mobile || Regular internet plan || internet2.voicestream.com || || [[T-Mobile pppd scripts]]
|-
| USA || T-mobile || "VPN" internet plan || internet3.voicestream.com || ||
|-
|}

== Starting pppd automatically ==

Once you have finished debugging your gprs-connect-chat and gprs options files, you may wish to automatically connect whenever needed and hang up when finished. Make sure you understand the impact of this change to your carrier plan billing. This is not recommended unless you have a large-use or unlimited data plan. These scripts do NOT prompt you before connecting.

=== On-demand connection settings ===

Additional settings are needed if you want the actual connection to be up only while there is traffic. In the 'gprs' file above, insert the following, making sure 'nodetach' is commented out. If 'nodetach' is on, the boot process will stop when it starts pppd. Also remove the option 'persist' mentioned above.

<pre>

# Wait until needed before connecting
demand

# Disconnect if idle for given amount of seconds
idle 20

</pre>

=== Start on boot (method 1) ===

Add the following definition to /etc/network/interfaces:
<pre>
auto ppp0
iface ppp0 inet ppp
provider gprs
</pre>

That should be it. Now you can use 'ifup ppp0' and 'ifdown ppp0' manually too.

=== Start on boot (method 2) ===

Create the following file as /etc/ppp/ppp_on_boot (needs chmod +x). The /etc/init.d/ppp script will call it to set up the daemon.
<pre>
#!/bin/sh
#
# Rename this file to ppp_on_boot and pppd will be fired up as
# soon as the system comes up, connecting to `provider'.
#
# If you also make this file executable, and replace the first line
# with just "#!/bin/sh", the commands below will be executed instead.
#

# The location of the ppp daemon itself (shouldn't need to be changed)
PPPD=/usr/sbin/pppd

# The default provider to connect to
$PPPD call gprs

# Additional connections, which would just use settings from
# /etc/ppp/options.<tty>
#$PPPD ttyS0
#$PPPD ttyS1
#$PPPD ttyS2
#$PPPD ttyS3
</pre>

Finally, you need to add the /etc/init.d/ppp script to the init process by creating symbolic links from the appropriate directories. I chose the following:

<pre>
/etc/rc0.d/K25ppp
/etc/rc1.d/K45ppp
/etc/rc2.d/S45ppp
/etc/rc3.d/S45ppp
/etc/rc4.d/S45ppp
/etc/rc5.d/S45ppp
/etc/rc6.d/K25ppp
</pre>

== See also ==
* [[pppd]]
* [[Manually using GSM]]
* [[Manually using Bluetooth]]

{{Languages|Manually_using_GPRS}}
[[Category:Documentation]]
[[Category:Developer software]]

[[Category:Guides]]

USB Networking/de

2008-01-17T22:54:50Z

Kriss: /* Ubuntu (getestet mit Feisty und Gutsy) */

= Neo1973 - Seite =

== Namensauflösung ==

Standardmäßig hat das Neo1973 eine Netzwerkschnittstelle usb0, die mit einem im Kernel einkompilierten (g_ether) Ethernet Dadget arbeitet.

Wenn Sie auf dem Neo voll qualifizierte Hostnamen im Internet erreichen wollen, müssen sie einen DNS-Server definieren. Dazu erstellen Sie die Datei /etc/resolv.conf, die mindestens diese Zeile enthält:

nameserver xxx.xxx.xxx.xxx

z.B. nameserver 192.168.1.1

Danach können Sie auf dem Neo Ihre OpenMoko 2007.2 Pakete mit "ipkg update && ipkg upgrade" aktualisieren.

Ein besserer Ansatz ist ein symbolischer Link

ln -s /var/run/resolv.conf /etc/resolv.conf

Danach erstellen Sie die datei /etc/network/if-up.d/08setupdns, die folgende Zeilen enthält:

#!/bin/sh -e
echo nameserver 192.168.0.200 > /var/run/resolv.conf

Auf diese Weise wird diese Datei vom PPP-Paket korrekt behandelt, wenn eine Einwahl per GPRS stattfindet.

== Routing ==

Sie benötigen eine zusätzliche Route für die Verbindung ins Internet. Diese verbindung kann von Ihrem PC geroutet werden (siehe unten), wenn der PC das Standardrouting-Ziel ist. Sie erreichen dies durch das Hinzufügen von

gateway 192.168.0.200

zu Ihrer /etc/network/interfaces im Abschnitt usb0.

= Desktop-Seite =

== Manuelle Methode ==

Nach dem Verbinden mit dem Gerät laden Sie das Modul usbnet und konfigurieren Sie die Schnittstelle usb0 (als root):
<pre>
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
</pre>
Wenn Ihre eth0 Schnittstelle sich im selben 'Bereich' (z.B. 192.168.0.105) befinet, dann können Sie folgendes tun:
1. Neo anpingen:
# ping -I usb0 192.168.0.202
2. Route zum Neo hinzufügen:
# /sbin/route add -host 192.168.0.202/32 dev usb0
3. Einloggen auf dem Neo:
# ssh root@192.168.0.202

Wenn Sie keine notwendigen Module zum Erzeugen von usb0 haben, stellen Sie sicher, dass folgende Kernel Optionen aktiviert sind:
* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER
Beide Optionen sind unter Device Drivers -> USB support -> USB Network Adapters zu finden. Für weitere Informationen siehe [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

== Automatische Methode ==

Die Information entnehmen sie dem [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet], geschickt von Marcin 'Hrw' Juszkiewicz.

=== Debian oder ähnliche ===
Editieren Sie /etc/network/interfaces wie folgt:
<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
</pre>

=== Ubuntu (getestet mit Feisty und Gutsy) ===
Editieren Sie /etc/network/interfaces:
<pre>
auto usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
up echo 1 > /proc/sys/net/ipv4/ip_forward &
up iptables -P FORWARD ACCEPT &
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
</pre>

Wenn Sie das Kommando "echo 1 > /proc/..." manuell ausführen, könnte sudo nicht ausreichen, denn das Kommando sudo muss unter der Shell bash ausgeführt werden.

Ubuntu Fiesty und Gusty haben offenbahr einen Fehler, dass ifdown nicht ausgeführt wird, solange die Schnittstelle "unplugged" ist. Das bedeutet, dass es nur dann funktioniert, wenn das System neu gebootet wird.

Man kann die Datei /etc/udev/rules.d/85-ifupdown.rules patchen, indem man zwei Zeilen am Ende der Datei editiert:
<pre>
SUBSYSTEM=="net", DRIVERS=="?*", 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", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus \
--startas /sbin/ifup -- --allow auto $env{INTERFACE}"

LABEL="net_end"

ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus \
--startas /sbin/ifdown -- --allow auto $env{INTERFACE}"
</pre>

Der Fehler besteht darin, dass LABEL="net_end" an falscher Position steht.

=== openSuSE ===
/etc/sysconfig/network/ifcfg-usb0
# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

=== Fedora (getestet unter FC8) ===
/etc/sysconfig/network-scripts/ifcfg-usb0
<pre>
# USB configuration for PDAs (openmoko)
# from http://www.handhelds.org/moin/moin.cgi/UsbNet
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes
</pre>

=== Red Hat oder ähnliche ===
Editieren Sie /etc/sysconfig/network-scripts/net.hotplug:

Nach diesem Kommando
<pre>
case $INTERFACE in
# interfaces that are registered after being "up" (?)
</pre>
fügen Sie hinzu
<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 ===
* Öffnen Sie /etc/conf.d/net und fügen Sie hinzu:
# Neo1973
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )
* Erzeugen Sie einen neuen init Script:
cd /etc/init.d
ln -s net.lo net.usb0
* Erzeugen Sie iptables Einträge:
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
* Speichern Sie das
/etc/init.d/iptables save
* Wenn Sie möchten, dass Routing standardmäßig aktiviert wird:
rc-update add iptables default

=== MacOS X ===
Sehen Sie [[MacOS_X#USB_Networking|USB Netzwerk Abschnitt im MacOS X Artikel]].

= Mobile Entwicklung =

== Weiterleiten der DNS Anfragen ==

Wenn Sie Ihren Standort oft wechseln und somit Verbindung zu mehreren Netzwerken haten und Ihre IP Adresse über DHCP beziehen, ist es ziemlich aufwendig, jedes mal die Datei /etc/resolv.conf zu aktualisieren.

Um dies als Teil eines Setup-Scriptes zu tun, kann man einen Proxy DNS einrichten, der auf die IP Adresse des Neo zeigt. Dies bedeutet, dass die Datei /etc/resolv.conf auf dem Neo nur folgendes enthält:

nameserver 192.168.0.200

und z.B. der Notebook funktioniert als DNS Proxy und leitet alle Anfragen basierend auf seiner /etc/resolv.conf weiter.

'''Starten Sie den DNS Proxy nur auf der Schnittstelle usb0, um andere Netzwerkverbindungen nicht zu unterbrechen.'''

=== Weiterleiten mit 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 from my site. The script also performs the initial setup of the connection as per the [[USB_Networking#Manual_method]] above.

Der Script ist für die Nutzung von [http://dnrd.sourceforge.net/ dnrd] als DNS Proxy entwickelt. Der [http://buildhost.automated.it/gta01 Script] ist eine Kopie von [http://buildhost.automated.it/dnrd-2.20.3.tar.gz dnrd]. Der Script führt auch die Ersteinrichtung für die Verbindung mit [[USB_Networking/de#Manuelle_Methode]] oben.

=== Weiterleiten mit einem UDP-Forwarder ===

Eine weitere einfache Installation ist mit einem UDP-Forwarder von http://www.tapor.com/udpf/ mit dem folgenden Kommando möglich:

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

=== Weiterleitung mit Iptables ===
Es ist möglich DNS Anfragen mit Iptables und DNAT weiterzuleiten:

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

Dabei ist <tt>192.168.0.1</tt> die IP Adresse des Heimatgateways (Routers). Dies ist die einfachste Methode, aber sie ist nicht empfehlenswert, wenn Sie eine direkte Verbindung zum Internet haben und die DNS Server ihres ISP ändern können. Außerdem hat diese Methode keine Lastverteilung.

= Verbindung mit dem Telefon =

Zum Anmelden am Neo <tt>ssh root@192.168.0.202</tt> mit dem leeren root Passwort

Notiz: Der SSH Daeomon (dropbear 0.49) im OpenMoko scheint einen Bug beim Zurückgeben des Verbindungsstatus an den Client zu haben. Ab und zu bekommen sie einen Rückgabewert 255.

===SSH Extras===

Wenn Sie nicht mehr root@192.168.0.202 auf dem PC eintippen möchten, können sie einen Eintrag in der /etc/hosts machen:

192.168.0.202 neo

dann editieren Sie ~/.ssh/config (oder erzeugen sie) und fügen hinzu

host neo
user root

dann brauchen Sie nur einzutippen:

# ssh neo

Um zu vermeiden, dass SSH für jeden Host eine Zeile mit dem Host-Key in der Datei known_hosts einfügr, können Sie folgende Zeile in der ~/.ssh/config einfügen

UserKnownHostsFile /dev/null

Vielleicht möchten Sie einen Schlüssel zur Umgehung der Anzeige des Anmeldebildschirms nutzen.

===SSH Schlüssel===
====Vom Host zum Neo====

Zur Erzeugung des SSH Schlüssels für die Verwendung des Login Mechanismus geben sie folgendes ein:

ssh-keygen -t rsa

Wenn Sie nach einem Passwort gefragt werden, drücken Sie Enter für leeren Passwort (''wirklich keine gute Idee'') oder geben Sie das Passwort für diesen Schlüssel ein. Loggen Sie sich am Neo mit ssh ein und erzeugen Sie das Verzeichnis ~/.ssh wie folgt:

# mkdir ~/.ssh

Danach kopieren Sie die Datei '''.pub''' vom PC auf den Neo:

# scp ~/.ssh/id_rsa.pub phone:.ssh/authorized_keys

Jetzt sollten Sie in der Lage sein, sich auf dem Neo direkt per ssh anzumelden.

Zum Deaktivieren des Passwort Logins ('''nach dem Einrichten des Schlüssel Zuganges''') editieren Sie die Datei /etc/init.d/dropbear und ändern Sie folgende Zeile:

DROPBEAR_EXTRA_ARGS=

zu

DROPBEAR_EXTRA_ARGS="-s"

Jetzt müssen Sie den dropbear neu starten um die Änderung zu aktivieren.

====Vom Neo zum Host====
Erzeugen Sie den Schlüssel

dropbearkey -t rsa -f id_rsa

Die Ausgabe wird in etwa wie folgt aussehen:

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

Kopieren Sie eine Zeile (in diesem Beispiel beginnend mit 'ssh-rsa') am Ende der Datei authorized_keys auf dem Host System (oft in ~/.ssh/).

Loggen Sie sich vom Neo aus mit ssh -i:

ssh -i id_rsa user@host

Die Anweisungen wurden entnommen aus: [[http://forum.openwrt.org/viewtopic.php?pid=53705]]

===GUI auf dem Desktop über SSH===

Wenn Sie die GUI des Neo auf dem Desktop benutzen möchten, können Sie den X Server wie folgt über SSH tunneln:

ssh -l root -X -v 192.168.0.202

Melden Sie sich an und starten Sie z.B. das Programm openmoko-finger-demo, welches auf ihrem Desktop geöffnet wird. Um die Seitenverhältnise zu verändern, verändern Sie einfach die Größe des Fensters auf dem Desktop.

===Remote Anwendungen auf dem Neo===

Um die Desktop Anwendungen auf Ihrem Neo anzuzeigen melden Sie sich zuerst auf dem Neo an:

ssh -l root 192.168.0.202

Danach darauf folgendes eingeben:

DISPLAY=:0 xhost +192.168.0.200

Danach können Sie die SSH Sitzung schließen. Gehen Sie zurück auf den Desktop und führen Sie aus:

DISPLAY=moko:0 xclock

Beachten Sie, dass der Befehl xhost entfernten Anwendungen auf 192.168.0.200 den Zugriff auf den X-Server erlaubt. Dies erlaubt also jedem Programm auf dem Desktop auf den X-Server zu zugreifen, einschließlich allen Kommandos, die Sie eingeben. Um die Fernbedienung auszuschalten, geben Sie folgendes ein:

DISPLAY=:0 xhost -192.168.0.200

<span id="bottom"></span>
{{Languages|USB Networking}}

[[Category:Hardware]]
[[Category:Implemented]]

Gsmd/de

2007-12-16T14:38:11Z

Kriss: /* Was derzeit fehlt */ neue sms funktionen

[[gsmd]] ist der [[GSM]] Daemon, der als ein Hintergrundprozess auf dem OpenMoko läuft und die Verwaltung der traditionellen 'Telefon' Funktionen (Sprache/SMS/GPRS) des Neo1973 übernimmt.

Weitere technische Details und API Dokumentationen stehen [[Gsmd/document |hier]] zur Verfügung.

== Nutzung ==

=== Auf dem Neo ===
gsmd wird beim Booten als ein Hintergrundprozess (Daemon) durch den Initscript /etc/init.d/gsmd gestartet. In diesem Fall wird die Debug Ausgabe nach /tmp/gsm.log weitergeleitet.

Zum Zwecke der Fehlersuche kann gsmd im Vordergrund gestartet werden, mit folgenden Optionen:
<pre>
> gsmd --help
gsmd - (C) 2006 by Harald Welte <laforge@gnumonks.org>
This program is FREE SOFTWARE under the terms of GNU GPL

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

Wenn Ihr GSM Modem am ttySAC0 angeschlossen ist (wie in [[:Category:Neo1973 Hardware | Neo1973]]), dann rufen Sie es z.B. wie folgt auf:
> gsmd -p /dev/ttySAC0 -s 115200 -F
(Baudrate wird automatisch vom Modem ermittelt)

=== Fom Host PC ===
Mit dem aktuellen [[uboot]] (svn > r2885) kann der GSM Modem eingeschaltet und auf der seriellen Konsole des uboot's selbst verbunden werden. Somit kann der PC direkt mit dem Modem kommunizieren. Einige Anmerkungen zu diesem Betriebsmodus des GSM Modems finden Sie [[User:Miki/hosted_gsmd|hier]].

== libgsmd ==

Libgsmd ist eine Bibliothek der Programmiersprache C, die eine API für die Anwendungsprogramme anbietet. Programme, die diese Bibliothek benutzen, können z.B. Anrufe tätigen, einkommende Anrufe annehmen, sich am Netzwerk registrieren, etc.

== libgsmd-tool ==

Libgsmd-tool ist eine kleine Demo Anwendung, die verwendet werden kann, um die Nutzung der libgsmd API zu demonstrieren bzw. zu testen.

== Nutzung ==

Libgsmd kann in mehreren Modis betrieben werden.

=== Nutzung im Kommandozeilen Modus ===

Der Kommandozeilenmodus bietet eine einfache textbasierte Schnittstelle um Anrufe zu tätigen.

Der Kommandozeilenmodus kann wie folgt gestartet werden:

libgsmd-tool -m shell

Dies kann wie im folgenden Beispiel genutzt werden:

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

?
A Answer incoming call
D Dial outgoing number
H Hangup call
O Power On
o Power Off
r Register to network
R Register to given operator (R=number)
U Unregister from netowrk
P Print current operator
L Detect available operators
Q Read signal quality
T Send DTMF Tone
n Print subscriber numbers
pd PB Delete (pb=index)
pr PB Read (pr=index)
prr PB Read Range (prr=index1,index2)
pf PB Find (pf=indtext)
pw PB Write (pw=index,number,text)
ps PB Support
pm PB Memory
pp PB Set Memory (pp=storage)
pRr Retrieve Readrg Records
pRf Retrieve Find Records
sd SMS Delete (sd=index,delflg)
sl SMS List (sl=stat)
sr SMS Read (sr=index)
ss SMS Send (ss=ask_ds,number,text|["text"])
sw SMS Write (sw=stat,number,text)
sm SMS Storage stats
sM SMS Set preferred storage (sM=mem1,mem2,mem3)
sc SMS Show Service Centre
sC SMS Set Service Centre (sC=number)
q Quit

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

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

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

=== Nutzung im atcmd Modus ===

Der stcmd Modus ist ein Passthrough-Modus. Passthrough bedeutet, dass er die [[GSM 07.07]] Befehle akzeptiert, die zum Daemon weitergeleitet werden, der sie ausführt und eine Antwort zurückliefert. Dies kann für die Fehlersuche nützlich sein.

Der atcmd Modus kann wie folgt gestartet werden:

libgsmd-tool -m atcmd

Die Nutzung kann wie im folgenden Beispiel aussehen:

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

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

== Funktionen zur Netzverbindung ==

Funktionen zur Auswahl des Netzbetreibers wurden umgesetzt und zusammengefasst im SVN [http://lists.openmoko.org/pipermail/gsmd-devel/2007-September/000216.html]:

Die neuen Kommandos im libgsmd-util sind:
R - Register to given operator (R=number)
P - Print current operator
L - Detect available operators
Q - Read signal quality

Dies ist mit der Finktion mit der Bezeichnung "_opers_" implementiert.

== Was derzeit fehlt ==

(Bitte fügen Sie einen Punkt zu dieser Auflistung hinzu, wenn Sie eine Funktionalität vermissen.)

* Telefon Funktionalität
** Flugzeugmodus, Ausschalten des gsmd (dies wird außerhalb des gsmd mit Hilfe der Runlevels erledigt)
** Fähigkeit Notrufe zu tätigen, wenn das Gerät über keine SIM Karte verfügt
** Anzeige des Herstellers/Models/Version/IMEI
** Benachrichtigung des Anwenders, wenn die SIM Karte gesperrt ist

* SMS Funktionalität
** SMS empfangen
** Zugriff auf die in der SIM-Karte gespeicherten SMS - ''bald gelöst - siehe Hilfe''

* SIM Funktionalität
** Auslesen der Telefonbucheinträge - ''bald gelöst - siehe Hilfe''
** Schreiben der Telefonbucheinträge - ''bald gelöst - siehe Hilfe''

* GPRS Funktionalität
** Einrichtung der GPRS Verbindung, benutzen Sie dies durch das separate DLC of TS07.10 Multiplex

* gsmd interne Infrastruktur
** feingranulierte Ereignisbehandlung
** Möglichkeit der Bestimmung des Loglevels auf der Kommandozeile
** Logdateien neu erstellen beim SIGUSR1 oder SIGHUP (logrotate)
** Permission Handling
** D-Bus Interface

== Implementation Thoughts ==

== Status Anzeige ==

=== Power Status des Gerätes ===

=== Suspend Power Status ===

=== Status der Netzwerkregistrierung ===

=== Status der Verschlüsselungserkennung ===

=== Anrufstatus ===

{{Languages | Gsmd}}

[[Category:Software]]
[[Category:Implemented]]

Userspace root image

2007-11-19T17:08:56Z

Kriss: /* Mounting the JFFS2 image on a loop back (MTD RAM) device */ - mount jffs2 on ppc

== Creating a root filesystem from scratch ==

To create a root file system image for storage in NAND flash, we use the mkfs.jffs2 program contained in the Debian package ''mtd-tools''.

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

is a typical command. It creates a FS image for our erase block size of 16k, padded to 0x700000 bytes in length from the files contained in the ''/tmp/jffsroot'' directory and stores the FS image in ''rootfs.jffs2''.

== Using pre-created root fs image ==

=== Prebuilt ===

See [[Repositories]] and update the list if you have more information.

=== OpenEmbedded ===

OpenEmbedded will itself create a jffs2 image at the end of the build process.

Once the build server is running, it will create root filesystem images for us.

=== demo JFFS2 root image ===

Check the [[Flashing openmoko]] page for pre-built root images. Please note that this image may take long to boot the first time, since this boot finishes the installation process.

=== Mounting the JFFS2 image on a loop back (MTD RAM) device ===

As mounting the JFFS2 image from /dev/loop0 device is not supported, use the mtdram device as described in http://www.handhelds.org/hypermail/familiar/62/6232.html

modprobe mtdcore
modprobe jffs2
modprobe mtdram total_size=59024 # default is 4 MByte - set to max. available size
modprobe mtdchar
modprobe mtdblock

Using ''total_size=59024'' will set the filesystem size to the available space on /dev/mtd4 of the GTA1 device. So when you copy the image back it will be about 58 MB. You can set this to smaller values though.

Be careful to really use the mtd-ram-disk (maybe there is a real Flash-device somewhere in your development system)

So check for that looking into /proc/mtd:
cat /proc/mtd
# dev: size erasesize name
# mtd0: 039a4000 00020000 "mtdram test device"

Then write the image to that device and mount it:

dd if=<rootfs.jffs2> of=/dev/mtd0
mount -t jffs2 /dev/mtdblock0 <mountpoint>

The image is an Little Endian jffs2 image. To mount it on Big Endian architectures (like PowerPC) it'll have to be converted:

jffs2dump -l -c -e <rootfs.jffs2.be> <rootfs.jffs2> # only needed on non little endian archs

==== create the new image ====
To get the changed image back there are two ways. The obvious one is to unmount it and copy the data back from the MTD block device (the image will be 58 MB):

umount /dev/mtdblock0
dd if=/dev/mtdblock0 of=<rootfs.jffs2>

You can also create a new image using the mounted file system and the method described [[Userspace_root_image#Creating_a_root_filesystem_from_scratch | above]] (the image will have the size of its data):

mkfs.jffs2 --pad=0x700000 -o new_rootfs.jffs2 -e 0x4000 -n -d <mountpoint>

== Flashing a root filesystem into NAND ==

See [[U-boot#Writing_rootfs_to_NAND]]

{{Languages|Userspace_root_image}}
[[Category:Software]]
[[Category:Guides]]

SMSTool

2007-11-13T12:23:07Z

Kriss: /* Planned Features */

{{InProgress}}
[[Image:SMSTool-0.3.png|thumb|SMSTool - SMS Tool]]

== Overview ==
Until OpenMoko releases an official GUI-Tool to send SMS you can use SMSTool for that task.

This programm is written in Python using pygtk. It can be used only if those are present in your environment.

(see [[SMSTool#Environment]])

== Current Features ==

* Send SMS
** The default number is mine. - Leave a message if you like. ;-) --[[User:Kriss|kriss]] 22:54, 9 September 2007 (CEST)

== Planned Features ==

* Receive SMS
* Move to python-gsmd

== Comment on GSM Support ==

* As there are no gsmd python bindings available at the time, SMSTool uses python-subprocess and threads to communicate to the commandline of [[Gsmd#libgsmd-tool | libgsmd-tool]] for the time being.

We have some basic support for gsmd bindings in python. (Move this to discussion if necessary, apologies for the noise)
http://projects.openmoko.org/plugins/scmsvn/viewcvs.php/?root=python-openmoko -- Sudharsh

== Download ==

[http://mput.de/~kristian/.openmoko/SMSTool-0.3c.tar.bz2 SMSTool-0.3c.tar.bz2]

An smstool package is available from the repository at [[User:Alessandro | Alessandro]]'s user page.

== Environment ==

The following archives will have to be installed:

* python-core
* python-misc
* python-lang
* python-pygtk
* python-subprocess
* python-threading (should be a dependency of python-subprocess - todo: fix)
* python-pygobject (should be a dependency of python-pygtk - todo: fix)

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

== Installation / Execution ==

* download file to Neo (e.g. using wget)
* Uncompress tar.gz file (e.g. tar -xzvf file.tar.gz)
* run:
export DISPLAY=:0.0
python SMSTool-x.x/SMSTool.py &

[[Category:Applications]]
[[Category:In_progress]]

PyPenNotes

2007-10-10T17:22:40Z

Kriss: screenshot update

{{InProgress}}

[[Image:PyPenNotes-0.3.png|thumb|pyPenNotes 0.3]]

== Overview ==
Little tool to write notes using pen and touchscreen.

This program is written in [[Python]] using pygtk. It can be used only if those are present in your environment (see [[PyPenNotes#Environment]]).

== Current Features ==

* Change color and size of pen
* Change background color (even on used notebook pages)
* Undo
* Save and Restore
** Using the file '''~/.penNotes.strokes_data'''
** You may symlink that to your SD-Card if you like...
* As many Notes as you like
** (1-9999, or no RAM left ;-) )
** 200 simple Notes may take about 10 MByte (should be less with Version 0.3 - so this is a vague estimate)

== Planned Features ==

* Manage different notebooks (choose place to save them)

== Download ==
{|border=1
! Version
! Download
! Release Focus
|-
| 0.3b ('''current''')
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.3b.tar.bz2 pyPenNotes-0.3b.tar.bz2]
| bugfix release - ignore non existent strokes-file; speed up strokes-file loading a bit
|-
| 0.3
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.3.tar.bz2 pyPenNotes-0.3.tar.bz2]
| 2nd Toolbar + Togglebutton, Undo, Save, Restore, Autosave/-load on exit and start, serious redraw speed up
|-
| 0.2
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.2.tar.bz2 pyPenNotes-0.2.tar.bz2]
| color, thickness and note selection, notes won't get saved to FLASH yet
|-
| 0.1
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.1.tar.bz2 pyPenNotes-0.1.tar.bz2]
| initial release - can do nothing yet. :-)
|}

== Environment ==

:''For more, see [[Python]].

The following archives will have to be installed (source packages: python python-pygtk python-pycairo python-pygobject):

python-core python-misc python-lang python-pygtk

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

[[Category:Applications]]
[[Category:In_progress]]

File:PyPenNotes-0.3.png

2007-10-10T17:21:43Z

Kriss:

PyPenNotes

2007-10-09T16:03:11Z

Kriss: /* Download */ 0.3b - bugfix release - ignore non existent strokes-file; speed up strokes-file loading a bit

{{InProgress}}

[[Image:PyPenNotes-0.1.png|thumb|pyPenNotes - "Blue Ink Editon"]]

== Overview ==
Little tool to write notes using pen and touchscreen.

This program is written in [[Python]] using pygtk. It can be used only if those are present in your environment (see [[PyPenNotes#Environment]]).

== Current Features ==

* Change color and size of pen
* Change background color (even on used notebook pages)
* Undo
* Save and Restore
** Using the file '''~/.penNotes.strokes_data'''
** You may symlink that to your SD-Card if you like...
* As many Notes as you like
** (1-9999, or no RAM left ;-) )
** 200 simple Notes may take about 10 MByte (should be less with Version 0.3 - so this is a vague estimate)

== Planned Features ==

* Manage different notebooks (choose place to save them)

== Currnet screenshot ==

http://scap.linuxtogo.org/files/be14e59a15321981dcbf1282e4f1e2ba.png

== Download ==
{|border=1
! Version
! Download
! Release Focus
|-
| 0.3b ('''current''')
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.3b.tar.bz2 pyPenNotes-0.3b.tar.bz2]
| bugfix release - ignore non existent strokes-file; speed up strokes-file loading a bit
|-
| 0.3
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.3.tar.bz2 pyPenNotes-0.3.tar.bz2]
| 2nd Toolbar + Togglebutton, Undo, Save, Restore, Autosave/-load on exit and start, serious redraw speed up
|-
| 0.2
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.2.tar.bz2 pyPenNotes-0.2.tar.bz2]
| color, thickness and note selection, notes won't get saved to FLASH yet
|-
| 0.1
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.1.tar.bz2 pyPenNotes-0.1.tar.bz2]
| initial release - can do nothing yet. :-)
|}

== Environment ==

:''For more, see [[Python]].

The following archives will have to be installed (source packages: python python-pygtk python-pycairo python-pygobject):

python-core python-misc python-lang python-pygtk

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

[[Category:Applications]]
[[Category:In_progress]]

PyPenNotes

2007-10-09T02:23:27Z

Kriss: 0.3 - 2nd Toolbar + Togglebutton, Undo, Save, Restore, Autosave/-load on exit and start, serious redraw speed up, new screenshoot

{{InProgress}}

[[Image:PyPenNotes-0.1.png|thumb|pyPenNotes - "Blue Ink Editon"]]

== Overview ==
Little tool to write notes using pen and touchscreen.

This program is written in [[Python]] using pygtk. It can be used only if those are present in your environment (see [[PyPenNotes#Environment]]).

== Current Features ==

* Change color and size of pen
* Change background color (even on used notebook pages)
* Undo
* Save and Restore
** Using the file '''~/.penNotes.strokes_data'''
** You may symlink that to your SD-Card if you like...
* As many Notes as you like
** (1-9999, or no RAM left ;-) )
** 200 simple Notes may take about 10 MByte (should be less with Version 0.3 - so this is a vague estimate)

== Planned Features ==

* Manage different notebooks (choose place to save them)

== Currnet screenshot ==

http://scap.linuxtogo.org/files/be14e59a15321981dcbf1282e4f1e2ba.png

== Download ==
{|border=1
! Version
! Download
! Release Focus
|-
| 0.3 ('''current''')
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.3.tar.bz2 pyPenNotes-0.3.tar.bz2]
| 2nd Toolbar + Togglebutton, Undo, Save, Restore, Autosave/-load on exit and start, serious redraw speed up
|-
| 0.2
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.2.tar.bz2 pyPenNotes-0.2.tar.bz2]
| color, thickness and note selection, notes won't get saved to FLASH yet
|-
| 0.1
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.1.tar.bz2 pyPenNotes-0.1.tar.bz2]
| initial release - can do nothing yet. :-)
|}

== Environment ==

:''For more, see [[Python]].

The following archives will have to be installed (source packages: python python-pygtk python-pycairo python-pygobject):

python-core python-misc python-lang python-pygtk

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

[[Category:Applications]]
[[Category:In_progress]]

PyPenNotes

2007-10-07T16:46:44Z

Kriss: /* Current Features */ - aprox RAM usage

{{InProgress}}

[[Image:PyPenNotes-0.1.png|thumb|pyPenNotes - "Blue Ink Editon"]]

== Overview ==
Little tool to write notes using pen and touchscreen.

This program is written in [[Python]] using pygtk. It can be used only if those are present in your environment (see [[SettingsGUI#Environment]]).

== Current Features ==

* draw in different colors, thicknesses
* change color
* sponge
* as many notes as you like
** (1-9999, or no RAM left ;-) )
** 168 simple notes may take about 19 MByte of RAM

== Planned Features ==

* save notes to flash

== Currnet screenshot ==

http://scap.linuxtogo.org/files/45edcb7a32ad1b6a5e0c19ff622bee30.png

== Download ==
{|border=1
! Version
! Download
! Release Focus
|-
| 0.2 ('''current''')
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.2.tar.bz2 pyPenNotes-0.2.tar.bz2]
| color, thickness and note selection, notes won't get saved to FLASH yet
|-
| 0.1
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.1.tar.bz2 pyPenNotes-0.1.tar.bz2]
| initial release - can do nothing yet. :-)
|}

== Environment ==

:''For more, see [[Python]].

The following archives will have to be installed (source packages: python python-pygtk python-pycairo python-pygobject):

python-core python-misc python-lang python-pygtk

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

[[Category:Applications]]
[[Category:In_progress]]

Thumbtribes

2007-10-07T16:14:05Z

Kriss: Note on Thumbtribes

A project by John Moore. Contaning a Webservice and a GUI client for the OpenMoko platoform.

See the Zedstar.org Ltd Blog at: http://zedstar.org/blog/

The service is available at: http://thumbtribes.mobi/

PyPenNotes

2007-10-06T19:38:10Z

Kriss: 0.2 - color, thickness and note selection, notes won't get saved to FLASH yet, new screenshot

SMSTool

2007-10-06T00:12:27Z

Kriss: /* Download */ - text update

{{InProgress}}
[[Image:SMSTool-0.3.png|thumb|SMSTool - SMS Tool]]

== Overview ==
Until OpenMoko releases an official GUI-Tool to send SMS you can use SMSTool for that task.

This programm is written in Python using pygtk. It can be used only if those are present in your environment.

(see [[SMSTool#Environment]])

== Current Features ==

* Send SMS
** The default number is mine. - Leave a message if you like. ;-) --[[User:Kriss|kriss]] 22:54, 9 September 2007 (CEST)

== Planned Features ==

* Receive SMS

== Comment on GSM Support ==

* As there are no gsmd python bindings available at the time, SettingGUI uses python-subprocess and threads to communicate to the commandline of [[Gsmd#libgsmd-tool | libgsmd-tool]] for the time being.

== Download ==

[http://mput.de/~kristian/.openmoko/SMSTool-0.3c.tar.bz2 SMSTool-0.3c.tar.bz2]

An smstool package is available from the repository at [[User:Alessandro | Alessandro]]'s user page.

== Environment ==

The following archives will have to be installed:

* python-core
* python-misc
* python-lang
* python-pygtk
* python-subprocess
* python-threading (should be a dependency of python-subprocess - todo: fix)
* python-pygobject (should be a dependency of python-pygtk - todo: fix)

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

== Installation / Execution ==

* download file to Neo (e.g. using wget)
* Uncompress tar.gz file (e.g. tar -xzvf file.tar.gz)
* run:
export DISPLAY=:0.0
python SMSTool-x.x/SMSTool.py &

[[Category:Applications]]
[[Category:In_progress]]

SMSTool

2007-10-06T00:09:26Z

Kriss: /* Download */ - bug in setup.py and python import management

{{InProgress}}
[[Image:SMSTool-0.3.png|thumb|SMSTool - SMS Tool]]

== Overview ==
Until OpenMoko releases an official GUI-Tool to send SMS you can use SMSTool for that task.

This programm is written in Python using pygtk. It can be used only if those are present in your environment.

(see [[SMSTool#Environment]])

== Current Features ==

* Send SMS
** The default number is mine. - Leave a message if you like. ;-) --[[User:Kriss|kriss]] 22:54, 9 September 2007 (CEST)

== Planned Features ==

* Receive SMS

== Comment on GSM Support ==

* As there are no gsmd python bindings available at the time, SettingGUI uses python-subprocess and threads to communicate to the commandline of [[Gsmd#libgsmd-tool | libgsmd-tool]] for the time being.

== Download ==

[http://mput.de/~kristian/.openmoko/SMSTool-0.3c.tar.bz2 SMSTool-0.3b.tar.bz2]

An smstool package is available from the repository at [[User:Alessandro | Alessandro]]'s user page.

== Environment ==

The following archives will have to be installed:

* python-core
* python-misc
* python-lang
* python-pygtk
* python-subprocess
* python-threading (should be a dependency of python-subprocess - todo: fix)
* python-pygobject (should be a dependency of python-pygtk - todo: fix)

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

== Installation / Execution ==

* download file to Neo (e.g. using wget)
* Uncompress tar.gz file (e.g. tar -xzvf file.tar.gz)
* run:
export DISPLAY=:0.0
python SMSTool-x.x/SMSTool.py &

[[Category:Applications]]
[[Category:In_progress]]

SMSTool

2007-10-04T20:04:56Z

Kriss: /* Download */ - is bz2

{{InProgress}}
[[Image:SMSTool-0.3.png|thumb|SMSTool - SMS Tool]]

== Overview ==
Until OpenMoko releases an official GUI-Tool to send SMS you can use SMSTool for that task.

This programm is written in Python using pygtk. It can be used only if those are present in your environment.

(see [[SMSTool#Environment]])

== Current Features ==

* Send SMS
** The default number is mine. - Leave a message if you like. ;-) --[[User:Kriss|kriss]] 22:54, 9 September 2007 (CEST)

== Planned Features ==

* Receive SMS

== Comment on GSM Support ==

* As there are no gsmd python bindings available at the time, SettingGUI uses python-subprocess and threads to communicate to the commandline of [[Gsmd#libgsmd-tool | libgsmd-tool]] for the time being.

== Download ==

[http://mput.de/~kristian/.openmoko/SMSTool-0.3b.tar.bz2 SMSTool-0.3b.tar.bz2]

An smstool package is available from the repository at [[User:Alessandro | Alessandro]]'s user page.

== Environment ==

The following archives will have to be installed:

* python-core
* python-misc
* python-lang
* python-pygtk
* python-subprocess
* python-threading (should be a dependency of python-subprocess - todo: fix)
* python-pygobject (should be a dependency of python-pygtk - todo: fix)

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

== Installation / Execution ==

* download file to Neo (e.g. using wget)
* Uncompress tar.gz file (e.g. tar -xzvf file.tar.gz)
* run:
export DISPLAY=:0.0
python SMSTool-x.x/SMSTool.py &

[[Category:Applications]]
[[Category:In_progress]]

SMSTool

2007-10-04T20:04:15Z

Kriss: /* Download */ - 0.3b including setup.py - no other new features

{{InProgress}}
[[Image:SMSTool-0.3.png|thumb|SMSTool - SMS Tool]]

== Overview ==
Until OpenMoko releases an official GUI-Tool to send SMS you can use SMSTool for that task.

This programm is written in Python using pygtk. It can be used only if those are present in your environment.

(see [[SMSTool#Environment]])

== Current Features ==

* Send SMS
** The default number is mine. - Leave a message if you like. ;-) --[[User:Kriss|kriss]] 22:54, 9 September 2007 (CEST)

== Planned Features ==

* Receive SMS

== Comment on GSM Support ==

* As there are no gsmd python bindings available at the time, SettingGUI uses python-subprocess and threads to communicate to the commandline of [[Gsmd#libgsmd-tool | libgsmd-tool]] for the time being.

== Download ==

[http://mput.de/~kristian/.openmoko/SMSTool-0.3b.tar.gz SMSTool-0.3b.tar.gz]

An smstool package is available from the repository at [[User:Alessandro | Alessandro]]'s user page.

== Environment ==

The following archives will have to be installed:

* python-core
* python-misc
* python-lang
* python-pygtk
* python-subprocess
* python-threading (should be a dependency of python-subprocess - todo: fix)
* python-pygobject (should be a dependency of python-pygtk - todo: fix)

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

== Installation / Execution ==

* download file to Neo (e.g. using wget)
* Uncompress tar.gz file (e.g. tar -xzvf file.tar.gz)
* run:
export DISPLAY=:0.0
python SMSTool-x.x/SMSTool.py &

[[Category:Applications]]
[[Category:In_progress]]

PyPenNotes

2007-10-04T19:48:34Z

Kriss: 0.1 - can't do nothing yet - "Blue Ink Edition"

{{InProgress}}

[[Image:pyPenNotes-0.1.png|thumb|pyPenNotes - "Blue Ink Editon"]]

== Overview ==
Little tool to write notes using pen and touchscreen. Currently in proof of concept state.

This program is written in [[Python]] using pygtk. It can be used only if those are present in your environment (see [[SettingsGUI#Environment]]).

== Current Features ==

* draw and paint using blue colored pixels

== Planned Features ==

* redraw screen if needed
* change color
* sponge
* save notes

== Download ==
{|border=1
! Version
! Download
! Release Focus
|-
| 0.1 ('''current''')
| [http://mput.de/~kristian/.openmoko/pyPenNotes-0.1.tar.bz2 pyPenNotes-0.1.tar.bz2]
| initial release - can do nothing yet. :-)
|}

== Environment ==

:''For more, see [[Python]].

The following archives will have to be installed (source packages: python python-pygtk python-pycairo python-pygobject):

python-core python-misc python-lang python-pygtk

If you want to test this and do not have a build environment, you can 'ipkg install' the python components from the ScaredyCat [[repositories]].

{{note|These packages take up a considerable amout of space (about 10 MByte), make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

[[Category:Applications]]
[[Category:In_progress]]