Openmoko - User contributions [en]

Dfu-util

2011-03-05T10:16:04Z

Janvlug: /* Source Code */

{{Languages|Dfu-util}}

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

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

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

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

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

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

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

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

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

== Binaries ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Mac ===
Compiling dfu-util on Mac:
* http://lists.openmoko.org/pipermail/community/2007-July/008438.html
* [[User:SNMoore]]
* [[MacOS_X#Flashing_to_your_device]]
* [http://www.handheld-linux.com/wiki.php?page=Openmoko%20Flasher Openmoko Flasher] has a precompiled binary in the App bundle

== Manual ==

See [[Manuals/Dfu-util]]

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

[[Category:Flashing Openmoko]]

Dfu-util

2011-03-05T10:15:38Z

Janvlug: /* Source Code */ link to Dfu-util project page

{{Languages|Dfu-util}}

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

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

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

== Source Code ==
Dfu-util is currently maintained at http://dfu-util.gnumonks.org/. 
On Debian and Ubuntu, you'll need libusb-dev:
sudo apt-get install libusb-dev autogen pkg-config autotools-dev autoconf automake

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

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

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

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

== Binaries ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Mac ===
Compiling dfu-util on Mac:
* http://lists.openmoko.org/pipermail/community/2007-July/008438.html
* [[User:SNMoore]]
* [[MacOS_X#Flashing_to_your_device]]
* [http://www.handheld-linux.com/wiki.php?page=Openmoko%20Flasher Openmoko Flasher] has a precompiled binary in the App bundle

== Manual ==

See [[Manuals/Dfu-util]]

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

[[Category:Flashing Openmoko]]

Dfu-util

2011-03-05T10:13:41Z

Janvlug: /* Source Code */ updated repository to current location

{{Languages|Dfu-util}}

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

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

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

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

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

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

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

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

== Binaries ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Mac ===
Compiling dfu-util on Mac:
* http://lists.openmoko.org/pipermail/community/2007-July/008438.html
* [[User:SNMoore]]
* [[MacOS_X#Flashing_to_your_device]]
* [http://www.handheld-linux.com/wiki.php?page=Openmoko%20Flasher Openmoko Flasher] has a precompiled binary in the App bundle

== Manual ==

See [[Manuals/Dfu-util]]

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

[[Category:Flashing Openmoko]]

FOSDEM 2011

2011-02-02T15:26:13Z

Janvlug: /* Visitors */ Added myself

= FOSDEM 2011 =

Date: Saturday 5 and Sunday 6 February 2011

Unfortunately the request for a dedicated Devroom was declined.
So let's collect interesting talks and attendents. I.e. create sort of a "Visitors Guide".

The official FOSDEM agenda is here: http://www.fosdem.org/2011/

For reference, here is the page from last year: [[Fosdem_2010]]

= Main Talks =
tbd.

= Lightning Talks =
tbd.

= Stands =

Openmoko can share booth space at the http://hackable-devices.org/ booth, which sports open projects like Makerbot, Milkymist, Watts'nzCity, or Shruthi-1. You can find the tables in the H building. Contact wim or john @hackable-devices.org for more.

= Devrooms =

* Embedded: http://lists.fosdem.org/pipermail/fosdem/2010-December/001098.html
* Open Source Telephony: http://lists.fosdem.org/pipermail/fosdem/2010-November/001058.html

= Hardware fixes =
Is there anyone around who can do the buzz (and optionally the other) fixes on my FreeRunner?

= Visitors =
Yes, I will be there

{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
! '''Who''' !! '''Saturday''' !! '''Sunday''' !! '''Comment''
|-
| [[User:Hns]] || x || x || Will try to show a running GTA04 at the Hackable Devices stand
|-
| [[aSThRo/ Openmoko-fr.org]] || x || || Meet friends, watch some good confs, fix some phones?...
|-
| [[user:boudewijn]] || x || || Meet OM'ers, enjoy the weekend, helping a hand
|-
| [[user:wvdputte]] || x || x || booth bunny and logistic
|-
| [[user:nightlybuild]] || x || x || booth bunny and logistic
|-
| [[user:cmair]] || x || x || Enjoy the weekend, discuss open phones, watch great talks ...
|-
| [[User:GNUtoo]] || x || x || Will have some devices running SHR(htc dream,nokia N900, openmoko freerunner...)
|-
| [[User:Janvlug|Jan Vlug]] || || x || Hoping to get my Freerunner fixed...
|-
|}

[[Category:Community]]

FOSDEM 2011

2011-01-26T22:30:47Z

Janvlug: Buzzfix and more?

= FOSDEM 2011 =

Date: Saturday 5 and Sunday 6 February 2011

Unfortunately the request for a dedicated Devroom was declined.
So let's collect interesting talks and attendents. I.e. create sort of a "Visitors Guide".

The official FOSDEM agenda is here: http://www.fosdem.org/2011/

For reference, here is the page from last year: [[Fosdem_2010]]

= Main Talks =
tbd.

= Lightning Talks =
tbd.

= Stands =

Openmoko can share booth space at the http://hackable-devices.org/ booth, which sports open projects like Makerbot, Milkymist, Watts'nzCity, or Shruthi-1. You can find the tables in the H building. Contact wim or john @hackable-devices.org for more.

= Devrooms =

* Embedded: http://lists.fosdem.org/pipermail/fosdem/2010-December/001098.html
* Open Source Telephony: http://lists.fosdem.org/pipermail/fosdem/2010-November/001058.html

= Hardware fixes =
Is there anyone around who can do the buzz (and optionally the other) fixes on my FreeRunner?

= Visitors =
Yes, I will be there

{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
! '''Who''' !! '''Saturday''' !! '''Sunday''' !! '''Comment''
|-
| [[User:Hns]] || x || x || Trying to give a Lightning Talk or Embedded Devroom Talk
|-
| [[aSThRo/ Openmoko-fr.org]] || x || || Meet friends, watch some good confs, fix some phones?...
|-
| [[user:boudewijn]] || x || || Meet OM'ers, enjoy the weekend, helping a hand
|-
| [[user:wvdputte]] || x || x || booth bunny and logistic
|-
| [[user:nightlybuild]] || x || x || booth bunny and logistic
|-
| [[user:cmair]] || x || x || Enjoy the weekend, discuss open phones, watch great talks ...
|-
|}

[[Category:Community]]

FOSDEM 2011

2010-12-22T11:52:50Z

Janvlug: /* FOSDEM 2011 */ Added date.

= FOSDEM 2011 =

Date: Saturday 5 and Sunday 6 February 2011

Unfortunately the request for a dedicated Devroom was declined.
So let's collect interesting talks and attendents. I.e. create sort of a "Visitors Guide".

The official FOSDEM agenda is here: http://www.fosdem.org/2011/

For reference, here is the page from last year: [[Fosdem_2010]]

= Main Talks =
tbd.

= Lightning Talks =
tbd.

= Stands =

Openmoko can share booth space at the http://hackable-devices.org/ booth, which sports open projects like Makerbot, Milkymist, Watts'nzCity, or Shruthi-1. You can find the tables in the H building. Contact wim or john @hackable-devices.org for more.

= Devrooms =

* Embedded: http://lists.fosdem.org/pipermail/fosdem/2010-December/001098.html
* Open Source Telephony: http://lists.fosdem.org/pipermail/fosdem/2010-November/001058.html

= Visitors =
Yes, I will be there

{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
! '''Who''' !! '''Saturday''' !! '''Sunday''' !! '''Comment''
|-
| [[User:Hns]] || x || x || Trying to give a Lightning Talk or Embedded Devroom Talk
|-
| [[aSThRo/ Openmoko-fr.org]] || x || || Meet friends, watch some good confs, fix some phones?...
|-
| [[user:boudewijn]] || x || || Meet OM'ers, enjoy the weekend, helping a hand
|-
| [[user:wvdputte]] || x || x || booth bunny and logistic
|-
|}

[[Category:Community]]

User:Janvlug

2010-11-01T13:36:45Z

Janvlug: New page: * location of the desktop files: /usr/share/applications/

* location of the desktop files: /usr/share/applications/

Manuals/Om 2007.2

2010-09-21T22:10:00Z

Janvlug: Undo revision 82406 by Drive (Talk)

Please notice it is strongly recommended to update to any recent distro (probably the first thing you should do with your FR after some hours of drooling and playing), as the info herein is completely out of date, as is the software this is about.
See [http://wiki.openmoko.org/wiki/Distributions#SHR_-_Stable_Hybrid_Release Distributions]

===Navigating menus and applications===
====Today Page====

[[Image:Todaypage_reduced_true.png|200px|right]] Openmoko starts by displaying the "Today" page, which is your home page. Icons in the top row indicate the status of the phone. The bottom row consists of three tabs. The tab with a house on the left leads to the "Today" page you're viewing now. The central tab leads to the "Launch Task" page, which is the main menu used to start applications. The tab with gears on the right leads to the "Running Tasks" page, which is used to deal with currently open windows and applications.

 

[[Image:Todaypage_reduced_false.png|right|200px|]] The "Today" page is empty, as shown above, when you first start Openmoko. We explain below how to turn on the "full view", displayed to the right. In the full view, a second row of icons give quick links to commonly-used applications such as the dialer, the adressbook, mailbox and calendar. The main body of the screen displays a clock and other useful information.

See [[Today/2007.2]] for more information about the Today page and customization.

 

====Launch Task Page====

{{stub}}

[[Image:LaunchTasks.png|right|200px]] 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], [[Om_2007.2_Applications|Applications]], [[Games/Om 2007.2|Games]], Utilities, and All.

 

====Running Tasks Page====

{{stub}}

[[Image:RunningTasks.png|right|200px]] 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 from and switching to 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 cycle through active applications using the AUX button

Clicking the top-left of the screen displays the drop down ''task menu''. This menu lists all active applications and allows to switch directly to any one. ''Note:'' If the task menu is not shown, click and hold the [[#Aux|Aux]] button to bring up the Aux menu, and select "Toggle Fullscreen".

=== Using the terminal ===

To start a console from "Today" page, click the middle tab at the bottom of the screen to display the "Launch applications" page, then select Terminal in the "Applications" submenu. The multitaps keyboard slides up (and down) from the bottom of the screen automatically when you touch the screen.

====Setting date and time====

From the terminal, type the following, but replace ''MM'' with the month (01-12); ''DD'' with the day (01-31); ''hhmm'' with the time (0000-2359); ''YYYY'' with the year (optional); and ''.ss'' with the seconds (optional).

date -s ''MMDDhhmmYYYY.ss''

To make the change persist between reboots, sync the hardware clock with the updated system time.

hwclock --systohc

See [[Setting Date and Time]] for more discussion, including synchronizing with an NTP server.

Note: UNIX traditionally sets the system clock to GMT (UTC) or "Zulu" (Z time zone). So I use the stanza:
date -u MMDDhhmmYYYY.ss (well, I usually ignore the seconds)
Then I can set the local time using the techniques described elsewhere. iceworm

==== Accessing the microSD card ====

Mounted at /media/card by default.
<pre>
　mount /media/card
</pre>
If you have multiple partitions on the card, the first (/dev/mmcblk0p1) will be mounted at /media/card, the second at /media/mmcblk0p2, the third at /media/mmcblk0p3 etc. To setup the package management to write on the microSD card when installing new software follow the [[Package_management | package management guide]].

fox example :
<pre>
Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 252544 153560 98984 61% /
/dev/root 252544 153560 98984 61% /
/dev/root 252544 153560 98984 61% /dev/.static/dev
udev 2048 76 1972 4% /dev
/dev/mmcblk0p1 3362 1794 1568 53% /media/card
/dev/mmcblk0p2 476382 157368 294419 35% /media/mmcblk0p2
tmpfs 61928 380 61548 1% /var/volatile
tmpfs 61928 0 61928 0% /dev/shm
</pre>

==Switching Keyboards==

===Fix default===
Due to a bug, the default keyboard supplied on the 2007.2 doesn't allow you to enter the "/" or "\" characters, which should be on the same key (0?) as "+".
You can instead add these characters to other keys, in this example ">" and "/" are added to the 1 key.
You may also insert the tab character \t, which provides tab completion.
The | character may also be useful.
Edit <tt>/etc/multitap-pad/im-multipress.conf</tt>:

[keys]
KP_0 = +;=;/;\\
KP_1 = .;,;/;>;-;?;!;@;:;(;)
KP_2 = a;b;c;2
KP_3 = d;e;f;3
KP_4 = g;h;i;4
KP_5 = j;k;l;5;\t
KP_6 = m;n;o;6
KP_7 = p;q;r;s;7
KP_8 = t;u;v;8
KP_9 = w;x;y;z;9
KP_10 = A;B;C;2
KP_11 = D;E;F;3
KP_12 = G;H;I;4
KP_13 = J;K;L;5
KP_14 = M;N;O;6
KP_15 = P;Q;R;S;7
KP_16 = T;U;V;8
KP_17 = W;X;Y;Z;9

The buggy key is <tt>KP_0</tt> in the above file.

The ; character is also missing. You can add this character by adding ;\; to any of the lines above.

===Matchbox keyboard===

Another keyboard is available: matchbox-keyboard. It is a full QWERTY keyboard. This howto is based on a blog entry which can be found [http://www.ginguppin.de/node/15 here]

====Considerations====

Pros:
* All keys can be generated
* Takes up less space than the keypad (multitap-pad), leaving more space for the application

Cons:
* You pretty much have to use a stylus. With difficulty you can hit keys with the corner of a fingernail.

====How to install it?====

ScaredyCat release (http://buildhost.automated.it/OM2007.2/) or others distributions, use the following:

opkg remove -force-depends multitap-pad
opkg install matchbox-keyboard-inputmethod
opkg install matchbox-keyboard-im
opkg install matchbox-keyboard-applet

Otherwise, you'll have to download the ipk files from [http://www.ginguppin.de/files/keyboard-ipk.tar.bz2 here]. Assuming you have a working internet connection on your FreeRunner, you can do the following:

cd /tmp
mkdir matchbox-keyboard
cd matchbox-keyboard
wget http://www.ginguppin.de/files/keyboard-ipk.tar.bz2
tar -jxf keyboard-ipk.tar.bz2
opkg remove -force-depends multitap-pad
opkg install matchbox-keyboard-inputmethod*.ipk
opkg install matchbox-keyboard-im*.ipk
opkg install matchbox-keyboard-applet*.ipk
cd ..
rm -rf matchbox-keyboard

After that you'll have to restart the X server:
/etc/init.d/xserver-nodm restart

====How to add a keyboard toggle button====

To add a button to enable showing / hiding the keyboard, edit <tt>/etc/matchbox/session</tt>. In the list of applets after <tt>--end-applets</tt>, add <tt>keyboard</tt>, and restart your X server

====How to switch between matchbox-keyboard and multitap-pad====

If you want to keep the multitap keyboard, but also be able to start up the matchbox-keyboard, you can follow these ugly instructions:

First you must install matchbox-keyboard.
opkg install matchbox-keyboard

Do the following (from the terminal or an ssh session with DISPLAY=:0.0):
killall multitap-pad
matchbox-keyboard > /dev/null 2>&1 &

(If you type the above commands with multitap, you have to leave off the redirection of matchbox-keyboard output, since several of the keys you need are missing.)

Caveats: When you start the matchbox-keyboard, it stays up all the time. This will (among other things) prevent you from unlocking, since the keyboard covers the openmoko logo at the bottom of the lock screen. You will need to:
# nohup multitap-pad -d &
# killall matchbox-keyboard
to close it down, and at least get the matchbox keyboard going again. You should do that any time you're going to leave the neo alone for any length of time, so you can unlock it later.

To make sure you don't end up removing all your keyboard input capability, you can create a new .desktop file in /usr/share/applications/ for starting and closing the keyboard. This is pretty easy to do by copying and editing an existing .desktop file.

===Modified Matchbox Keyboard: finger friendly===
There is a modified Matchbox keyboard available on http://wiki.harnir.net/openmoko:keyboard-compressed .
The keyboard can be controlled without stylus and also includes everything needed for terminal-use.

===== Installation =====

Download one of the files below, uncompress and put it in ''/usr/share/matchbox-keyboard/'' on your Neo FreeRunner:

* [http://wiki.harnir.net/_media/openmoko:file:keyboard-compressed.xml.gz?id=openmoko%3Akeyboard-compressed&cache=cache general keyboard layout] DEAD LINK
* [http://wiki.harnir.net/_media/openmoko:file:keyboard-compressed-pl.xml.gz?id=openmoko%3Akeyboard-compressed&cache=cache Polish keyboard layout] DEAD LINK

If you want, you can change the name of the file to ''keyboard.xml'' or make a symlink to it. This way, ''matchbox-keyboard'' will use it automatically after next restart of the X server.

Note: I've installed keyboard layout from [[http://atariland.net/~dreilly/openmoko/]] before making this one. Please inform me if my layout works without these modifications, or if they are needed.

===== How does it look like? =====

==== Default layout ====
[[Image:Matchbox-keyboard-general.png]]
* ^[ - Escape
* ⇑ - Shift
* ⌫ - Backspace
* ⇔ - switch layout to the alternate
* ^C - Control
* ◆ - write a digit or symbol
* ↵ - Enter

==== Default Polish layout ====
[[Image:Matchbox-keyboard-pl.png]]

==== Shifted Polish layout ====

[[Image:Matchbox-keyboard-pl-caps.png]]

* ⇒ - Tab
* ⇑⇑ - Caps Lock

If you use general layout, special characters from the top row stay the same in the shifted layout.

==== Digits and symbols ====

[[Image:Matchbox-keyboard-symbols.png]]

When you select a desired key in this layout, keyboard immediately returns back to the alphabet keys.

==== Alternate keyboard layout ====

[[Image:Matchbox-keyboard-alternate.png]]

This layout is "persistent" - when you select a key it won't disappear by itself - you need to use the <key>⇔</key> key in the bottom-left corner of the keyboard to return to the default keyboard.

Alternate layout is meant for easy writing of medium or long numbers (decimal or hex, hence the A-F letters), IP and MAC addresses, RGB values, etc. You can find here also direction keys (↑, ↓, ←, →) for easier movement operations.

===Switch back to the original Openmoko keypad===

If you for whatever reason need to switch back, here are the steps:
opkg remove matchbox-keyboard-inputmethod matchbox-keyboard-im matchbox-keyboard-applet
opkg install multitap-pad

Comment or delete the following lines in /etc/gtk-2.0/gtk.immodules :
#"/usr/lib/gtk-2.0/2.10.0/immodules/libmb-im-invoker.so"
#"matchbox-im-invoker" "Virtual Keyboard" "" "" "*"

Now restart the xserver:
/etc/init.d/xserver-nodm restart

== Turning off the boot sound ==

To stop the boot sound playing simply edit '''/etc/pulse/session'''. Look near the bottom of the file, you should see something like:

# Load samples
load-sample startup /usr/share/openmoko/sounds/startup_openmoko.wav
load-sample touchscreen /usr/share/openmoko/sounds/touchscreen_click.wav

To disable the boot sound and/or the touchscreen tap sound simply place a # at the start of the line, ie:

# Load samples
#load-sample startup /usr/share/openmoko/sounds/startup_openmoko.wav
#load-sample touchscreen /usr/share/openmoko/sounds/touchscreen_click.wav

If you want to change the sound, simply change the .wav file name to something else.

[[Category:Om 2007.2]]
[[Category:Manuals]]

Smedia Glamo 3362

2010-08-30T19:46:35Z

Janvlug: /* Timing settings */

== Summary ==
Glamo3362 is the graphics chip in the [[Neo FreeRunner]]. It supports 2D and 3D acceleration, and provides an extra SD interface which is used for the uSD card slot (the other one is used for the [[Wlan]] adaptor).

Glamo's 2D engine is currently used to accelerate solid fills and blits in both XGlamo (Kdrive) and X.org (xf86-video-glamo).

The datasheets for the chip are not public, but have been made available (under NDA) to a few community volunteers who are interested in working on accelerated drivers. Please post to the [http://lists.openmoko.org/mailman/listinfo/devel devel mailing list] if you are interested in joining in this effort. [http://kerneltrap.org/mailarchive/openmoko-community/2008/11/13/4088744 This mailing list thread] has some discussion on the topic.

== MicroSD support ==
* Supports SDHC (Secure Digital High Capacity) cards up to 8GB
* Connected to: Glamo 3362 MMC/SD controller
* [[Supported microSD cards]]
* Specifications: [http://www.sdcard.org/about/memory_card/pls/ SD Simplified Specification], [http://www.mmca.org/compliance/buy_spec/AN_MMCA050419.pdf MMC (partial)], [http://www.sandisk.com/Assets/File/OEM/Manuals/manual-rs-mmcv1.0.pdf MMC (product manual)]

== Bus Interface ==
* Glamo is connected to the [[Samsung S3C2442B B54]] address/data bus, accessed via MMIO.

== Hardware Acceleration ==
This is a compilation of all the publicly available information that is known about the Glamo 3362 used in the Neo FreeRunner GTA02 and links to past and present projects utilizing the Glamo's hardware acceleration. If anyone is working or has worked on hardware acceleration with the Glamo please add any links and any further information to this page.

===Hardware Accelerated Projects===
* [http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket Blog post] by balrog accounting his working creating an accelerated mplayer driver using the Glamo 3362
** [http://repo.or.cz/w/mplayer/glamo.git?a=tree;f=drivers/libglamo;h=c268ca2a4a98517b6e218669b0a46d2dad737abb;hb=HEAD Source for libglamo] interface used for mplayer acceleration
* Xglamo
** [[Media:xglamo-graphics.pdf | xglamo-graphics.pdf]]
** [http://git.openmoko.org/?p=xglamo.git;a=summary Xglamo source]
* [http://www.bitwiz.org.uk/freerunner-dri Tom White's DRI project]
* xf86-video-glamo (driver for X.org)
** [http://git.openmoko.org/?p=xf86-video-glamo.git;a=summary Git repository]

===Known Features===
* 8MB internal SDRAM
* 16bit local bus interface to S3C2410
** The bus is limited in speed to about 7 Mb/s. This means that rendering is slow unless it can follow an accelerated path, and that texture uploads for 3D graphics would be slow.
* 2D acceleration
* 3D acceleration
** 256x256 Max Texture Size
** No Render-To-Texture Support
** 511x511 Max 3D Destination Buffer Size
*** Note that this is smaller than the VGA screen.
** Pipeline: Transform, cull, lighting, clipping, setup, rasterizer
** Standards compliance: OpenGL ES 1.0, OpenGL ES 1.1 and Mobile D3D.
* [http://en.wikipedia.org/wiki/H.263 h.263] codec (encode/decode)
* LCM controller
* SD-Card controller
* hardware JPEG encoder/decoder
* Camera interface and imapge processing (unused)

===Timing settings===

The CPU (S3C2440) memory bank setting values can be adjusted in such a way that Glamo performance is increased. Bootloader usually takes care of this setup so to change these settings at startup, bootloader with different values can be flashed. Besides flashing bootloader, one can use other tools that can set the memory bank.

In depth description and discussion can ge found [http://www.mail-archive.com/community@lists.openmoko.org/msg60256.html here].

Qi with applied patch (binary only!):

* [http://www.openmobile.nl/pages/downloads.php#qiglamo Openmobile.nl website's page]
* [http://www.openmobile.nl/modules/download_gallery/dlc.php?file=53 direct download link]

Runtime tweaking can be done by direct writing via [http://www.bsdmn.com/openmoko/glamo/timings/ memwrite] or [http://git.debian.org/?p=pkg-fso/omhacks.git;a=blob;f=README omhacks]:

To apply 2.4.2 timings:

./memwrite $((0x48000008)) $((0x1380))

or

om screen glamo-bus-timings 2-4-2

To see the timings that are currently in use:

./memwrite $((0x48000008))

or

om screen glamo-bus-timings

[[Category:Used chip]]
[[Category:Neo FreeRunner Hardware]]
[[Category:Hardware ideas]]

[[Category:Used chip]]
[[Category:Neo FreeRunner Hardware]]
[[Category:Hardware ideas]]

Manuals/SHR

2010-08-15T15:49:13Z

Janvlug: /* SwapSpace */

{{Languages|Manuals/SHR}}
{| align="right"
| __TOC__
|}

==SHR Introduction==

Welcome to '''[[SHR]]''', a community driven distribution for (not only) Openmoko Neo phones.

[[Image:SHR-Logo.png|200px|thumb|center|SHR]]

'''SHR''' (Stable Hybrid Release) is here to provide you with Root FileSystem images that you can easily install into your device to use as a daily phone and PDA. There are many prepackaged programs available that can be installed upon demand by users, it can also be used by developers as a base image for customized and flavored distribution or release. '''SHR unstable (SHR-U)''' is a testing environment before software gets stabilized and it is the main testing ground for [[FSO]] releases. '''SHR testing (SHR-T)''' images provide as much stability as possible for day-to-day usage.

==Installation==

===Getting SHR===

You need to download two files for your version as above: kernel and root filesystem. Depending whether you will be installing into the internal [[NAND memory]] or on the [[microSD]] card, you need to either get .jffs2 file for NAND or .tar.gz file for microSD.

- Get the latest kernel from the below linkpages. Starts with uImage-...

- Get the root filesystem, for NAND: full-om-gta0_.jffs2, for µSD: full-om-gta0_.tar.gz

The above are '''full''' images. You can also choose images with less packages, marked as '''lite'''.

;GTA02 Neo FreeRunner
*testing line: http://build.shr-project.org/shr-testing/images/om-gta02/
*unstable 2.6.3* line: http://build.shr-project.org/shr-unstable/images/om-gta02/
*( unstable 2.6.29 line: http://build.shr-project.org/shr-unstable.29/images/om-gta02/ )

;GTA01 Neo 1973
*testing line: http://build.shr-project.org/shr-testing/images/om-gta01/
*unstable 2.6.29 line: http://build.shr-project.org/shr-unstable.29/images/om-gta01/

;Image lite to image full
If you flashed a '''lite''' image and want to upgrade to the '''full''' image run:

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

;Kernel modules
The images of the filesystems mentioned above (.jffs2, .tar.gz), already contain the newest kernel modules.

Get the new kernel modules if you only want to flash a new kernel, but not a whole new file system. From the same page as the kernel download the modules to match your kernel (their dates should be the same). Use sftp to put that file on the FreeRunner via the usb connection. Run gzip to unwrap the modules:
# gzip -dc modules-...tar.gz | tar -xf - -C /

===Installation on Flash===

In order to install your SHR distribution directly to your FreeRunner Flash memory (NAND), you need to get the desired filesystem file ( <tt>.jffs2</tt> ) as described above and flash your device using the <tt>dfu-util</tt> tool.

Please visit [[Flashing the Neo FreeRunner]] for more details about flashing and see [[Dfu-util]] for detailed information about the dfu-util.

{{Note|Your battery must be charged (sufficiently) before NAND flashing. Symptom of insufficient charge: Your progress bar "####" stops while flashing. If so, you must charge, and later you should be able to make the complete flash.}}
Commands to flash the filesystem and the kernel:

for the GTA02 Neo FreeRunner:

# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D full-om-gta02.jffs2
# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-om-gta02-latest.bin

for the GTA01 Neo 1973:

# dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a rootfs -R -D full-om-gta01.jffs2
# dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a kernel -R -D uImage-om-gta01-latest.bin

===Installation on the microSD Card===

Installing SHR on your microSD Card depends on the Bootloader you are using, ''uBoot'' or ''Qi''.

In simple words, the difference between both systems resides on how you must prepare your microSD Card and files you use to fill them:

* If you use ''uBoot'', you need to create two partitions. First partition, not so big, in FAT16 or ext2 where you have to place the kernel file (<tt>uImage-om-gta02-latest.bin</tt>) and second partition in ext2 or ext3 where you have to uncompress the filesystem file (<tt>shr-image-om-gta02.tar.gz</tt>).

* If you use ''Qi'', you only need an ext2 partition into your µSD Card where you uncompress the filesystem image file (<tt>shr-image-om-gta02.tar.gz</tt>). In this case Qi Bootloader is going to look for the kernel image into the <tt>/boot</tt> directory for file named <tt>uImage-GTA02.bin</tt> .

===Bootloaders===

Make sure you have recent and correct versions of [[Booting_from_SD | uBoot]] or [[Qi]] installed, please visit the links for detailed information and tips. For example [[Android]] uses modified [[Qi]] which can cause you troubles when using SHR.

===SHR version===

Should you ever later wonder what version of SHR you have actually installed, please run

timestamp of image creation:
cat /etc/timestamp

latest shr version from opkg upgrade (this version is changed everytime someone builds task-base on shr buildhost):
cat /etc/shr-version

{{Note|Please note that this is true only for shr-u, with shr-t running opkg update;opkg upgrade does not change the SHR version. Only flashing or a new image download can change the SHR version. But this will be also merged to shr-t later.}}

==Running SHR==

===First boot===
[[Image:Shr-boot-preview.png|200px|thumb|center|SHR Boot Splash screen]]

====Booting====
First boot usually takes a bit longer as your phone's new software needs to do some initial setting up. It is recommended to reboot after this first boot (and after the initial setup), to make sure that all packages get initialized properly.

====Initial Setup====

During the first run, Setup is automatically initiated to walk the user through basic setup of the Enlightenment desktop environment. These steps vary as both Enlightenment desktop and SHR evolve, at this point preferred language and desktop profile options are available. The Profile offers to choose a preconfigured way of displaying the desktop. Illume2-SHR (with continuous development) and Illume-SHR (discontinued) profiles are available. '''Illume2-SHR''' is the recommended Profile.

{| class="wikitable"
| [[Image:SHR-Setup-Language.png|200px|thumb|language selection]]
| [[Image:SHR-Setup-Profile.png|200px|thumb|theme selection]]
| [[Image:SHR-Wizard.png|200px|thumb|SHR Wizard]]

|}

Note, you may need to ssh into the device and run /usr/bin/xinput_calibrator_once.sh if calibration is wrong. I found this using a Neo1973 and SHR images from around May 2010.

====SHR Wizard====
After the initial Setup, SHR Setting Wizard is launched to allow setting up your local phone settings and setting up root password. Sometimes a '''Please wait''' message is displayed for a long time, as the wizzard is waiting for the SIM card to be initialized.

===First look===
[[Image:SHR-First-Look.png|200px|thumb|Desktop screen]]
[[Image:SHR-Task-Buttons.png|200px|thumb|Task switch buttons]]
====Illume desktop====
Illume desktop is the default home screen of the SHR desktop.

Application definition files located in /usr/share/applications are displayed here as icons. All applications are ran fullscreen and you can switch between them by using the the '''< left''' or '''right >''' arrows on sliding shelve available by tapping Top Shelf on any empty space. To close applications, choose '''X''' from the same sliding shelve.

Several icons (e-gadgets) are placed in the Top Shelve:

The '''L''' icon is to switch between left/right mouse click. By taping this icon the icon gets changed to R and next tap will be as right click. After the click, the behavior is automatically switched back to Left click so any following taps are left click again.

'''Mode Switch Icon''' allows to split the screen horizontally or vertically, thus allowing to display two applications at the same time.

'''Keyboard icon''' pops up or hides the Keyboard.

'''Illume Settings''' icon (represented by SHR logo) invokes the [[#Illume_settings | Illume desktop settings]].

'''Home Icon''' allows quick go to the home desktop/application.

'''GSM''' and '''Battery''' status icons, as well as '''time''' are displayed by default, Bluetooth and WiFi status icons available in the setting of the Top Shelve content.

To '''reconfigure the Top Shelve''' itself, use the L/R click icon to Right click on the Top Panel and choose: Illume Indicator->Set Content to add or remove items from the Top Panel. Or, upon right click on the Top Panel you can also choose Illume Indicator->Begin Move/Resize to move your icons around. To escape this mode, you must click on the L/R gadget's edge, it will switch to L, then choose R again, right click on the Top Panel and select Illume Indicator->Stop Move/Resize.

====Keyboard====

Keyboard comes up automagically when a text field is tapped or you can also toggle the keyboard by it's icon in the Top Shelve. In the Keyboard, dictionary switcher is the arrow-up on left side, alternative keyboard layouts are under the ABC button on the right. The Default keyboard has English dictionary enabled. For Space quick slide left-to-right, for Enter, quick slide up-down, to quick change keyboard layout quick slide down-up. While typing with a dictionary enabled keyboard, possible word options start appearing in the keyboard's upper part or more word options are available under the arrow-up on the left. When happy with the word, tap it, it will be pasted into the text field with a space attached. The Keyboard and dictionary can [[#Illume_keyboard_and_dictionaries | easily be localized]].

====Copy and Paste====

In '''E based''' applications, for example the phone suite (contacts, messages...), by tapping and holding down for over two seconds the Select-Paste menu will pop up. By pressing Select, you can now swipe through the text to select desirable part. Tap and hold down again, Copy-Cut-Cancel menu will appear to Copy to clipboard. Another long tap will provide Select-Paste for Paste.

In '''Gtk''' based application, you can use keyboard for Ctrl-C (Copy) and Ctrl-V (Paste) or items in Menu if provided.

In the Vala '''Terminal''', you can select simply by swiping through the text and for Paste there is an icon in the menu bar of this application.

Copy & Paste between different toolkits has some limitations. See the table below. In Ventura, select is possible, but copy/paste doesn't seem to work at all.

{| cellspacing="0" class="wikitable" border="1" style="font-size: 85%; text-align: left;width="100%"
|-
! From -> To
! to GTK
! to E
! to Terminal
|-
| from GTK
|style="background:#88FF88;"|Works
|style="background:#88FF88;"|Works
|style="background:red"|Doesn't work
|-
| from E
|style="background:red"|Doesn't work
|style="background:#88FF88;"|Works
|style="background:#88FF88;"|Works
|-
| from Terminal
|style="background:red"|Doesn't work
|style="background:#88FF88;"|Works
|style="background:#88FF88;"|Works
|-
|}

====Alarm====

The Alarms application (installed by default) allows alarm presetting for single or repeatable alarms. If you set an alarm and turn your Openmoko FreeRunner off, at the time of the alarm the phone will be powered up and alarm will sound.

====Phone applications====

Besides other software, SHR comes with 4 main phone applications: ''Dialer'', ''Contacts'', ''Messages'' and ''Phone log''.

{|
| [[Image:SHR-Dialer.png|200px|thumb|Dialer]]
| [[Image:SHR-Contacts.png|200px|thumb|Contacts]]
| [[Image:SHR-Mesages.png|200px|thumb|Messages]]
| [[Image:SHR-Phonelog.png|200px|thumb|Phone log]]
|}

=====PIM data=====

======Storage======
PIM data (contacts, messages etc.) are stored through internal opimd storage mechanism into

/etc/freesmartphone/opim/pim.db

This database can easily be copied from one SHR installation to another, for example due to a need for reflashing. The Contacts application can display a picture of the contact. As the pim.db database contains a path to the picture files only but not the pictures themselves, therefore, in case of PIM data backup or transfer, these picture files '''need to be copied too'''.

======SIM Contacts======

SHR phone applications do not read SIM contacts by default but you can use SIM Manager to access your SIM contacts '''SHR Settings -> Others -> SIM Manager''', which allows you to edit and import the SIM contacts into the internal storage. You can also use Pisi to import your SIM contacts into opimd.

======Synchronization======

'''[[Pisi]]''' is an application for synchronizing PIM data and can be used for import and export your contacts, calendar entries etc. between various sources, like VCF, LDAP, Google and more. To install Pisi:

opkg install pisi

After installation, edit Pisi configuration in '''.pisi/conf''' in your home directory. To have a correct opimd fields support, make sure '''field_support=TRUE''' is enabled in opimd section.

With the installed package you have a well-documented sample that is placed at
/usr/share/doc/pisi/conf.example
You may copy the file and rename this file to
/home/root/.pisi/conf
as a starting point - then edit this file in order to configure your PIM synchronization data sources. Look at section

[opimd]
description=OPIMD Contacts
module=contacts_opimd
field_support=TRUE

=====Idle screen=====
[[Image:SHR-Idle_Screen.png|200px|thumb|Idle Screen with GSM operator strength and name. GPS, WiFi, Display and CPU are requested, Battery status.]]
Upon press of the AUX button Idle Screens locks up the display. AUX press or a finger slide on the Slider unlocks the screen.

At the top, status icons are shown to indicate what is going on in the phone:

From left to right:
GSM strength and operator. Requested Resources (GPS, Display etc., when for example Display is requested, the screen will not dim). Battery capacity.

====Hardware Buttons====

=====Power Button=====

[[Image:SHR-Quick-Settings.png|200px|thumb|Quick Settings]]

The '''PWR''' (Power) button is mapped to start [[#quick_settings | Quick Settings]] screen (Illume System menu in older versions) on a short press.

Mapping of the PWR button be configured via the '''Illume Settings-> Input -> Key Bindings'''.

Pressing the Power button for longer then 8 seconds will force a complete power down of the device. This is hardconfigured in the kernel.
<div id="quick_settings"> </div>
The '''Quick Settings''' screen provides several toggles: Airplane mode, Phone profiles, Power settings and Power buttons.

=====Auxiliary Button=====
The '''AUX''' (Auxiliary) button is mapped to toggle on/off the SHR Idle screen. Mapping of this button is configured in /etc/phonefsod.conf

idle_screen = aux,lock

You can configure the [[#idle_screen | Idle Screen]] to come up even during active phone call by adding '''phone''' to the setting:

idle_screen = aux,lock, phone

<div id="idle_screen"> </div>
The '''Idle Screen''' shows current date and time, missed calls and messaged and also what [[#FSO_Resources | FSO resources]] are currently being requested - used.

======Replacing idle screen======

If you wish to use the E simple LOCKED screen instead of the SHR Idle Screen, edit '''/etc/phonefsod.conf''' to this:

# when to show idle screen
# ...
# idle_screen = aux,lock
idle_screen =

You need to restart phonefsod to make the change happen.

Also, change key mapping for the AUX button by setting '''Illume Settings''' -> '''Input''' -> '''Key Bindings''', bind the key '''XF86Phone''' to '''Desktop Simple Lock'''

====Settings applications====

Many desktop and phone settings are possible to do via graphical interface. [[#SHR_Settings | SHR Settings]] provides access to most common phone personality settings and is accessible by tapping Settings icon on the desktop. [[#Illume_settings | Illume settings]] (and Enlightenment desktop settings) are accessible on Top shelve by tapping the "SHR Logo" icon. Also, FSO and SHR phoneui applications have configuration files in /etc where some of the above mentioned apps write and that can be edited manually.

===First steps===

Right after installation and first boot you might want to do a few initial steps like adjusting the call volume and some other tasks.

====Audio - Call Volume====

During the first phone call please use the Volume and Mic sliders on the Active Call Screen and adjust them to fit your preferences. The new improved settings will be used for all in/out-going calls thereafter.

====Network Connection====

[[#Networking|Establish network connection]] and SSH into your phone. You can establish connection either via USB to your desktop and enable NAT or you can connect through Wifi.

====Initializing the opkg database====
''Initialize the opkg database'' in order to install some applications from SHR repositories or from other sources, for example [http://opkg.org opkg.org]. While being online, you need to run

opkg update

Searching in the opkg database can take a long time. You can speed things up by dumping the database into a file and grepping it through. Do this only once or after every opkg update:

opkg list > packages.txt

Then you can search quickly for package name, for example for [[Navit|navit]]:

grep navit packages.txt

====SwapSpace====

When the RAM is used up, applications get killed. This is particularly bad while doing opkg upgrade. Therefore you might want to create a swap space. Read [[SwapSpace]] article or the [http://shr-project.org/trac/wiki/swap swap article on the SHR wiki].

==Settings==
===SHR Settings===
[[Image:SHR-Settings-main.png|200px|thumb|SHR Settings]]

SHR Settings is the main setting application of SHR. It provides an easy way of setting up your phone to your liking - from phone related settings, to requesting resources in order to prevent screen dim or suspend (for example while using GPS).

Please refer to [[#FSO_Resources | this section]] about a better way to manage preventing screen dim or suspend.

While some settings are persistent over reboots, others are not.

====Main Screen====
The main screen is divided into eight categories, which contain several modules. Every SHR Settings module has a specified task - for example controlling the GSM antenna power, setting the time etc.

====Phone====
Here you can set if the GSM antenna is on and if your phone number is shown when you call someone.

'''GSM'''
In GSM settings you can turn off and on GSM module. After turning off antenna, whole GSM modem is turned off.

To list available providers, click on Operators button. Scanning can take some time. After a while, a list of operators should pop up.

You can't connect to operators marked [forbidden].

Selecting an operator from the list also changes modem registration mode to manual. It won't register to other network, even if some is available and has better signal strengh. To return to automatic mode, click "Automatic" button in operator list.

'''Call'''
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Phone.png|200px|thumb|Phone settings]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-List-providers.png|200px|thumb|List providers]]

|}

You can set if your phone number should be displayed to other party. You can either depend on network decision ("By network") or force it manually ("Manual")

'''Phoneutils'''

For the default SHR phone applications to be able to correctly parse incoming calls/messages and match them with your contacts, you will need to set the right country code for your location. (for example 420 for Czech republic) for more info, please go to: http://wiki.openmoko.org/wiki/Phone_Prefixes

'''SIM'''

Here you can view some informations about your SIM card and clean phone and messagebooks.

====Profiles====

Here you can select the current profile, which the device should use to determine ring tone etc.

'''Current profile'''

Here you can adjust properties of the currently used profile.

To change the ring tone, click the "Change" button.

To use your own ring tone, place it in /usr/share/sounds directory.

After selecting a sid tune as the ring tone, there are available controls to select tune number from the file.

If you like to test a .sid you can play it using this command on the FR:

gst-launch filesrc location=Arkanoid_PSID.sid ! siddec tune=2 ! alsasink

Note that it's a ! used and not a | to construct the gstreamer pipe command.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Profiles.png|200px|thumb|Profiles]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Profiles-Ringtones.png|200px|thumb|Ringtones]]

|}

====Connectivity====

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Connectivity.png |200px|thumb|Connectivity top]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Connectivity2.png |200px|thumb|Connectivity bottom]]
|}

'''WiFi'''

With the "WiFi radio" toggle you can set, if the wifi module is powered. WiFi radio has to be turned on before trying to connect to a WiFi network, unless you try to connect through [[Mokonnect]] which is capable of powering it up.

'''GPRS'''

To enter APN, login and password fields, just click on the actual value (default: "internet"). Your phone provider can provide the required configuration options.

{{Note|You can also use Mokonnect to manage your GPRS connection}}

'''USB'''

With this toggle you can switch USB port between device (Neo to PC) or host (device to Neo) modes.

'''Bluetooth'''

To power up Bluetooth module, switch the "Bluetooth radio" toggle to "On". After that, the "Visibility" toggle should arrive - set it to "On" if you want your FR to be visible by other Bluetooth devices on scanning.

====Power====

'''Battery'''

This module displays informations about battery state - charge, voltage, remaining time etc. To update the data, click the "Update" button.

Here you can also force enable 500mA charging.

'''Display'''

With this slider you can easily set the backlight brightness.

{{Note|This setting isn't permanent over sessions. At boot backlight is set back to 80%.}}

'''Power'''

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Power.png |200px|thumb|Power]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Timeouts.png |200px|thumb|Timeouts]]
|}

'''Timeouts'''

Timeouts are reached in this order: Busy state -> idle -> idle dim -> idle prelock -> lock -> suspend.

{{Note|Storing of this setting via D-bus calls is not supported in the new API of Vala rewrite of FSO2 and therefore SHR Settings doesn't have a functional setting for this.}}

You can set values of idle timeouts manually. The default parameters are stored in '''/etc/freesmartphone/conf/GTA02/fsodeviced.conf''' but customized '''.fsodeviced.conf''' file in your home directory will take precedence:

[fsodevice.kernel_idle]
suspend = 20
lock = 2
idle_prelock = 12
idle = 10
idle_dim = 20

====Appearance====

'''Theming'''
[[Image:SHR-Neo-Theme.png|200px|thumb|Neo theme]]

The Apperance section allows you to change between installed themes. To install more themes, see also [[#Installing themes | Installing themes]].

You can change finger size - this will mainly effect vertical spacing between widgets.

Switching between engines:

E can be switched to use different engines. The default engine is x11. Alternative engine x11-16 is not supported and results in buggy behavior of several applications, for example the phone suite or Ventura browser. It's usage is not recommended.

Changing system boot Splash screen is also possible in this module. To install more splash screens, see also [[#Installing splash screen themes|Installing splash themes]].

====Position====

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-GPS.png |200px|thumb|center|GPS]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-GPS-Satelites.png |200px|thumb|GPS Satelite details]]
|}

'''GPS'''

By default, GPS is turned on only when requested by an application. That state corresponds to "Auto" setting. After changing to "Manual", you can force set it to on or off.

'''GPS information'''

This page can be used to monitor GPS status. You either have to turn GPS on manually or start another application to enable the GPS.

You can also view information about every visible satellite and check, which are used for getting a fix. To do that, click "Satellite details".

'''Remove AGPS data'''
If you experience problems with GPS, turn it off, click "Remove AGPS data" and reboot your Neo.
Assisted GPS ([[aGPS]]) support GPS receiver to find position by non-satellite information.

====Date/time====

[[Image:SHR-Settings-Date-Time.png |200px|thumb|Date & Time]]

'''Time'''

Here you can view and set the time. By default, the time is just displayed, To adjust it, click on "Set time".

After finishing adjusting, click the "OK" button.

'''Date'''

This module displays the current date.

====Others====

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

[[Image:SHR-Settings-Others.png |200px|thumb|Others]]

'''PIM'''

Pim data are stored in opimd domains. Every opimd domain has different backends to store its data to. The domain reads data from every backend and writes data to the default backend. This elector allows you to choose the backend that stores newly generated data, it doesn't copy or move existing data to a different backend.

'''Services'''

The services selector is listing scripts from /etc/init.d/ directory.

After clicking on a servis, you can either start, restart or stop the service and view the result.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Services.png |200px|thumb|center|Services]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Service-restart.png |200px|thumb|Services debug screen]]
|}

'''Userspace backups'''

Here you can either archive or restore your files and configurations.

=== Illume settings ===

The Illume desktop can be easily customized - tap the Settings icon (SHR Logo) on the Top Shelve.

'''Illume settings''' provides various options to alter the desktop environment. You can change sizes of elements, single or double click, wallpaper. To access all the various options, open Illume Settings and slide the visible icons to the left, to view more options on the right hand side.

Some setting screens are not resized properly to fit the phone's display - for example the Wallpapper setting. This is a known bug already reported upstream.



==Localization==

=== Localize SHR manually ===

[[Image:SHR-Illume-Settings-Languages.png|200px|thumb|Setting Language]]

====Desktop environment====

You can change the language of the SHR desktop environment by using the Settings of Illume. For Example, for Czech language: in the Illume top shelf go to Settings (SHR Logo) -> Language -> Language Settings -> and choose: Čeština. If your language is not in the menu you can install by using opkg.

You can list all available languages by running:

opkg list | grep eglibc-locale-

And install the language of your choice (for example czech):

opkg install eglibc-locale-cs

After this, the Language Settings of Illume will offer Czech.

This will localize the Illume environment and will also set correct lang environment variable of your desktop.

====Applications====

If you wish to have other applications localized, you need to install translation for each of them (presuming it is available):

This will install czech localization for SHR phone applications, SHR Settings and TangoGps:

opkg install libframeworkd-phonegui-efl-locale-cs shr-settings-locale-cs tangogps-locale-cs

====Terminal environment====

For localized terminal environment (ssh login) set lang variables in /etc/profile.d/locale.sh, example for Czech language:

export LANG=cs_CZ
export LC_ALL=cs_CZ

====Illume keyboard and dictionaries====
[[Image:Illume-keyboards-terminal-dutch-nl-screenshot.png| Dutch terminal virtual keyboard|256px|thumb]]
→ more details on page [[Illume keyboard]]

Unlike other input methods for mobile devices, the Illume keyboard is corrective rather than predictive. It detects what you mean, even if some letters mistyped. If you accidently hit some keys next to the correct one Illume still reckognizes the word. This kind of compensates for the small size of the keys. Keep a key pressed for a longer time to affirm you really mean it.

An English dictionary is used by default. A few dictionaries for other languages are included in the SHR distribution. In addition, every dictionary for [http://en.wikipedia.org/wiki/MySpell myspell] can be used.

You can install a different keyboard with a layout which fits your language or alternatives for the default keyboards like the numerical one. The localized [[Illume keyboard]]s are available in the SHR repository under the name ''illume-keyboard-LANG''.

==== German (and Austria) Language ====

See [[Configure_SHR_for_German-speaking_use]] for detailed customization for german speaking.

===Date and time===
{{Note|This needs a complete and correct rewrite.}}

Date and time are automatically set from GPS or Network. The easiest way of setting the time for the first time is to run TangoGps (GPS & Map icon) and obtaining GPS fix. Time will then be set automatically.

The local timezone is automatically retrieved from the GSM network.

It is possible to instruct framework on how to set the time and timezone in /etc/frameworkd.conf :

[otimed]
# a list of time/zone sources to use or NONE
timesources = GPS,NTP
zonesources = GSM
# use an ip address here, otherwise DNS resolution will block
ntpserver = 134.169.172.1

To disable automatic date/zone settings, simply create an empty [otimed] section in /etc/frameworkd.conf

Timezone change

Create a symlink named /etc/localtime which points to the appropriate file in /usr/share/zoneinfo. For example, if you're in France., the following command will link the correct zoneinfo file to your /etc/localtime, giving you the correct time:

ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime

Afterwards, edit /etc/timezone if necessary [?]

Local timezone work instantly for the current boot when:

TZ="Europe/Paris"
export TZ

For a permanent timezone change edit /etc/profile and change to:

TZ="Europe/Paris"

If you use UTC time, set '''UTC=yes''' in '''/etc/default/rcS'''.

Adjusting time manually:

Via SHR-Settings -> Date/time -> Set time

From linux based desktop:

ssh root@192.168.0.202 "date -u -s `date -u +%m%d%H%M%Y.%S`"

The above does NOT work from Ubuntu as of 4/2/2010, the proper format is:

ssh root@192.168.0.202 "date -u -s `date -u +%Y.%m.%d-%H:%M:%S`"

Set the hardware clock to the system time:

hwclock --systohc

Is this better?:

hwclock --utc --systohc

==FSO Resources==

[[FSO]] is in control of each device. These are called ''resources''. If the software wanting to use the device is capable of requesting this resource via <tt>d-bus</tt>, FSO will do this, otherwise you might need to power the device manually. After the requested resource is released, FSO will power it down. Manual resource request can be done through ''SHR Setting'' or you can use <tt>fsoraw</tt> command. (Using fsoraw is faster and better than running dbus commands)

opkg install fsoraw

Example of usage fsoraw:

fsoraw -r Display mokomaze

See [[FSO Resources]] for more details on using the following resources:

'''Wifi'''

Unless this resource is enabled you've no eth0 and wifi module is completely un-powered. Use the [[Mokonnect]] network manager to set up networks, it will power Wifi up automatically when needed.

'''Bluetooth'''

You need to have this resource requested to have bluetooth module powered.

'''GPS'''

The fso-gpsd is a daemon waiting for gsmd connections, automatically powering the device on and off. When a connection exists, it powers up the GSM. In SHR Settings you can switch GPS completely off SHR Settings -> GPS -> Manual > Off

'''GSM'''

You need to have this resource requested to have GSM module powered.

'''Display'''

While this resource is requested the display won't be blanked and suspend is disabled.

'''CPU'''

While this resource is requested then suspend is disabled. Display will blank as normal.

'''Test'''

A test resource.

'''UsbHost'''

While this resource is requested the USB is turned into powered USB Host mode.

'''Accelerometer'''

You need to have this resource requested to have the Accelerometer module powered.

==Networking==

There are several ways of networking - Wifi, USB, Bluetooth and Gprs:

===USB===

By default, USB networking is enabled in <tt>/etc/network/interfaces</tt>, where enhanced configuration can be direct edited. The phone default IP address is 192.168.0.202. Some setup is required on the desktop side, please read [[USB Networking]].

===WiFi===

WiFi manager [[iliwi]] is available by default for search/connect/making default a wifi connection. ''iliwi'' uses key only in hex format. The Wifi device is not required to be manually turned on via SHR-Settings as ''iliwi'' will automatically enable the device when needed and disable it after use. iliwi needs to stay running to keep the WiFi connection enabled.

When WiFi is connected, the Idle screen show the icon of the WiFi resource being occupied.

===GPRS===

GPRS Credentials are set during the first run in SHR Wizard and you may edit them at any time via SHR settings or direct editing of /etc/phonefsod.conf. GPRS connection can then be established/closed via SHR Settings or through SHR Quick Settings (available under the Power button). SHR Quick Settings - Network tab allows also connection sharing - this will share the GPRS connection with USB network and run DHCP server to provide the client with an IP address.

When GPRS is connected, the idle screen shows a small G above the signal strength indicator.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |
[[Image:SHR-Gprs-Share.png|200px|thumb|GPRS + Connection sharing]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |
[[Image:SHR-Iliwi-Scan.png|200px|thumb|Iliwi WiFi scanning]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |

[[Image:SHR-Iliwi-Connect.png|200px|thumb|Iliwi WiFi connecting]]

|}

==Bluetooth==

Bluetooth can be used for several different applications - file transfer (OBEX), networking, input devices (HIDD), music playing (A2DP), calling etc. In some occasions, the devices need to be authorized - paired. At the moment, support for some bluetooth functions is better than for others - it is possible to do all mentioned above with the notice that phone calls with bluetooth headset are always routed to the bluetooth even if the bluetooth headset is not around, making it quite difficult to use.

In the SHR repositories are applications ready to be installed (by opkg) that already do provide bluetooth support. This means that they request the bluetooth resource automatically, can search bluetooth devices around, help you with pairing and can perhaps even reconnect bluetooth headset upon resume from suspend. From applications that have some bluetooth support some are for example [[Launcher]] (home screen launcher and phone suite), [[Podboy]] (podcast player), [[Elmtooth]] (bluetooth manager). In order to set up bluetooth for phone calls, some manual setup from [[#GSM_phone_calls_with_bluetooth_headset | bellow]] is still required.

===Bluez3 - the manual non D-Bus way===

If you want to use the bluetooth device directly, you need to turn the bluetooth radio on in SHR Settings -> Connectivity -> Bluetooth Radio: On. You can also make the bluetooth device visible here.

====OBEX file transfer====

There are several obex programs allowing file transfer, all in console at the moment. Obexpush installs obextool, and opd daemon:

opkg install obexpush

Default receiving path (editable in /etc/default/opd_args ) does not exist, so create it

mkdir /var/obexpush

Files are then received automatically, no notice, no confirmation... they just silently appear in /var/obexpush

To send some files, first scan for devices:

hcitool scan
Scanning ...
00:16:41:F5:A5:BC laptop

Then send the file onto bluetooth address found in the scan:

obextool push image.jpg 00:16:41:F5:A5:BC 10

====Connect Bluetooth keyboard====

hidd --search

Editors note: This is the old bluez3 way, but it works. New bluez4 way will replace this.

===Bluez4 - D-Bus based way===

SHR uses bluez4 which is completely different from bluez3. The bluetoothd is taking care of most of the bluetooth now. Please see [[Manually using Bluetooth]] for detailed information about using bluetooth and also for a list of supported devices.

====Pairing====

[[Emtooth]] is a bluetooth manager. It provides setting up bluetooth device name, pairing/unpairing, visibility setting and more. Install Emtooth:

opkg install emtooth

It will discover nearby devices, double tapping on found device will initiate pairing process.

====GSM with bluetooth headset====

In order to use bluetooth headset for phone calls, several simple steps need to be done.

1). Your bluetooth headset device must be [[#Pairing | paired]] first.

2). [[#Configuring_FSO | Add]] your bluetooth headset into FSO configuration.

Please note: phonecalls are now always routed to the bluetooth headset.
After startup and after every resume, the headset needs to be [[#Re-Connecting_the_bluetooth_headset |reconnected]].

=====Configuring FSO=====

Now we must tell frameworkd that you have a bluetooth headset. Headset parameters should be set in

/etc/freesmartphone/opreferences/conf/phone/default.yaml

Parameters bt-headset-enabled and bt-headset-address (see opreferences/schema/phone.yaml for semantics).

You need to restart FSO for the changes to take effect.

# /etc/init.d/frameworkd restart

example of my /etc/freesmartphone/opreferences/conf/phone/default.yaml:

message-length: 7
message-tone: notify_message.wav
message-vibration: 1
message-volume: 10
ring-loop: 1
ring-tone: ringtone_ringnroll.wav
ring-vibration: 1
ring-volume: 10
bt-headset-enabled: 1
bt-headset-address: 00:09:DD:31:92:98

=====Re-Connecting the headset=====

You might need to get the bluetooth headset connected manually on the beginning and also after suspend:

mdbus -s org.bluez $BTADAPTER/dev_xx_xx_xx_xx_xx_xx org.bluez.Headset.Connect

where xx_xx_xx_xx_xx_xx is address of the device, for example:

mdbus -s org.bluez $BTADAPTER/dev_00_09_DD_31_92_98 org.bluez.Headset.Connect

Hopefully, your bluetooth headset now works. Good luck!

==System Customizing==

===Command scheduling===

The traditional ''at'' command in ''SHR'' is modified to work over dbus. This modified ''at_over_dbus'' will run scheduled task at required time - actually it will even automatically wake up the phone from suspend or start it if the phone was switched off.

To schedule a command to be executed at a particular time, one must:

Place commands in a script in ''/var/spool/at'' and name it like

TIMESTAMP.NAME.NUMBER

where

where TIMESTAMP is the seconds since 1970-01-01 00:00:00 UTC when the command should be run.
The rest (NAME, NUMBER) is up to you. Finally you have to:

touch /var/spool/at/trigger

Also, make sure to have atd running. You are responsible to remove the script when unnecessary. It will run once more if you/other program write to the trigger file during the execution, so you may consider removing the
executable flag of the script (if it is long running) or rename the script from within for example like this:

mv "$0" "x$0.$$"

===Installing splash screen themes===

List available splash screen themes

opkg list | grep splash-theme

Install one of the available themes

opkg install shr-splash-theme-dontpanic

Then go to '''SHR Settings -> Appearance -> Splash settings'''. Here you can preview installed themes and change the default one.

===Installing themes===

Every theme is made of several components (a theme for illume, theme for the phone applications, theme for etk and so on). There is a SHR metapackage for each theme that allows installing the complete theme in one go.

List available SHR theme metapackages:

opkg list | grep shr-theme

Install one of the available themes

opkg install shr-theme-gry

Then go to '''SHR Settings -> Appearance -> Elementary Settings'''. Here you can preview installed themes and choose the preferred one.

The Illume screen requires to change theme via '''Settings (SHR Logo) -> Look -> Theme'''. Here you can preview installed themes and choose the preferred one.

===Enable mouse cursor===

edit line 143 of /etc/X11/Xserver and erase '''-nocursor'''

ARGS="$ARGS"

===Random errors===
No icons, no GSM functions etc. happen mostly due to '''errors on your µSD''' card. Remove your card and fix it in card reader or by booting to another partition (nand) or by reboot and mount read only, then run fsck.

For reboot into nand and fix 1st partition of ext2 on your card

fsck.ext2 /dev/mmcblk0p1

===GSM modem 1024 suspend bug===

The calypso GSM modem suffers a known [[1024]] hardware bug that causes unreliable GSM function. To work it around, SHR by default doesn't suspend the modem completely. If you have undertaken a fix for this bug you can extend your battery time by enabling the modem to fully suspend when possible.

Edit the following in file:

For the new FSO2 edit /etc/freesmartphone/conf/GTA02/fsogsmd.conf

deep_sleep == "always"

Then kill fsogsmd and restart fsodeviced or reboot the phone.

For old FSO (frameworks) edit /etc/frameworkd.conf

ti_calypso_deep_sleep = always

Then restart framework or reboot the phone.

==Reporting bugs==

SHR is a work in progress. If you experience issues, please report them back to SHR. With your report provide relevant logs from

/var/log/

To report a bug, please go to http://shr-project.org/trac/report

Check if the bug is already reported. If not, add a ticket, be as much precise as you can in the title and the description, in what circumstances the issue happened and so on. If bug already exists, see if you can help fixing it by providing some fresh info.

==More information==

For SHR home page, source code and other resources, visit:

* [http://trac.shr-project.org SHR Project Homepage]
* [http://blog.shr-project.org SHR Blog]
* [http://trac.shr-project.org Trac Bugtracker]
* [http://git.shr-project.org Git Sourcecode-repository]
* [http://build.shr-project.org Downloads on buildhost]
* [http://lists.shr-project.org SHR User and Development Mailing Lists]

==About this manual==

This manual makes use of updated SHR-Unstable distribution which means that for example SHR-Testing or not updated SHR-Unstable might behave differently then stated in this manual.

Please help extending this manual by correcting typos or discussing proposals on the talk page or email <tt>vanous @ penguin . cz</tt>. Thank you.

[[Category:SHR]]
[[Category:Manuals]]

SwapSpace

2010-08-15T15:47:28Z

Janvlug: /* Links */

WARNING: THIS MIGHT KILL YOUR SD CARD, since there might be alot of read/writes on the same spot.
The Freerunner has only 128mb ram, when this is used up applications get killed.

Please note that the above warning do not apply to [[microSD]] (including microSDHC) card with wear-levelling algorithms/microcontrollers. (See [[#References]])

Please note that you can change the ''swappiness setting'' (low value, default 60) so the swap partition or swap file will be used as little as possible. (See [[#References]])

=Make swap when you are connected to your openmoko with ssh=

{{Note|swap files cannot be created on compressed file systems like jffs2. SHR uses jffs2: I created a swap file on /media/card/swapfile}}

64M byte of swap just as an example
dd if=/dev/zero of=/swapfile bs=1024 count=65536
Next time you boot there will be swap
echo "/swapfile swap swap defaults 0 0">> /etc/fstab
Make swap
mkswap /swapfile
Make the swap file work now:
swapon /swapfile

=Make swap when microSD card is in a card reader=
The uSD card is booted on /boot. To use this, we need to make sure that the microsd card is booted, and the Swap can be turned on.

Create the swapfile on the uSD card.
# dd if=/dev/zero of=/boot/swapfile bs=1024k count=128
# mkswap /boot/swapfile

Now, we can put in an init script for [[Fyp]] which does this for us everytime we boot.

# touch /etc/init.d/extswap.sh
# chmod +x /etc/init.d/extswap.sh
# cat > /etc/init.d/extswap.sh
#! /bin/sh
### BEGIN INIT INFO
# Provides: extswap
# Required-Start: mountall
# Required-Stop:
# Default-Start: S
# Default-Stop:
# Short-Description: Uses Additional Swap If Available. works on SHR distro
# Description:
### END INIT INFO

PATH=/sbin:/bin

do_start() {
modprobe loop
echo 10 > /proc/sys/vm/swappiness
if [ -e /boot/swapfile ] ; then
for loopdev in `ls /dev/loop* 2>/dev/null` ; do
losetup $loopdev /boot/swapfile && swapon $loopdev && echo $loopdev > /var/extswapfile && break
done
fi
}

do_stop() {
loopdev=`cat /var/extswapfile 2>/dev/null`
swapoff $loopdev 2>/dev/null && rm -f /var/extswapfile && losetup -d $loopdev
}

case "$1" in
start|"")
do_start
;;
restart|reload|force-reload)
do_stop
do_start
;;
stop)
do_stop
;;
*)
echo "Usage: extswap.sh [start|stop|restart]" >&2
exit 3
;;
esac
# update-rc.d extswap.sh defaults

==References==
*[http://www.notebookreview.com/default.asp?newsID=4258 2/17/2008, notebookreview.com: SDHC Cards vs Hard Drive vs SSD] Quote: "...That sounds like an absolutely manditory thing to have in flash storage ... and luckily "high-performance" SDHC cards such as the 16GB A-DATA SDHC card and many other class 6 cards from other manufacturers incorportate wear-leveling [Please check before you buy!]..."
*[[MicroSD]](HC) cards are a sort of a SSD: [http://robert.penz.name/137/no-swap-partition-journaling-filesystem-on-a-ssd/ December 7, 2008, robert.penz.name: No SWAP Partition, Journaling Filesystems, … on a SSD?] Quote: "...They assume perfect wear leveling...We stay also with the 2 million cycles and assume a 16GB SSD *With 50 MByte/sec we get 20 years! *With 2 MByte/sec we get 519 years! *And even if we reduce the write cycles to 100.000 and write with 2 MByte/sec all the time we’re at 26 years!!...1. Never choose to use a journaling file system on the SSD partitions: Bullshit, you’re just risking data security. Stay with ext3...7. One more thing to consider is that flash-devices handle their space in blocks. The blocksize typically varies between 16KB and 512 KB. Therefore writing one byte may cause erase and rewrite of up to 512KB..."
*[http://fosswire.com/post/2009/2/sysctl-swappiness/ fosswire.com: Speed up your system by avoiding the swap file] Quote: "...the Linux kernel provides a tweakable setting that controls how often the swap file is used, called swappiness. A swappiness setting of zero means that the disk will be avoided unless absolutely necessary (you run out of memory), while a swappiness setting of 100 means that programs will be swapped to disk almost instantly..."

==Links==
*http://www.google.dk/search?q=linux+swap+partition+vs+file+speed
*http://shr-project.org/trac/wiki/swap

[[Category:MicroSD]]
[[Category:Application Developer]]

Recover files from flash

2010-08-15T14:23:44Z

Janvlug: How to recover files from flash when not booting

This is what I did to access the file system on the flash memory after that my [[Neo FreeRunner]] did not boot anymore.
(Note that I'm using Qi and SHR-U on flash memory on jiffs).

= Make a bootable SD card =
Take an SD card of at least 1 GB from which all information may be deleted.
I installed Hackable:1 on the SD card by following these instructions:
http://www.hackable1.org/wiki/Installation

= Boot from your SD card =
Press and hold AUX button while pressing the power button.
Select the second option to boot from the SD card.

= Mount the file system that resides on your flash memory =
mount -t jffs2 /dev/mtdblock6 /mnt/flash/

= Do your thing to make your phone booting again =
For example:
* Check the file system
* Do an opkg upgrade of a broken operating system
chroot /mnt/flash opkg update
chroot /mnt/flash opkg upgrade
* Backup some directories
scp -r root@192.168.0.202:/mnt/flash/etc/freesmartphone/opim backupdir

Trouble shooting

2010-08-15T14:20:38Z

Janvlug: Howto access the file system in flash when the phone does not boot?

== Howto access the file system in flash when the phone does not boot any more? ==
[[Recover files from flash]]

More Information

2010-08-15T14:17:15Z

Janvlug: Added trouble shooting to user area

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

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

The Openmoko stack, which includes a full X server, allows users and developers to transform mobile hardware platforms into unique products. Our license gives developers and users 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 [http://downloads.openmoko.org/CAD/ CAD] files. And at LinuxWorld 2008, we announced the release of the [http://downloads.openmoko.org/schematics/ schematics for our products].

<div style="clear:both"> </div>

<table class="wikitable" cellspacing="4" cellpadding="6" width="100%" style="color:white">
<tr style="background:#ff6600; text-align:center; font-weight:bold">
<td width="50%">News and events</td>
<td width="50%">New to Openmoko?</td>
</tr>
<tr valign="top" style="background:#333333">
<td>

{{News}}

* [[News Archive|(news archive)]]
</td>
<td>

===About Openmoko===
* [[Introduction]]
* [[Why Openmoko]]
* [[Neo FreeRunner|Neo FreeRunner phone]]
* [[Supported Hardware]]
* [[FAQ]]

===Getting Openmoko===
* [[Getting Openmoko]]
* [http://www.openmoko.com Openmoko Inc.]
</td>
</tr>
<tr style="background:#ff6600; text-align:center; font-weight:bold">
<td width="50%">for Users</td>
<td width="50%">for Developers</td>
</tr>
<tr valign="top" style="background:#333333">
<td>
===Getting started===
* [[Getting Started with your Neo FreeRunner | Neo FreeRunner getting started guide]]
* [[Applications|Applications list (wiki)]] and [http://opkg.org directory (opkg.org)]

===Distributions===
* [[Distributions|Features comparison table]]
* [[Om 2008.8|Om 2008.8 (ASU)]] - [[Om 2007.2|Om 2007.2 (old stable)]]
* [[OpenmokoFramework|FSO]] - [[FDOM - a Fat and Dirty OM based distribution|FDOM]] - [[Qtopia / Qt Extended on FreeRunner|Qt Extended]] - [[Debian]] - [[Gentoo]] - [[Android]] - [[Stable Hybrid Release]] - [[Hackable:1]]

===Openmoko community===
* [[Discussion_Forums| Discussion Forums]]
* [[Jokes]]
* [[Community Repository]]
* [[Development resources | Development resources]]
* [[Openmoko E-courseware | E-courseware]]
* [[University Program#Student Projects | Student Projects]]

===Help===
* [[Trouble shooting]]
</td>
<td>
===Applications development===
* [[Openmoko developer guide]]
* [[Toolchain|The toolchain]]

* [[Python|Introduction to Python]]
* [http://projects.openmoko.org/ Projects hosted in our GForge]
* [[OpenmokoFramework|Openmoko dbus-based service level framework]]

===Integration and distributions===
* [[OpenEmbedded|The OpenEmbedded distribution building framework]]
* [[MokoMakefile|Building Openmoko using the MokoMakefile ]]
* [[Opkg|The Opkg package manager]]

===Emulation===
* [[Openmoko under QEMU]]
</td>
</tr>
</table>

Browse articles by [[:Category:Categories|Categories]].

[[Category:Community]]

Manuals/SHR

2010-05-18T21:32:34Z

Janvlug: /* Copy and Paste */

{{Languages|Manuals/SHR}}
{| align="right"
| __TOC__
|}

==SHR Introduction==

Welcome to '''[[SHR]]''', a community driven distribution for (not only) Openmoko Neo phones.

[[Image:SHR-Logo.png|200px|thumb|center|SHR]]

'''SHR''' (Stable Hybrid Release) is here to provide you with Root FileSystem images that you can easily install into your device to use as a daily phone and PDA. There are many prepackaged programs available that can be installed upon demand by users, it can also be used by developers as a base image for customized and flavored distribution or release. '''SHR unstable''' is a testing environment before software gets stabilized and it is the main testing ground for [[FSO]] releases. '''SHR testing''' images provide as much stability as possible for day-to-day usage.

SHR users, readers of this manual, please report improvements, discrepancies or missing features on this page to <tt>vanous @ penguin . cz</tt>. Thank you.

==Installation==

===Getting SHR===

You need to download two files for your version as above: kernel and root filesystem. Depending whether you will be installing into the internal [[NAND memory]] or on the [[microSD]] card, you need to either get .jffs2 file for NAND or .tar.gz file for microSD.

- Get the latest kernel from the below linkpages. Starts with uImage-...

- Get the root filesystem, for NAND: full-om-gta0_.jffs2, for µSD: full-om-gta0_.tar.gz

The above are '''full''' images. You can also choose images with less packages, marked as '''lite'''.

;GTA02 Neo FreeRunner
*testing line: http://build.shr-project.org/shr-testing/images/om-gta02/
*unstable line: http://build.shr-project.org/shr-unstable/images/om-gta02/

;GTA01 Neo 1973
*testing line: http://build.shr-project.org/shr-testing/images/om-gta01/
*unstable line: http://build.shr-project.org/shr-unstable/images/om-gta01/

;Image lite to image full
If you flashed a '''lite''' image and want to upgrade to the '''full''' image run:

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

;Kernel modules
The images of the filesystems mentioned above (.jffs2, .tar.gz), already contain the newest kernel modules.

Get the new kernel modules if you only want to flash a new kernel, but not a whole new file system. From the same page as the kernel download the modules to match your kernel (their dates should be the same). Use sftp to put that file on the FreeRunner via the usb connection. Run gzip to unwrap the modules:
# gzip -dc modules-...tar.gz | tar -xf - -C /

===Installation on Flash===

In order to install your SHR distribution directly to your Freerunner Flash memory (NAND), you need to get the desired filesystem file ( <tt>.jffs2</tt> ) as described above and flash your device using the <tt>dfu-util</tt> tool.

Please visit [[Flashing the Neo FreeRunner]] for more details about flashing and see [[Dfu-util]] for detailed information about the dfu-util.

{{Note|Your battery must be charged (sufficiently) before NAND flashing. Symptom of insufficient charge: Your progress bar "####" stops while flashing. If so, you must charge, and later you should be able to make the complete flash.}}
Commands to flash the filesystem and the kernel:

Note that there are some issues using dfu-util with sudo.

'''Don't use sudo with dfu-util. Make sure you are root before using dfu-util!'''

for the GTA02 Neo FreeRunner:

# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D full-om-gta02.jffs2
# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-om-gta02-latest.bin

for the GTA01 Neo 1973:

# dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a rootfs -R -D full-om-gta01.jffs2
# dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a kernel -R -D uImage-om-gta01-latest.bin

===Installation on the microSD Card===

Installing SHR on your microSD Card depends on the Bootloader you are using, ''uBoot'' or ''Qi''.

In simple words, the difference between both systems resides on how you must prepare your microSD Card and files you use to fill them:

* If you use ''uBoot'', you need to create two partitions. First partition, not so big, in FAT16 or ext2 where you have to place the kernel file (<tt>uImage-om-gta02-latest.bin</tt>) and second partition in ext2 or ext3 where you have to uncompress the filesystem file (<tt>shr-image-om-gta02.tar.gz</tt>).

* If you use ''Qi'', you only need an ext2 partition into your µSD Card where you uncompress the filesystem image file (<tt>shr-image-om-gta02.tar.gz</tt>). In this case Qi Bootloader is going to look for the kernel image into the <tt>/boot</tt> directory for file named <tt>uImage-GTA02.bin</tt> .

Please visit the links below for detailed information and tips:
*For [[Booting from SD | uBoot]] and for [[Qi]].

===SHR version===

Should you ever later wonder what version of SHR you have actually installed, please run

timestamp of image creation:
cat /etc/timestamp

latest shr version from opkg upgrade (this version is changed everytime someone builds task-base on shr buildhost):
cat /etc/shr-version

{{Note|Please note that this is true only for shr-u, with shr-t running opkg update;opkg upgrade does not change the SHR version. Only flashing or a new image download can change the SHR version. But this will be also merged to shr-t later.}}

==Running SHR==

===First boot===
[[Image:Shr-boot-preview.png|200px|thumb|center|SHR Boot Splash screen]]

====Booting====
First boot usually takes a bit longer as your phone's new software needs to do some initial setting up. It is recommended to reboot after this first boot (and after the initial setup), to make sure that all packages get initialized properly.

====Initial Setup====

During the first run, Setup is automatically initiated to walk the user through basic setup of the Enlightenment desktop environment. These steps vary as both Enlightenment desktop and SHR evolve, at this point preferred language and desktop profile options are available. The Profile offers to choose a preconfigured way of displaying the desktop. Illume2-SHR (with continuous development) and Illume-SHR (discontinued) profiles are available. '''Illume2-SHR''' is the recommended Profile.

{| class="wikitable"
| [[Image:SHR-Setup-Language.png|200px|thumb|language selection]]
| [[Image:SHR-Setup-Profile.png|200px|thumb|theme selection]]
| [[Image:SHR-Wizard.png|200px|thumb|SHR Wizard]]

|}

====SHR Wizard====
After the initial Setup, SHR Setting Wizard is launched to allow setting up your local phone settings and setting up root password. Sometimes a '''Please wait''' message is displayed for a long time, as the wizzard is waiting for the SIM card to be initialized.

===First look===
[[Image:SHR-First-Look.png|200px|thumb|Desktop screen]]
[[Image:SHR-Task-Buttons.png|200px|thumb|Task switch buttons]]
====Illume desktop====
Illume desktop is the default home screen of the SHR desktop.

Application definition files located in /usr/share/applications are displayed here as icons. All applications are ran fullscreen and you can switch between them by using the the '''< left''' or '''right >''' arrows on sliding shelve available by tapping Top Shelf on any empty space. To close applications, choose '''X''' from the same sliding shelve.

Several icons (e-gadgets) are placed in the Top Shelve:

The '''L''' icon is to switch between left/right mouse click. By taping this icon the icon gets changed to R and next tap will be as right click. After the click, the behavior is automatically switched back to Left click so any following taps are left click again.

'''Mode Switch Icon''' allows to split the screen horizontally or vertically, thus allowing to display two applications at the same time.

'''Keyboard icon''' pops up or hides the Keyboard.

'''Illume Settings''' icon (represented by SHR logo) invokes the [[#Illume_settings | Illume desktop settings]].

'''Home Icon''' allows quick go to the home desktop/application.

'''GSM''' and '''Battery''' status icons, as well as '''time''' are displayed by default, Bluetooth and WiFi status icons available in the setting of the Top Shelve content.

To '''reconfigure the Top Shelve''' itself, use the L/R click icon to Right click on the Top Panel and choose: Illume Indicator->Set Content to add or remove items from the Top Panel. Or, upon right click on the Top Panel you can also choose Illume Indicator->Begin Move/Resize to move your icons around. To escape this mode, you must click on the L/R gadget's edge, it will switch to L, then choose R again, right click on the Top Panel and select Illume Indicator->Stop Move/Resize.

====Keyboard====

Keyboard comes up automagically when a text field is tapped or you can also toggle the keyboard by it's icon in the Top Shelve. In the Keyboard, dictionary switcher is the arrow-up on left side, alternative keyboard layouts are under the ABC button on the right. The Default keyboard has English dictionary enabled. For Space quick slide left-to-right, for Enter, quick slide up-down, to quick change keyboard layout quick slide down-up. While typing with a dictionary enabled keyboard, possible word options start appearing in the keyboard's upper part or more word options are available under the arrow-up on the left. When happy with the word, tap it, it will be pasted into the text field with a space attached. The Keyboard and dictionary can [[#Illume_keyboard_and_dictionaries | easily be localized]].

====Copy and Paste====

In '''E based''' applications (for example the phone suite (contacts, messages...)) by tapping and holding down for over two seconds the Select-Paste menu will pop up. By pressing Select, you can now swipe through the text to select desirable part. Tap and hold down again, Copy-Cut-Cancel menu will appear to Copy to clipboard. Another long tap will provide Select-Paste for Paste.

In '''Gtk''' based application you can use keyboard for Ctrl-C (Copy) and Ctrl-V (Paste) or items in Menu if provided.

In the Vala '''Terminal''' you can select simply by swiping through the text and for Paste there is a icon in the menu bar of this application.

Copy & Paste between different toolkits has some limitations. See the table below. In Ventura, select is possible, but copy/paste doesn't seem to work at all.

{| cellspacing="0" class="wikitable" border="1" style="font-size: 85%; text-align: left;width="100%"
|-
! From -> To
! to GTK
! to E
! to Terminal
|-
| from GTK
|style="background:#88FF88;"|Works
|style="background:#88FF88;"|Works
|style="background:red"|Doesn't work
|-
| from E
|style="background:red"|Doesn't work
|style="background:#88FF88;"|Works
|style="background:#88FF88;"|Works
|-
| from Terminal
|style="background:red"|Doesn't work
|style="background:#88FF88;"|Works
|style="background:#88FF88;"|Works
|-
|}

====Alarm====

The Alarms application (installed by default) allows alarm presetting for single or repeatable alarms. If you set an alarm and turn your Openmoko Freerunner off, at the time of the alarm the phone will be powered up and alarm will sound.

====Phone applications====

Besides other software, SHR comes with 4 main phone applications: ''Dialer'', ''Contacts'', ''Messages'' and ''Phone log''.

{|
| [[Image:SHR-Dialer.png|200px|thumb|Dialer]]
| [[Image:SHR-Contacts.png|200px|thumb|Contacts]]
| [[Image:SHR-Mesages.png|200px|thumb|Messages]]
| [[Image:SHR-Phonelog.png|200px|thumb|Phone log]]
|}

=====PIM data=====

======Storage======
PIM data (contacts, messages etc.) are stored through internal opimd storage mechanism into

/etc/freesmartphone/opim/pim.db

This database can easily be copied from one SHR installation to another, for example due to a need for reflashing. The Contacts application can display a picture of the contact. As the pim.db database contains a path to the picture files only but not the pictures themselves, therefore, in case of PIM data backup or transfer, these picture files '''need to be copied too'''.

======SIM Contacts======

SHR phone applications do not read SIM contacts by default but you can use SIM Manager to access your SIM contacts '''SHR Settings -> Others -> SIM Manager''', which allows you to edit and import the SIM contacts into the internal storage. You can also use Pisi to import your SIM contacts into opimd.

======Synchronization======

'''[[Pisi]]''' is an application for synchronizing PIM data and can be used for import and export your contacts, calendar entries etc. between various sources, like VCF, LDAP, Google and more. To install Pisi:

opkg install pisi

After installation, edit Pisi configuration in '''.pisi/conf''' in your home directory. To have a correct opimd fields support, make sure '''field_support=TRUE''' is enabled in opimd section.

[opimd]
description=OPIMD Contacts
module=contacts_opimd
field_support=TRUE

=====Idle screen=====
[[Image:SHR-Idle_Screen.png|200px|thumb|Idle Screen with GSM operator strength and name. GPS, WiFi, Display and CPU are requested, Battery status.]]
Upon press of the AUX button Idle Screens locks up the display. AUX press or a finger slide on the Slider unlocks the screen.

At the top, status icons are shown to indicate what is going on in the phone:

From left to right:
GSM strength and operator. Requested Resources (GPS, Display etc., when for example Display is requested, the screen will not dim). Battery capacity.

====Setting applications====

[[#SHR_Settings | SHR Settings]] is accessible by tapping Settings icon on the desktop. [[#Illume_settings | Illume settings (and Enlightenment desktop settings)]] are accessible by sliding down the Top shelve and then tapping the "SHR Logo" icon.

====Hardware Buttons====

=====Power Button=====

[[Image:SHR-Quick-Settings.png|200px|thumb|Quick Settings]]

The '''PWR''' (Power) button is mapped to start [[#quick_settings | Quick Settings]] screen (Illume System menu in older versions) on a short press.

Mapping of the PWR button be configured via the '''Illume Settings-> Input -> Key Bindings'''.

Pressing the Power button for longer then 8 seconds will force a complete power down of the device. This is hardconfigured in the kernel.
<div id="quick_settings"> </div>
The '''Quick Settings''' screen provides several toggles: Airplane mode, Phone profiles, Power settings and Power buttons.

=====Auxiliary Button=====
The '''AUX''' (Auxiliary) button is mapped to toggle on/off the SHR Idle screen. Mapping of this button is configured in /etc/phonefsod.conf

idle_screen = aux,lock

You can configure the [[#idle_screen | Idle Screen]] to come up even during active phone call by adding '''phone''' to the setting:

idle_screen = aux,lock, phone

<div id="idle_screen"> </div>
The '''Idle Screen''' shows current date and time, missed calls and messaged and also what [[#FSO_Resources | FSO resources]] are currently being requested - used.

======Replacing idle screen======

If you wish to use the E simple LOCKED screen instead of the SHR Idle Screen, edit '''/etc/phonefsod.conf''' to this:

# when to show idle screen
# ...
# idle_screen = aux,lock
idle_screen =

You need to restart phonefsod to make the change happen.

Also, change key mapping for the AUX button by setting '''Illume Settings''' -> '''Input''' -> '''Key Bindings''', bind the key '''XF86Phone''' to '''Desktop Simple Lock'''

===First steps===

Right after installation and first boot you might want to do a few initial steps like adjusting the call volume and some other tasks.

====Audio - Call Volume====

During the first phone call please use the Volume and Mic sliders on the Active Call Screen and adjust them to fit your preferences. The new improved settings will be used for all in- and outgoing calls thereafter.

====Network Connection====
''Establish network connection'' and SSH into your phone. You can establish connection either via USB to your desktop and enable NAT or you can connect through Wifi. If you use USB, some setup is required on the desktop side, please read [[USB Networking]]. For Wifi, you can use [[#Network manager|Network Manager]]

====Initializing the opkg database====
''Initialize the opkg database'' in order to install some applications from SHR repositories or from other sources, for example [http://opkg.org opkg.org]. While being online, you need to run

opkg update

Searching in the opkg database can take a long time. You can speed things up by dumping the database into a file and grepping it through. Do this only once or after every opkg update:

opkg list > packages.txt

Then you can search quickly for package name, for example for navit:

grep navit packages.txt

====SwapSpace====

When the RAM is used up, applications get killed. This is particularly bad while doing opkg upgrade. Therefore you might want to create a swap space. Read [[SwapSpace]] article.

==Settings==
===SHR Settings===
[[Image:SHR-Settings-main.png|200px|thumb|SHR Settings]]

SHR Settings is the main setting application of SHR. It provides an easy way of setting up your phone to your liking - from phone related settings, to requesting resources in order to prevent screen dim or suspend (for example while using GPS).

Please refer to [[#FSO_Resources | this section]] about a better way to manage preventing screen dim or suspend.

While some settings are persistent over reboots, others are not.

====Main Screen====
The main screen is divided into eight categories, which contain several modules. Every SHR Settings module has a specified task - for example controlling the GSM antenna power, setting the time etc.

====Phone====
Here you can set if the GSM antenna is on and if your phone number is shown when you call someone.

'''GSM'''
In GSM settings you can turn off and on GSM module. After turning off antenna, whole GSM modem is turned off.

To list available providers, click on Operators button. Scanning can take some time. After a while, a list of operators should pop up.

You can't connect to operators marked [forbidden].

Selecting an operator from the list also changes modem registration mode to manual. It won't register to other network, even if some is available and has better signal strengh. To return to automatic mode, click "Automatic" button in operator list.

'''Call'''
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Phone.png|200px|thumb|Phone settings]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-List-providers.png|200px|thumb|List providers]]

|}

You can set if your phone number should be displayed to other party. You can either depend on network decision ("By network") or force it manually ("Manual")

'''Phoneutils'''

For the default SHR phone applications to be able to correctly parse incoming calls/messages and match them with your contacts, you will need to set the right country code for your location. (for example 420 for Czech republic) for more info, please go to: http://wiki.openmoko.org/wiki/Phone_Prefixes

'''SIM'''

Here you can view some informations about your SIM card and clean phone and messagebooks.

====Profiles====

Here you can select the current profile, which the device should use to determine ring tone etc.

'''Current profile'''

Here you can adjust properties of the currently used profile.

To change the ring tone, click the "Change" button.

To use your own ring tone, place it in /usr/share/sounds directory.

After selecting a sid tune as the ring tone, there are available controls to select tune number from the file.

If you like to test a .sid you can play it using this command on the FR:

gst-launch filesrc location=Arkanoid_PSID.sid ! siddec tune=2 ! alsasink

Note that it's a ! used and not a | to construct the gstreamer pipe command.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Profiles.png|200px|thumb|Profiles]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Profiles-Ringtones.png|200px|thumb|Ringtones]]

|}

====Connectivity====

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Connectivity.png |200px|thumb|Connectivity top]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Connectivity2.png |200px|thumb|Connectivity bottom]]
|}

'''WiFi'''

With the "WiFi radio" toggle you can set, if the wifi module is powered. WiFi radio has to be turned on before trying to connect to a WiFi network, unless you try to connect through [[Mokonnect]] which is capable of powering it up.

'''GPRS'''

To enter APN, login and password fields, just click on the actual value (default: "internet"). Your phone provider can provide the required configuration options.

{{Note|You can also use Mokonnect to manage your GPRS connection}}

'''USB'''

With this toggle you can switch USB port between device (Neo to PC) or host (device to Neo) modes.

'''Bluetooth'''

To power up Bluetooth module, switch the "Bluetooth radio" toggle to "On". After that, the "Visibility" toggle should arrive - set it to "On" if you want your FR to be visible by other Bluetooth devices on scanning.

====Power====

'''Battery'''

This module displays informations about battery state - charge, voltage, remaining time etc. To update the data, click the "Update" button.

Here you can also force enable 500mA charging.

'''Display'''

With this slider you can easily set the backlight brightness.

{{Note|This setting isn't permanent over sessions. At boot backlight is set back to 80%.}}

'''Power'''

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Power.png |200px|thumb|Power]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Timeouts.png |200px|thumb|Timeouts]]
|}

'''Timeouts'''

Timeouts are reached in this order: Busy state -> idle -> idle dim -> idle prelock -> lock -> suspend.

{{Note|Storing of this setting via D-bus calls is not supported in the new API of Vala rewrite of FSO2 and therefore SHR Settings doesn't have a functional setting for this.}}

You can set values of idle timeouts manually. The default parameters are stored in '''/etc/freesmartphone/conf/GTA02/fsodeviced.conf''' but customized '''.fsodeviced.conf''' file in your home directory will take precedence:

[fsodevice.kernel_idle]
suspend = 20
lock = 2
idle_prelock = 12
idle = 10
idle_dim = 20

====Appearance====

'''Theming'''
[[Image:SHR-Neo-Theme.png|200px|thumb|Neo theme]]

The Apperance section allows you to change between installed themes. To install more themes, see also [[#Installing themes | Installing themes]].

You can change finger size - this will mainly effect vertical spacing between widgets.

Switching between engines:

E can be switched to use different engines. The default engine is x11. Alternative engine x11-16 is not supported and results in buggy behavior of several applications, for example the phone suite or Ventura browser. It's usage is not recommended.

Changing system boot Splash screen is also possible in this module. To install more splash screens, see also [[#Installing splash screen themes|Installing splash themes]].

====Position====

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-GPS.png |200px|thumb|center|GPS]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-GPS-Satelites.png |200px|thumb|GPS Satelite details]]
|}

'''GPS'''

By default, GPS is turned on only when requested by an application. That state corresponds to "Auto" setting. After changing to "Manual", you can force set it to on or off.

'''GPS information'''

This page can be used to monitor GPS status. You either have to turn GPS on manually or start another application to enable the GPS.

You can also view information about every visible satellite and check, which are used for getting a fix. To do that, click "Satellite details".

'''Remove AGPS data'''
If you experience problems with GPS, turn it off, click "Remove AGPS data" and reboot your Neo.
Assisted GPS ([[aGPS]]) support GPS receiver to find position by non-satellite information.

====Date/time====

[[Image:SHR-Settings-Date-Time.png |200px|thumb|Date & Time]]

'''Time'''

Here you can view and set the time. By default, the time is just displayed, To adjust it, click on "Set time".

After finishing adjusting, click the "OK" button.

'''Date'''

This module displays the current date.

====Others====

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

[[Image:SHR-Settings-Others.png |200px|thumb|Others]]

'''PIM'''

Pim data are stored in opimd domains. Every opimd domain has different backends to store its data to. The domain reads data from every backend and writes data to the default backend. This elector allows you to choose the backend that stores newly generated data, it doesn't copy or move existing data to a different backend.

'''Services'''

The services selector is listing scripts from /etc/init.d/ directory.

After clicking on a servis, you can either start, restart or stop the service and view the result.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Services.png |200px|thumb|center|Services]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Service-restart.png |200px|thumb|Services debug screen]]
|}

'''Userspace backups'''

Here you can either archive or restore your files and configurations.

=== Illume settings ===

The Illume desktop can be easily customized - slide the top shelf down and tap the Settings icon (SHR Logo).

'''Illume settings''' provides various options to alter the desktop environment. You can change sizes of elements, single or double click, wallpaper. To access all the various options, open Illume Settings and slide the visible icons to the left, to view more options on the right hand side.

Some setting screens are not resized properly to fit the phone's display - for example the Wallpapper setting. This is a known bug already reported upstream.



==Localization==

=== Localize SHR manually ===

[[Image:SHR-Illume-Settings-Languages.png|200px|thumb|Setting Language]]

====Desktop environment====

You can change the language of the SHR desktop environment by using the Settings of Illume. For Example, for Czech language: in the Illume top shelf go to Settings (SHR Logo) -> Language -> Language Settings -> and choose: Čeština. If your language is not in the menu you can install by using opkg.

You can list all available languages by running:

opkg list | grep eglibc-locale-

And install the language of your choice (for example czech):

opkg install eglibc-locale-cs

After this, the Language Settings of Illume will offer Czech.

This will localize the Illume environment and will also set correct lang environment variable of your desktop.

====Applications====

If you wish to have other applications localized, you need to install translation for each of them (presuming it is available):

This will install czech localization for SHR phone applications, SHR Settings and TangoGps:

opkg install libframeworkd-phonegui-efl-locale-cs shr-settings-locale-cs tangogps-locale-cs

====Terminal environment====

For localized terminal environment (ssh login) set lang variables in /etc/profile.d/locale.sh, example for Czech language:

export LANG=cs_CZ
export LC_ALL=cs_CZ

====Illume keyboard and dictionaries====
[[Image:Illume-keyboards-terminal-dutch-nl-screenshot.png| Dutch terminal virtual keyboard|256px|thumb]]
→ more details on page [[Illume keyboard]]

Unlike other input methods for mobile devices, the Illume keyboard is corrective rather than predictive. It detects what you mean, even if some letters mistyped. If you accidently hit some keys next to the correct one Illume still reckognizes the word. This kind of compensates for the small size of the keys. Keep a key pressed for a longer time to affirm you really mean it.

An English dictionary is used by default. A few dictionaries for other languages are included in the SHR distribution. In addition, every dictionary for [http://en.wikipedia.org/wiki/MySpell myspell] can be used.

You can install a different keyboard with a layout which fits your language or alternatives for the default keyboards like the numerical one. The localized [[Illume keyboard]]s are available in the SHR repository under the name ''illume-keyboard-LANG''.

==== German (and Austria) Language ====

See [[Configure_SHR_for_German-speaking_use]] for detailed customization for german speaking.

===Date and time===
{{Note|This needs a complete and correct rewrite.}}

Date and time are automatically set from GPS or Network. The easiest way of setting the time for the first time is to run TangoGps (GPS & Map icon) and obtaining GPS fix. Time will then be set automatically.

The local timezone is automatically retrieved from the GSM network.

It is possible to instruct framework on how to set the time and timezone in /etc/frameworkd.conf :

[otimed]
# a list of time/zone sources to use or NONE
timesources = GPS,NTP
zonesources = GSM
# use an ip address here, otherwise DNS resolution will block
ntpserver = 134.169.172.1

To disable automatic date/zone settings, simply create an empty [otimed] section in /etc/frameworkd.conf

Timezone change

Create a symlink named /etc/localtime which points to the appropriate file in /usr/share/zoneinfo. For example, if you're in France., the following command will link the correct zoneinfo file to your /etc/localtime, giving you the correct time:

ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime

Afterwards, edit /etc/timezone if necessary [?]

Local timezone work instantly for the current boot when:

TZ="Europe/Paris"
export TZ

For a permanent timezone change edit /etc/profile and change to:

TZ="Europe/Paris"

If you use UTC time, set '''UTC=yes''' in '''/etc/default/rcS'''.

Adjusting time manually:

Via SHR-Settings -> Date/time -> Set time

From linux based desktop:

ssh root@192.168.0.202 "date -u -s `date -u +%m%d%H%M%Y.%S`"

The above does NOT work from Ubuntu as of 4/2/2010, the proper format is:

ssh root@192.168.0.202 "date -u -s `date -u +%Y.%m.%d-%H:%M:%S`"

Set the hardware clock to the system time:

hwclock --systohc

Is this better?:

hwclock --utc --systohc

==FSO Resources==

[[FSO]] is in control of each device. These are called ''resources''. If the software wanting to use the device is capable of requesting this resource via <tt>d-bus</tt>, FSO will do this, otherwise you might need to power the device manually. After the requested resource is released, FSO will power it down. Manual resource request can be done through ''SHR Setting'' or you can use <tt>fsoraw</tt> command. (Using fsoraw is faster and better than running dbus commands)

opkg install fsoraw

Example of usage fsoraw:

fsoraw -r Display mokomaze

See [[FSO Resources]] for more details on using the following resources:

'''Wifi'''

Unless this resource is enabled you've no eth0 and wifi module is completely un-powered. Use the [[Mokonnect]] network manager to set up networks, it will power Wifi up automatically when needed.

'''Bluetooth'''

You need to have this resource requested to have bluetooth module powered.

'''GPS'''

The fso-gpsd is a daemon waiting for gsmd connections, automatically powering the device on and off. When a connection exists, it powers up the GSM. In SHR Settings you can switch GPS completely off SHR Settings -> GPS -> Manual > Off

'''GSM'''

You need to have this resource requested to have GSM module powered.

'''Display'''

While this resource is requested the display won't be blanked and suspend is disabled.

'''CPU'''

While this resource is requested then suspend is disabled. Display will blank as normal.

'''Test'''

A test resource.

'''UsbHost'''

While this resource is requested the USB is turned into powered USB Host mode.

'''Accelerometer'''

You need to have this resource requested to have the Accelerometer module powered.

==Network manager==

While there are several ways of networking - Wifi, USB, Bluetooth and Gprs - By default, USB networking is enabled in <tt>/etc/network/interfaces</tt>.

Enhanced configuration is possible through direct editing of /etc/network/interfaces or through [[Mokonnect]].

The <tt>connmand</tt> daemon with Mokonnect are the recommended user level applications for setting up networking. At the moment, Mokonnect can manage USB, Wifi and Gprs connections, as well as routing and NAT. The Wifi device is not required to be manually turned on via SHR-Settings as Mokonnect will automatically enable the device when needed and disable it after use.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |
[[Image:SHR-Mokonnect.png|200px|thumb|Mokonnect]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |

[[Image:SHR-Mokonnect-Wifi.png|200px|thumb|Mokonnect Wifi]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |

[[Image:SHR-Mokonnect-Wifi-Scan.png|200px|thumb|Mokonnect Wifi Scan]]

|}

==Bluetooth==

Bluetooth can be used for several different applications - file transfer (OBEX), networking, input devices (HIDD), music playing (A2DP), calling etc. In some occasions, the devices need to be authorized - paired. At the moment, support for some bluetooth functions is better than for others - it is possible to do all mentioned above with the notice that phone calls with bluetooth headset are always routed to the bluetooth even if the bluetooth headset is not around, making it quite difficult to use.

In the SHR repositories are applications ready to be installed (by opkg) that already do provide bluetooth support. This means that they request the bluetooth resource automatically, can search bluetooth devices around, help you with pairing and can perhaps even reconnect bluetooth headset upon resume from suspend. From applications that have some bluetooth support some are for example [[Launcher]] (home screen launcher and phone suite), [[Podboy]] (podcast player), [[Elmtooth]] (bluetooth manager). In order to set up bluetooth for phone calls, some manual setup from [[#GSM_phone_calls_with_bluetooth_headset | bellow]] is still required.

===Bluez3 - the manual non D-Bus way===

If you want to use the bluetooth device directly, you need to turn the bluetooth radio on in SHR Settings -> Connectivity -> Bluetooth Radio: On. You can also make the bluetooth device visible here.

====OBEX file transfer====

There are several obex programs allowing file transfer, all in console at the moment. Obexpush installs obextool, and opd daemon:

opkg install obexpush

Default receiving path (editable in /etc/default/opd_args ) does not exist, so create it

mkdir /var/obexpush

Files are then received automatically, no notice, no confirmation... they just silently appear in /var/obexpush

To send some files, first scan for devices:

hcitool scan
Scanning ...
00:16:41:F5:A5:BC laptop

Then send the file onto bluetooth address found in the scan:

obextool push image.jpg 00:16:41:F5:A5:BC 10

====Connect Bluetooth keyboard====

hidd --search

Editors note: This is the old bluez3 way, but it works. New bluez4 way will replace this.

===Bluez4 - D-Bus based way===

SHR uses bluez4 which is completely different from bluez3. The bluetoothd is taking care of most of the bluetooth now. Please see [[Manually using Bluetooth]] for detailed information about using bluetooth and also for a list of supported devices.

====Pairing====

[[Emtooth]] is a bluetooth manager. It provides setting up bluetooth device name, pairing/unpairing, visibility setting and more. Install Emtooth:

opkg install emtooth

It will discover nearby devices, double tapping on found device will initiate pairing process.

====GSM with bluetooth headset====

In order to use bluetooth headset for phone calls, several simple steps need to be done.

1). Your bluetooth headset device must be [[#Pairing | paired]] first.

2). [[#Configuring_FSO | Add]] your bluetooth headset into FSO configuration.

Please note: phonecalls are now always routed to the bluetooth headset.
After startup and after every resume, the headset needs to be [[#Re-Connecting_the_bluetooth_headset |reconnected]].

=====Configuring FSO=====

Now we must tell frameworkd that you have a bluetooth headset. Headset parameters should be set in

/etc/freesmartphone/opreferences/conf/phone/default.yaml

Parameters bt-headset-enabled and bt-headset-address (see opreferences/schema/phone.yaml for semantics).

You need to restart FSO for the changes to take effect.

# /etc/init.d/frameworkd restart

example of my /etc/freesmartphone/opreferences/conf/phone/default.yaml:

message-length: 7
message-tone: notify_message.wav
message-vibration: 1
message-volume: 10
ring-loop: 1
ring-tone: ringtone_ringnroll.wav
ring-vibration: 1
ring-volume: 10
bt-headset-enabled: 1
bt-headset-address: 00:09:DD:31:92:98

=====Re-Connecting the headset=====

You might need to get the bluetooth headset connected manually on the beginning and also after suspend:

mdbus -s org.bluez $BTADAPTER/dev_xx_xx_xx_xx_xx_xx org.bluez.Headset.Connect

where xx_xx_xx_xx_xx_xx is address of the device, for example:

mdbus -s org.bluez $BTADAPTER/dev_00_09_DD_31_92_98 org.bluez.Headset.Connect

Hopefully, your bluetooth headset now works. Good luck!

==System Customizing==

===Installing splash screen themes===

List available splash screen themes

opkg list | grep splash-theme

Install one of the available themes

opkg install shr-splash-theme-dontpanic

Then go to '''SHR Settings -> Appearance -> Splash settings'''. Here you can preview installed themes and change the default one.

===Installing themes===

Every theme is made of several components (a theme for illume, theme for the phone applications, theme for etk and so on). There is a SHR metapackage for each theme that allows installing the complete theme in one go.

List available SHR theme metapackages:

opkg list | grep shr-theme

Install one of the available themes

opkg install shr-theme-gry

Then go to '''SHR Settings -> Appearance -> Elementary Settings'''. Here you can preview installed themes and choose the preferred one.

The Illume screen requires to change theme via '''Settings (SHR Logo) -> Look -> Theme'''. Here you can preview installed themes and choose the preferred one.

===Enable mouse cursor===

edit line 143 of /etc/X11/Xserver and erase '''-nocursor'''

ARGS="$ARGS"

===Random errors===
No icons, no GSM functions etc. happen mostly due to '''errors on your µSD''' card. Remove your card and fix it in card reader or by booting to another partition (nand) or by reboot and mount read only, then run fsck.

For reboot into nand and fix 1st partition of ext2 on your card

fsck.ext2 /dev/mmcblk0p1

===GSM modem 1024 suspend bug===

The calypso GSM modem suffers a known [[1024]] hardware bug that causes unreliable GSM function. To work it around, SHR by default doesn't suspend the modem completely. If you have undertaken a fix for this bug you can extend your battery time by enabling the modem to fully suspend when possible.

Edit the following in file:

For the new FSO2 edit /etc/freesmartphone/conf/GTA02/fsogsmd.conf

deep_sleep == "always"

Then kill fsogsmd and restart fsodeviced or reboot the phone.

For old FSO (frameworks) edit /etc/frameworkd.conf

ti_calypso_deep_sleep = always

Then restart framework or reboot the phone.

==Workarounds==

==Reporting bugs==

SHR is a work in progress. If you experience issues, please report them back to SHR. With your report provide relevant logs from

/var/log/

To report a bug, please go to http://shr-project.org/trac/report

Check if the bug is already reported. If not, add a ticket, be as much precise as you can in the title and the description, in what circumstances the issue happened and so on. If bug already exists, see if you can help fixing it by providing some fresh info.

==More information==

For SHR home page, source code and other resources, visit:

* [http://trac.shr-project.org SHR Project Homepage]
* [http://blog.shr-project.org SHR Blog]
* [http://trac.shr-project.org Trac Bugtracker]
* [http://git.shr-project.org Git Sourcecode-repository]
* [http://build.shr-project.org Downloads on buildhost]
* [http://lists.shr-project.org SHR User and Development Mailing Lists]

[[Category:SHR]]
[[Category:Manuals]]

SwapSpace

2009-12-23T23:23:26Z

Janvlug: No swap on jffs2 possible.

WARNING: THIS MIGHT KILL YOUR SD CARD, since there might be alot of read/writes on the same spot.
The Freerunner has only 128mb ram, when this is used up applications get killed.

Please note that the above warning do not apply to [[microSD]] (including microSDHC) card with wear-levelling algorithms/microcontrollers. (See [[#References]])

Please note that you can change the ''swappiness setting'' (low value, default 60) so the swap partition or swap file will be used as little as possible. (See [[#References]])

=Make swap when you are connected to your openmoko with ssh=

{{Note|swap files cannot be created on compressed file systems like jffs2. SHR uses jffs2: I created a swap file on /media/card/swapfile}}

64M byte of swap just as an example
dd if=/dev/zero of=/swapfile bs=1024 count=65536
Next time you boot there will be swap
echo "/swapfile swap swap defaults 0 0">> /etc/fstab
Make swap
mkswap /swapfile
Make the swap file work now:
swapon /swapfile

=Make swap when microSD card is in a card reader=
The uSD card is booted on /boot. To use this, we need to make sure that the microsd card is booted, and the Swap can be turned on.

Create the swapfile on the uSD card.
# dd if=/dev/zero of=/boot/swapfile bs=1024k count=128
# mkswap /boot/swapfile

Now, we can put in an init script for [[Fyp]] which does this for us everytime we boot.

# touch /etc/init.d/extswap.sh
# chmod +x /etc/init.d/extswap.sh
# cat > /etc/init.d/extswap.sh
#! /bin/sh
### BEGIN INIT INFO
# Provides: extswap
# Required-Start: mountall
# Required-Stop:
# Default-Start: S
# Default-Stop:
# Short-Description: Uses Additional Swap If Available. works on SHR distro
# Description:
### END INIT INFO

PATH=/sbin:/bin

do_start() {
modprobe loop
echo 10 > /proc/sys/vm/swappiness
if [ -e /boot/swapfile ] ; then
for loopdev in `ls /dev/loop* 2>/dev/null` ; do
losetup $loopdev /boot/swapfile && swapon $loopdev && echo $loopdev > /var/extswapfile && break
done
fi
}

do_stop() {
loopdev=`cat /var/extswapfile 2>/dev/null`
swapoff $loopdev 2>/dev/null && rm -f /var/extswapfile && losetup -d $loopdev
}

case "$1" in
start|"")
do_start
;;
restart|reload|force-reload)
do_stop
do_start
;;
stop)
do_stop
;;
*)
echo "Usage: extswap.sh [start|stop|restart]" >&2
exit 3
;;
esac
# update-rc.d extswap.sh defaults

==References==
*[http://www.notebookreview.com/default.asp?newsID=4258 2/17/2008, notebookreview.com: SDHC Cards vs Hard Drive vs SSD] Quote: "...That sounds like an absolutely manditory thing to have in flash storage ... and luckily "high-performance" SDHC cards such as the 16GB A-DATA SDHC card and many other class 6 cards from other manufacturers incorportate wear-leveling [Please check before you buy!]..."
*[[MicroSD]](HC) cards are a sort of a SSD: [http://robert.penz.name/137/no-swap-partition-journaling-filesystem-on-a-ssd/ December 7, 2008, robert.penz.name: No SWAP Partition, Journaling Filesystems, … on a SSD?] Quote: "...They assume perfect wear leveling...We stay also with the 2 million cycles and assume a 16GB SSD *With 50 MByte/sec we get 20 years! *With 2 MByte/sec we get 519 years! *And even if we reduce the write cycles to 100.000 and write with 2 MByte/sec all the time we’re at 26 years!!...1. Never choose to use a journaling file system on the SSD partitions: Bullshit, you’re just risking data security. Stay with ext3...7. One more thing to consider is that flash-devices handle their space in blocks. The blocksize typically varies between 16KB and 512 KB. Therefore writing one byte may cause erase and rewrite of up to 512KB..."
*[http://fosswire.com/post/2009/2/sysctl-swappiness/ fosswire.com: Speed up your system by avoiding the swap file] Quote: "...the Linux kernel provides a tweakable setting that controls how often the swap file is used, called swappiness. A swappiness setting of zero means that the disk will be avoided unless absolutely necessary (you run out of memory), while a swappiness setting of 100 means that programs will be swapped to disk almost instantly..."

==Links==
*http://www.google.dk/search?q=linux+swap+partition+vs+file+speed

[[Category:MicroSD]]
[[Category:Application Developer]]

Manuals/SHR

2009-12-14T12:27:22Z

Janvlug: /* Getting SHR */ type

{{Languages|Manuals/SHR}}
{| align="right"
| __TOC__
|}

==SHR Introduction==

Welcome to '''[[SHR]]''', a community driven distribution for (not only) Openmoko Neo phones.

[[Image:SHR-Logo.png|200px|thumb|center|SHR]]

'''SHR''' (Stable Hybrid Release) is here to provide you with Root FileSystem images that you can easily install onto your phone to use as a daily phone. There are many prepackaged programs available that can be installed upon demand by users, it can also be used by developers as a base image for customized and flavored distribution or release. '''SHR unstable''' is a testing environment before software get stabilized and it is the main testing ground for [[FSO]] releases. '''SHR testing''' images provide as much stability as possible for day-to-day usage.

SHR users, readers of this manual, please report improvements, discrepancies or missing features on this page to <tt>vanous @ penguin . cz</tt>. Thank you.

[http://shr-project.org SHR Project page]

==Installation==

===Getting SHR===

First, determine which model of phone you have, the GTA01 (Neo 1973) or the GTA02 (Neo FreeRunner).

You need to download two files for your version as above: kernel and root filesystem. Depending whether you will be installing into the internal [[NAND memory]] or on [[µSD]] card, you need to either get .jffs2 file for NAND or .tar.gz file for µSD.

For the '''GTA02 Neo FreeRunner''' you need to download the images of the:
*testing line: http://build.shr-project.org/shr-testing/images/om-gta02/
*unstable line: http://build.shr-project.org/shr-unstable/images/om-gta02/

- Get the latest kernel from the above linkpage. Starts with uImage-...

- Get the root filesystem, for NAND: full-om-gta02.jffs2, for µSD: full-om-gta02.tar.gz

The above are '''full''' images. You can also choose images with less packages, marked as '''lite''' which can be upgraded to the full image by running

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

- '''Get the kernel modules.''' From the same page, download the modules to match your kernel (their dates should be the same). Put that file on the FreeRunner and run

gzip -dc modules-...tar.gz | tar -xf - -C /
depmod -a

Editors note: Running depmod should not be necessary, if it's needed, please report a bug. Recommending of the depmod command will be removed in near future.

'''GTA01 Neo 1973''' images are at (20091130 future):
*http://build.shr-project.org/shr-unstable/images/om-gta01/

===Installation on Flash===

In order to install your SHR distribution directly to your Freerunner Flash memory (NAND), you need to get the desired filesystem file ( <tt>.jffs2</tt> ) as described above and flash your device using the <tt>dfu-util</tt> tool.

Please visit [[Flashing the Neo FreeRunner]] for more details about flashing and see [[Dfu-util]] for detailed information about the dfu-util.

{{Note|Your battery must be charged (sufficiently) before NAND flashing. Symptom of insufficient charge: Your progress bar "####" stops while flashing. If so, you must charge, and later you should be able to make the complete flash.}}
Commands to flash the filesystem and the kernel:

for the GTA02 Neo FreeRunner:

sudo dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D full-om-gta02.jffs2
sudo dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-om-gta02-latest.bin

for the GTA01 Neo 1973:

sudo dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a rootfs -R -D full-om-gta01.jffs2
sudo dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a kernel -R -D uImage-om-gta01-latest.bin

===Installation on µSD Card===

Installing SHR on your µSD Card depends on the Bootloader you are using, ''uBoot'' or ''Qi''.

In simply words, difference between both systems resides on how you must prepare your µSD Card and files you use to fill them:

* If you use ''uBoot'', you need to create two partitions. First partition, not so big, in FAT16 or ext2 where you have to place the kernel file (<tt>uImage-om-gta02-latest.bin</tt>) and second partition in ext2 or ext3 where you have to uncompress the filesystem file (<tt>shr-image-om-gta02.tar.gz</tt>).

* If you use ''Qi'', you only need an ext2 partition into your µSD Card where you uncompress the filesystem image file (<tt>shr-image-om-gta02.tar.gz</tt>). In this case Qi Bootloader is going to look for the kernel image into the <tt>/boot</tt> directory for file named <tt>uImage-GTA02.bin</tt> .

Please visit links below for detailed information and tips:
*For [[Booting from SD | uBoot]] and for [[Qi]].

===SHR version===

Should you ever later wonder what version of SHR you have actually installed, please run

cat /etc/shr-version

{{Note|Please note that running opkg update;opkg upgrade does not change the SHR version. Only flashing or a new image download can change the SHR version.}}

===Booting===
Press the power button shortly to start the phone. The booting splash screen will appear. The first boot after a new installation always takes a bit longer. It is recommended to reboot after this first boot, to make sure all packages got initialized properly.

[[Image:Shr-boot-preview.png|200px|thumb|center|SHR Boot Splash screen]]

===Initial Setup===

On the first boot, Setup is automatically initiated to walk the user through basic setup of the Enlightenment desktop environment. You are able to choose preferred language of the desktop environment and the theme. However both options are only offering one choice at the moment.

{| class="wikitable"
| [[Image:SHR-Setup-Language.png|200px|thumb|language selection]]
| [[Image:SHR-Setup-Profile.png|200px|thumb|choosing from two themes (from an older version of SHR)]]
|}

==Running SHR==

===SIM Auth===

[[Image:SHR-SIM-Auth.png|200px|thumb|center|SIM Auth]]
SIM Pin is asked for upon start up.

===First look===
[[Image:SHR-First-Look.png|200px|thumb|Desktop screen]]
'''Illume desktop''' is the default home screen of the SHR desktop. Application files located in /usr/share/applications are displayed here. All applications are ran fullscreen and you can switch between them by using the Task switcher in the top shelf or by using the '''<''' left or right '''>''' arrows in the top shelf.

===Phone applications===

Besides other software, SHR comes with 4 main phone applications: ''Dialer'', ''Contacts'', ''Messages'' and ''Phone log''.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Dialer.png|200px|thumb|Dialer]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Contacts.png|200px|thumb|Contacts]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Contacts-Options.png|200px|thumb|Contact options]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Contact-Add.png|200px|thumb|Add new contact]]
|}

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Mesages.png|200px|thumb|Messages]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |

[[Image:SHR-Messages-Options.png|200px|thumb|Messages options]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Message-View.png|200px|thumb|View message]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Message-View-chars.png|200px|thumb|Unicode support]]

|}

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Mesages-Options.png|200px|thumb|Message options]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |

[[Image:SHR-Phonelog.png|200px|thumb|Phonelog]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |

[[Image:SHR-Dialer-Active.png|200px|thumb|Active call]]

|}

Upon a missed call or an unread message there is a notifier that presents a screen with button to run Messages or Phonelog application, or you can simply close the Notifier with the Top Shelf cross.

===First steps===

Right after installation and first boot you might want to do a few initial steps:

{{Note|In SHR testing 091210 the default max charging current is 100mA. Change it to 500mA via "Settings", if your USB port can supply it or else the charging will be slow. The Openmoko power supply can supply up to 1000mA via the USB port without changing settings.}}

====Network Connection====
''Establish network connection'' and SSH into your phone. The <tt>root</tt> account uses no password by default. You can establish connection either via USB to your desktop and enable NAT or you can connect through Wifi. If you use USB, some setup is required on the desktop side, please read [[USB_Networking]]. For Wifi, you can use [[#Network manager|Network Manager]]

====GSM Network====
''Check if GSM is working correctly'' - observe the GSM gadget in the Top Shelve and see reported signal of your GSM operator. If GSM Gadget seems not be running, click ''Settings'' and later on ''Phone''. Move ''GSM Antenna'' to ''On''.

====Audio: Volume====
''Check and set call volume'' - this is handled by alsa state files in <tt>/usr/share/shr/scenarii/</tt> . To customize speaker volume edit <tt>/usr/share/shr/scenarii/gsmhandset.state</tt> and change <tt>control 4</tt>. Values between from 105 to 120 might be sufficient:

vi /usr/share/shr/scenarii/gsmhandset.state
or post 091204?
vi /etc/freesmartphone/alsa/default/gsmhandset

control.4 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 127'
iface MIXER
name 'Speaker Playback Volume'
value.0 116
value.1 116
}

Should you want to alter more parameters be aware that each file is a set of value for the 94 parameters. Some of the important ones are:

Control 48: internal mic of the tel (set to 2 or 3)
Control 4 : internal speaker (set from 110 to 120)
Control 49: headset mic
Control 3 : headset speaker

====Initializing the opkg database====
''Initialize the opkg database'' in order to install some applications from SHR repositories or from other sources, for example [[http://opkg.org opkg.org]]. While still being online, you need to first run

opkg update

Searching in the opkg database can take a long time. You can speed things up by dumping the database into a file and grepping it through.

Do this only once or after every opkg update:

opkg list > packages.txt

Then you can search quickly for package name, for example for navit:

grep navit packages.txt

====SwapSpace====
{{Main|SwapSpace}}
When the RAM is used up, applications get killed. This is particularly bad while doing opkg upgrade. Therefore you might want to create a swap space. Read [[SwapSpace]]

====Changing root password====

Recent images will show up a prompt to change the root password during the first boot wizard.
If for some reason this prompt doesn't show up you can change the password by using the terminal emulator in your SHR installation.

For older images,
SHR is shipped without root password (just press enter)

This is very dangerous if you connect using wifi, or USB. You need to activate the root password:

passwd

then type your selected password (2 times)

A much more convenient way might be to install your public-key to ~/.ssh/authorized_keys. You can find your public-key of you host at location:

/path/file

For running
cmd | ssh root@neo anycommand
from your host this might be even mandatory, e.g if you want to pipe anything to the ssh.

===Localization===

==== Localize SHR manually ====

[[Image:SHR-Illume-Settings-Languages.png|200px|thumb|Setting Language]]

You can change the language of the SHR desktop environment by using the Settings of Illume. For Example, for Czech language: in the Illume top shelf go to Wrench (Settings) -> Language -> Language Settings -> and choose: Čeština. If your language is not in the menu you can install by using opkg.

You can list all available languages by running:

opkg list | grep eglibc-locale-

And install the language of your choice (for example czech):

opkg install eglibc-locale-cs

After this, the Language Settings of Illume will offer Czech.

This will localize the Illume environment and will also set correct lang environment variable. If you wish to have translations for other applications, you need to install them again (presuming they are available):

This will install czech localisation for SHR phone applications, SHR Settings and TangoGps:

opkg install libframeworkd-phonegui-efl-locale-cs shr-settings-locale-cs tangogps-locale-cs

For localized terminal environment (ssh login) set lang variables set /etc/profile, example for Czech language:

export LANG=cs_CZ
export LC_ALL=cs_CZ

The Illume keyboard offers english dictionary correction by default. You can list all the dictionaries available for installation:

opkg list | grep illume-dic

If your language is not available and english is bothering you, you can set an empty dictionary:

echo "" > /usr/lib/enlightenment/modules/illume/dicts/None.dic

By using it, it will get filled by the words you use and after time will start helping and correcting your typing.

[[Image:Illume-keyboards-terminal-dutch-nl-screenshot.png| Dutch terminal virtual keyboard|256px|thumb]]
Furthermore you can install a different keyboard with a layout which fits your language or alternatives for the default keyboards like the numerical one. The localized [[Illume keyboard]]s are available in the SHR repository under the name ''illume-keyboard-LANG''.

Note that sometimes after an upgrade of Illume has taken place, these keyboards have to be installed again before the become available again. Removing these packages will restore the availability of the respective original keyboards.

==== German (and Austria) Language ====
Find a hopefully [[Configure_SHR_for_German-speaking_use|stable SHR German language version]] with Austrian Maps [[Configure_SHR_for_German-speaking_use|here]]. The configuration can be used for any
German speaking country. The Austrian maps for [[Navit]] can be replaced and Navit is "speaking" German. Navit is configured with a preselect of country "Austria" (see [[Navit]]), There are some differences between dictionary de_AT (Austria) and de_DE (Germany).

===Date and time===

The local timezone is automatically retrieved from the GSM network.

create a symlink named /etc/localtime which points to the appropriate file in /usr/share/zoneinfo. For example, if you're in France., the following command will link the correct zoneinfo file to your /etc/localtime, giving you the correct time:

ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime

Afterwards, edit /etc/timezone if necessary [?]

Local timezone work instantly for the current boot when:

TZ="Europe/Paris"
export TZ

For a permanent timezone change edit /etc/profile and change to:

TZ="Europe/Paris"

Date and time are automatically set from GPS or Network. The easiest way of setting the time for the first time is to run TangoGps (GPS & Map icon) and obtaining GPS fix. Time will then be set automatically after several minutes.

Time can set time also manually.

Via SHR-Settings -> Date/time -> Set time

From linux based desktop:

ssh root@192.168.0.202 "date -u -s `date -u +%m%d%H%M%Y.%S`"

You can also set the hardware clock to the system time:

hwclock --systohc

Is this better?:

hwclock --utc --systohc

It is possible to instruct framework on how to set the time and timezone in /etc/frameworkd.conf :

[otimed]
# a list of time/zone sources to use or NONE
timesources = GPS,NTP
zonesources = GSM
# use an ip address here, otherwise DNS resolution will block
ntpserver = 134.169.172.1

To disable automatic date/zone settings, simply create an empty [otimed] section in /etc/frameworkd.conf

===File transfer===

After you have established network connection, it is very easy to access and transfer files. The easiest solution is to use Konqueror or Nautilus on your desktop computer and type the following on your location bar. This should provide you with a view of the client's file system on Konqueror or Nautilus and you can easily drag-drop and copy-paste files.

sftp://root@192.168.0.202

===Reporting bugs===

SHR is a work in progress. If you experience issues, please report them back to SHR. With your report provide logs from

/var/log/ophonekitd
/var/log/frameworkd

To report a bug, please go to http://shr-project.org/trac/report

Check if the bug is already reported. If not, add a ticket, be as much precise as you can in the title and the description, in what circumstances the issue happened and so on.

==Settings==
===SHR Settings===
[[Image:SHR-Settings-main.png|200px|thumb|SHR Settings]]

SHR Settings is the main setting application of SHR. It provides an easy way of setting up your phone to your liking - from phone related settings, to requesting resources in order to prevent screen dim or suspend (for example while using GPS).

Please refer to [http://wiki.openmoko.org/wiki/FSO_Resources#Automatic_way this wiki page] about a better way to manage preventing screen dim or suspend.

While some settings are persistent over reboots, others are not.

====Main Screen====
The main screen is divided into eight categories, which contain several modules. Every SHR Settings module has a specified task - for example controlling the GSM antenna power, setting the time etc.

====Settings: Phone====
Here you can set if the GSM antenna is on and if your phone number is shown when you call someone.

'''GSM'''
In GSM settings you can turn off and on GSM module. After turning off antenna, whole GSM modem is turned off.

To list available providers, click on Operators button. Scanning can take some time. After a while, a list of operators should pop up.

You can't connect to operators marked [forbidden]. After a connection failure, a message is displayed.

Selecting an operator from the list also changes modem registration mode to manual. It won't register to other network, even if some is available and has better signal strengh. To return to automatic mode, click "Automatic" button in operator list.

'''Call'''
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Phone.png|200px|thumb|Phone settings]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-List-providers.png|200px|thumb|List providers]]

|}

You can set if your phone number should be displayed to other party. You can either depend on network decision ("By network") or force it manually ("Manual")

'''Phoneutils'''

For the default SHR phone applications to be able to correctly parse incoming calls/messages and match them with your contacts, you will need to set the right country code for your location. (for example 42 for Czech republic) for more info, please go to: http://wiki.openmoko.org/wiki/Phone_Prefixes

'''SIM'''

Here you can view some informations about your SIM card and clean phone and messagebooks.

====Settings: Profiles====

Here you can select the current profile, which the device should use to determine ring tone etc.

'''Current profile'''

Here you can adjust properties of the currently used profile. Available settings: ring tone, ring volume, ring vibration, ring loop, ring length, message tone, message volume, message vibration, message loop, message length.

To change the ring tone, click the "Change" button.

To use your own ring tone, place it in /usr/share/sounds directory.

After selecting a sid tune as the ring tone, there are available controls to select tune number from the file.

This is changing settings in /etc/freesmartphone/opreferences/conf/phone/default.yaml

ring-volume # Ring Volume control 0 (mini) to ? maxi)
ring-length # min time for ringtone. Must be greater than the duration of you ringtone
ring-loop # define the number of loop of ringtone to play
ring-tone: "ringtone_ringnroll.ogg" # .ogg example
ring-tone: "Arkanoid_PSID.sid" # .sid example, use default tune
ring-tone: "Arkanoid_PSID.sid;tune=2" # .sid example, plays the second tune of that

If you like to test a .sid you can play it using this command on the FR:

gst-launch filesrc location=Arkanoid_PSID.sid ! siddec tune=2 ! alsasink

Note that it's a ! used and not a | to construct the gstreamer pipe command.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Profiles.png|200px|thumb|Profiles]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Profiles-Ringtones.png|200px|thumb|Ringtones]]

|}

====Settings: Connectivity====

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Connectivity.png |200px|thumb|Connectivity top]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Connectivity2.png |200px|thumb|Connectivity bottom]]
|}

'''WiFi'''

With the "WiFi radio" toggle you can set, if the wifi module is powered. WiFi radio has to be turned on before trying to connect to a WiFi network, unless you try to connect through [[Mokonnect]] which is capable of powering it up.

'''GPRS'''

To enter APN, login and password fields, just click on the actual value (default: "internet"). Keyboard will pop up.
If you don't know APN, login and passwork, ask your provider.}}

{{Note|You can also use Mokonnect to manage your GPRS connection}}

To connect to the GPRS network, just click the "Connect" button. Entered values will be saved after successful connection.

'''USB'''

With this toggle you can switch USB port between device (Neo to PC) or host (device to Neo) modes.

'''Bluetooth'''

To power up Bluetooth module, switch the "Bluetooth radio" toggle to "On". After that, the "Visibility" toggle should arrive - set it to "On" if you want your FR to be visible by other Bluetooth devices on scanning.

====Settings: Power====

'''Battery'''

This module displays informations about battery state - charge, voltage, remaining time etc. To update the data, click the "Update" button.

Here you can also force enable 500mA charging.

'''Display'''

With this slider you can easily set the backlight brightness.

{{Note|This setting isn't permanent over sessions. At boot backlight is set back to 100%.}}

'''Power'''

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Power.png |200px|thumb|Power]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Timeouts.png |200px|thumb|Timeouts]]
|}

Here you can turn on or off automatic dimming or suspend after idle timeout (see: Timeouts module)

'''Timeouts'''

Here you can set up values of idle timeouts used by the device. Timeouts are reached in this order: idle -> idle dim -> idle prelock -> lock -> suspend. Idle, idle prelock and lock aren't used by default in SHR at the moment. This setting changes parameters in /etc/frameworkd.conf :

[fsodevice.kernel_idle]
suspend = 20
lock = 2
idle_prelock = 12
idle = 10
idle_dim = 20

====Settings: Appearance====

'''Theming'''
[[Image:SHR-Neo-Theme.png|200px|thumb|Neo theme]]
Find available themes by running

opkg list | grep theme-illume

install it by

opkg install e-wm-theme-illume-sixteen elementary-theme-sixteen

http://opkg.org has a very fast theme called nEo

opkg install http://www.opkg.org/packages/e-wm-theme-neo_0.2_armv4t.ipk
opkg install http://www.opkg.org/packages/elementary-theme-neo_0.2_armv4t.ipk
opkg install http://www.opkg.org/packages/etk-theme-neo_0.2_armv4t.ipk
opkg install -force-overwrite http://www.opkg.org/packages/libframeworkd-phonegui-efl-theme-neo_0.2_armv4t.ipk

If you also want the GTK+ Applications to fit in with the rest of the Systems look execute

opkg install http://www.opkg.org/packages/gtk-theme-neo_0.1_armv4t.ipk

For a completely monolithic look additionally execute

opkg install -force-overwrite http://www.opkg.org/packages/gpe-theme-neo_0.1_armv4t.ipk
opkg install http://www.opkg.org/packages/icon-theme-neo_0.2_armv4t.ipk

Please observe the command line output when installing these themes, since it will tell you how to activate the themes.

{{Note|some of the theme packages have to be reinstalled after an opkg upgrade.}}

Reverting back can be done by

opkg install e-wm-theme-illume-sixteen shr-theme-gtk-e17lookalike -force-reinstall
opkg install libframeworkd-phonegui-efl0 e-wm-theme-default etk-theme-shr shr-theme -force-reinstall

====Settings: Position====

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-GPS.png |200px|thumb|center|GPS]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-GPS-Satelites.png |200px|thumb|GPS Satelite details]]
|}

'''GPS'''

By default, GPS is turned on only when requested (when you turn on TangoGPS, Navit, omgps or other GPS app). That state corresponds to "Auto" setting. After changing to "Manual", you can force set it to on or off.

'''GPS information'''

This page can be used to monitor GPS status. If some value isn't known, then "unknown" is displayed.

You can also view information about every visible satellite and check, which are used for getting a fix. To do that, click "Satellite details".

'''Remove AGPS data'''
If you experience problems with GPS, turn it off, click "Remove AGPS data" and reboot your Neo.
Assisted GPS ([[aGPS]]) support GPS receiver to find position by non-satellite information.

'''Save downloaded maps of TangoGSP on Memory Card'''

By default, TangoGPS will save your downloaded maps in /home/root/Maps. But it'll be inconvenient if you flashing again. You can change the path of folder Maps into a folder we created in Memory Card by using Config (Map Repositories) of TangoGPS.

Otherwise, if you have a problem that can't change in that way. Don't be upset, there's another way. First you create a folder <tt>Maps</tt> on Memory Card:
mkdir /media/mmcblk0/Maps
Then you have to delete folder <tt>Maps</tt> in your home directory (e.g <tt>/home/root/Maps</tt> if it exists.
rm -R /home/root/Maps
Then we'll create a symbolic link ("-s") for the created Maps folder on Memory Card in your the home directory of root on the Phone by
ln -s /media/mmcblk0/Maps /home/root/Maps
That should be fine. From now, everytime when you download new maps, it'll be saved directly to folder <tt>Maps</tt> on Memory Card.

Note: repeat the second and the third step (remove Maps in home/root and create link) have to be repeated if you want to link to the downloaded maps for TangoGPS after flashing phone.

====Settings: Date/time====

[[Image:SHR-Settings-Date-Time.png |200px|thumb|Date & Time]]

'''Time'''

Here you can view and set the time. By default, the time is just displayed, To adjust it, click on "Set time".

After finishing adjusting, click the "OK" button.

'''Date'''

This module displays the current date.

====Settings: Others====

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

[[Image:SHR-Settings-Others.png |200px|thumb|Others]]

'''PIM'''

Every opimd domain has different backends to store its data. The domain reads data from every backend and writes data to the default backend. So with the selector in shr-settings you can choose the backend that stores newly generated data, it doesn't copy or move existing data to a different backend.

'''Services'''

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Services.png |200px|thumb|center|Services]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Service-restart.png |200px|thumb|Services debug screen]]
|}

Here is listed every interesting script from /etc/init.d/ directory.

After clicking on one, you can either start, restart or stop the service and view the result.

'''Userspace backups'''

Here you can either archive or restore your files and configurations.

=== Illume settings ===

The Illume desktop can be easily customized - slide the top shelf down and tap the Settings icon (Wrench).

{{Note|TIP: for better access of the Settings icon, tap and hold the Settings icon, then drag it to the right.}}

'''Illume settings''' (the wrench) provides various options to alter the desktop environment. You can change sizes of elements, single or double click, wallpaper. To access all the various options, open Illume Settings and slide the visible icons to the left, to preview more options on the right hand side.

The little applets in the top shelf (for example Battery, GSM, Bluetooth etc.) are called '''shelf gadgets''' and you can configure whether they are visible (on the front part of the top shelf) or hidden (you can access them by sliding the top shelf) through Illume Settings -> Display -> Shelf gadget.

Some screens are not resized properly to fit the phone's display - for example the Wallpapper setting. This is a known bug already reported upstream.



==FSO Resources==

FSO is in control of each device. These are called ''resources''. If the software wanting to use the device is capable of requesting this resource via <tt>d-bus</tt>, FSO will do this, otherwise you might need to power the device manually. After the requested resource is released, FSO will power it down. Manual resource request can be done through ''SHR Setting'' or you can use <tt>fsoraw</tt> command. (Using fsoraw is faster and better then running dbus commands)

opkg install fsoraw

Example of usage fsoraw:

fsoraw -r Display mokomaze

See [[FSO Resources]] for more details on using the following resources:

'''Wifi'''

Unless this resource is enabled you've no eth0 and wifi module is completely un-powered. Use the network manager to set up networks, [[Mokonnect]] will power Wifi up automatically when needed.

'''Bluetooth'''

You need to have this resource requested to have bluetooth module powered.

'''GPS'''

The fso-gpsd is a daemon waiting for gsmd connections, automatically powering the device on and off. When a connection exists, it powers up the GSM. In SHR Settings you can switch GPS completely off SHR Settings -> GPS -> Manual > Off

'''GSM'''

You need to have this resource requested to have GSM module powered.

'''Display'''

While this resource is requested the display won't be blanked and suspend is disabled.

'''CPU'''

Default rules.yaml checks for this resource to disable automatic suspend when it's requested. While this resource is kept suspend is disabled (but screen can be blanked).

'''Test'''

A test resource

==Network manager==

While there are several ways of networking - Wifi, USB, Bluetooth and Gprs - By default, USB networking is enabled in <tt>/etc/network/interfaces</tt>.

Enhanced configuration is possible through direct editing of /etc/network/interfaces or through [[Mokonnect]].

The <tt>connmand</tt> daemon with Mokonnect are the recommended user level applications for setting up networking. At the moment, Mokonnect can manage USB, Wifi and Gprs connections, as well as routing and NAT. The Wifi device is not required to be manually turned on via SHR-Settings as Mokonnect will automatically enable the device when needed and disable it after use.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |
[[Image:SHR-Mokonnect.png|200px|thumb|Mokonnect]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |

[[Image:SHR-Mokonnect-Wifi.png|200px|thumb|Mokonnect Wifi]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |

[[Image:SHR-Mokonnect-Wifi-Scan.png|200px|thumb|Mokonnect Wifi Scan]]

|}

==Bluetooth==

Bluetooth can be used for several different applications - file transfer, networking, HIDD, music playing (A2DP), calling etc. In some occasions, the devices need to be authorized - paired. At the moment, support for some bluetooth functions is better than for others - it is possible to do all mentioned above with the notice that phone calls with bluetooth headset are always routed to the bluetooth even if it is not around, making it quite difficult to use.

Don't forget you need to turn the bluetooth radio on in SHR Settings -> Connectivity -> Bluetooth Radio: On, where you can also make the bluetooth device visible.

SHR uses bluez4 which is completely different from bluez3. The bluetoothd is taking care of most of the bluetooth now. Please see [[Manually using Bluetooth]] for detailed information about using bluetooth and also for a list of supported devices.

===OBEX file transfer===

There are several obex programs allowing file transfer, all in console at the moment. Obexpush installs obextool, and opd daemon:

opkg install obexpush

Default receiving path (editable in /etc/default/opd_args ) does not exist, so create it

mkdir /var/obexpush

Files are then received automatically, no notice, no confirmation... they just silently appear in /var/obexpush

To send some files, first scan for devices:

hcitool scan
Scanning ...
00:16:41:F5:A5:BC laptop

Then send it onto bt address found in the scan:

obextool push image.jpg 00:16:41:F5:A5:BC 10

===Connect Bluetooth keyboard===

hidd --search

Editors note: This is the old bluez3 way, but it works. New bluez4 way will replace this.

===Pairing===

This comes from [[Manually_using_Bluetooth#Once_Again.2C_Bluetooth_Headset_on_Freerunner]]

Now, you must pair the bluetooth headset with your phone. Make sure the bluetooth chip is powered up (can be done through the Connectivity section in the SHR-Unstable settings manager) and that bluetoothd is running:
/etc/init.d/bluetooth start
Now, to actually pair the bluetooth headset, you will need the simple-agent script. If you already have it, excellent. If you, like me, do not, then you can get it here: http://dl.getdropbox.com/u/453116/simple-agent

Put it in /usr/bin/ and run ===chmod a+x /usr/bin/simple-agent===

Now put your headset into pairing mode and run

hcitool scan

Find your headset and use its address in the command

simple-agent hci0 XX:XX:XX:XX:XX:XX

If you give a third parameter (what it is doesn't matter) to simple-agent, it will disconnect then reconnect to the headset (reset pairing).

===GSM phone calls with bluetooth headset===

Your bluetooth headset device must be paired first.

====Configuring bluez====

Older SHR releases you need to uncomment <tt>SCORouting=PCM</tt> setting in <tt>[General]</tt> section of

/etc/bluetooth/audio.conf

like this:

# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
SCORouting=PCM

do not forget to restart bluetoothd after that.

/etc/init.d/bluetooth stop
/etc/init.d/bluetooth start

====Configuring FSO====

Now we must tell frameworkd that you have a bluetooth headset. Headset parameters should be set in

/etc/freesmartphone/opreferences/conf/phone/default.yaml

Parameters bt-headset-enabled and bt-headset-address (see opreferences/schema/phone.yaml for semantics).

You need to restart FSO for the changes to take effect.

/etc/init.d/frameworkd restart

example of my /etc/freesmartphone/opreferences/conf/phone/default.yaml:

message-length: 7
message-tone: notify_message.wav
message-vibration: 1
message-volume: 10
ring-loop: 1
ring-tone: ringtone_ringnroll.wav
ring-vibration: 1
ring-volume: 10
bt-headset-enabled: 1
bt-headset-address: 00:09:DD:31:92:98

====Re-Connecting the bt device====

You might need to get the bluetooth headset connected manually on the beginning and also after suspend:

mdbus -s org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_xx_xx_xx_xx_xx_xx org.bluez.Headset.Connect

where xx_xx_xx_xx_xx_xx is address of the device, for example:

mdbus -s org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_00_09_DD_31_92_98 org.bluez.Headset.Connect

Hopefully, your bluetooth headset now works. Good luck!

==System Customizing==

===Changing the splash screen===

list available splash screen themes

opkg list | grep splash-theme

and install one of the available themes

opkg install shr-splash-theme-dontpanic

Then go to SHR Settings -> Others -> Themes. Here you can preview installed themes and change the default one.

===Enable mouse cursor===

edit line 121 of /etc/X11/Xinit and erase -hide-cursor

ARGS="$ARGS -dpi ${DPI} -screen ${SCREEN_SIZE} -mouse tslib -root-ppm /usr/share/pixmaps/xsplash-vga.ppm vt1"

===Speedup of suspend and wake up===

Some setup types of the bootloader are causing slow suspending and waking up through a long console output. ([http://shr-project.org/trac/ticket/351 bug report]) This occurs when using the the Qi bootloader in combination with an installation on an SD card and when using the u-boot bootloader.

I you are using Qi and installation on a µSD card, you can change the kernel parameter loglevel=1 in /boot/append-GTA02.

===Opimd utils===

Opimd utils is a set of several testing scripts to play with the new opimd backends. It also provides opimd-messages program and mainly new opimd-notifier
that is much better then the standard one.

For further Information refer to the corresponding [[Opimd|Wiki Page]].
opkg install opimd-utils

{{Note| opimd-utils isn't announced yet! It can eat your cat! Don't touch it unless you are opimd developer or you are writing app with opimd support.

'''NOTE 2:''' In order to have sound and vibration on incoming message when using opimd interface, you have to patch oeventsd with patch available at [http://openmoko.opendevice.org/~dos/opimd/oeventsd/]

'''NOTE 3:''' For testing and development opimd recommended distribution is ''upgraded'' SHR unstable.
}}

===opkg upgrade issues===

{{Note| Image unstable/testing december and previously: Before upgrading (via opkg), you should go to "Settings"->"Power" and change "Auto-suspend" to "Off", or else your phone will suspend while upgrading. Former images: If "Auto-suspend" can not be found, you must prevent the phone from suspending while upgrading. Tap shortly (within 1-2 seconds?) on the just blackened screen to prevent suspending. After the upgrade the "Auto-suspend" settings will be available.
}}

You can request the CPU resource (temporary non-suspend) while executing opkg by inserting this in file /etc/profile :
alias opkg="fsoraw -r CPU -- opkg"

To make the alias work at once for the current boot execute:
alias opkg="fsoraw -r CPU -- opkg"
Source: spaetz

As '''opkg''' had some '''issues''' recently, installation might get broken due to that. You can fix it or prevent by using the following scripts

Safe update packages:

#!/bin/sh

for pkg in `opkg list_upgradable | awk '!/(kernel|Multiple)/ {print $1}'`
do
echo "installing pack $pkg"
opkg install $pkg -force-reinstall
done

Force reinstall all installed packages:

#!/bin/sh

for pkg in `opkg list_installed | awk '!/(kernel|Multiple)/ {print $1}'`
do
echo "installing pack $pkg"
opkg install $pkg -force-reinstall
done

===Random errors===
No icons, no GSM functions etc. - this is mostly due to '''errors on your µSD''' card. Remove your card and fix it in card reader or by booting to another partition (nand) or by reboot and mount read only, then run fsck.

For reboot into nand and fix 1st partition of ext2 on your card

fsck.ext2 /dev/mmcblk0p1

===Adding your phone to your hosts===

You can add your phone to your hosts file for a name resolving:

You can use the name <tt>neo</tt> if you added the host <tt>neo</tt> in <tt>/etc/hosts</tt> on your desktop computer (add the following line for host <tt>neo</tt> assuming that the IP-address of your phone is <tt>192.168.0.202</tt>.
echo "192.168.0.202 neo neo" >> /etc/hosts

You can then access your phone like this:

ssh root@neo

Which is shorter than this:

ssh root@192.168.0.202

==Installing Software==

You can use opkg for installing software packages or you can try SHR Installer from http://git.shr-project.org/git/?p=shr-installer.git;a=summary . It requires packagekitd

opkg install packagekitd

If you wan to use opkg after you used the installer, make sure packagekitd is not running

killall packagekitd

'''Cool applications'''

SHR comes with only a few preinstalled applications but its repository provides more cool stuff. Also, there are applications that are not in SHR repos at the moment but can still be installed. The following few examples are here just to spark your interest:

'''[[Paroli]]''' is available in SHR images, you can install it:

opkg install paroli

fix the conf files that the paroli installer messes with (might get fixed in the next couple of days.)

cp /etc/old_frameworkd.conf /etc/frameworkd.conf
cp /etc/freesmartphone/oevents/old_rules.yaml /etc/freesmartphone/oevents/rules.yaml

now if you want to disable the shr phone apps without removing them comment all of the lines out in

/etc/X11/Xsession.d/89notifier and /etc/X11/Xsession.d/80ophonekitd

if you want the bind-home to ease upgrades add this line to fstab.

/media/card/bind-home /home/root none bind 0 0

You should now have a functional paroli on SHR setup. Once you have a working setup I would advise against doing opkg upgrades and only upgrade specific packages when needed.

[[Category:SHR]]

Navit

2009-09-09T09:04:04Z

Janvlug: Added link to SHR bug report.

{{Application|Navit}}

As described on the [http://navit.sourceforge.net/ Navit home page],

"'''Navit''' is a car navigation system with routing engine.

Its modular design is capable of using vector maps of various formats for routing and rendering of the displayed map. It's even possible to use multiple maps at a time.

The GTK+ or SDL user interfaces are designed to work well with touch screen displays. Points of Interest of various formats are displayed on the map.

The current vehicle position is either read from gpsd or directly from NMEA GPS sensors."

Some people say Navit is also a good choice for pedestrian and bicycle navigation.

[[Image:Navit-2241.png|thumb|Navit-r2241]]

== Acknowledgment ==

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

===Install Navit===
==== FSO (OM2008.x,SHR,...) ====

You can now simply add a feed from there : http://download.navit-project.org/navit/openmoko/svn/

Essentially, to enable this directory as [[Om_2008.8_Installer#How to add a Repository ?|feed]] and install or update navit do:
* Only for the first time:
echo src navit http://download.navit-project.org/navit/openmoko/svn > /etc/opkg/navit-feed.conf
opkg update

* Always:
opkg install navit

Navit will be auto-updated when you run opkg upgrade later

Navit might not be able to use gpsd at startup:
navit:plugin_load:can't load '/usr/lib/navit/vehicle/
libvehicle_gpsd.so', Error 'libgps.so.16: cannot open shared object
file: No such file or directory'
navit:vehicle_new:invalid type 'gpsd'

to solve this issue (necessary for SHR):

opkg install libgps17
ln -s /usr/lib/libgps.so.17 /usr/lib/libgps.so.16

====Debian====
Navit is now in Debian [http://packages.debian.org/source/testing/navit testing] and [http://packages.debian.org/source/unstable/navit unstable].

Add the following line to <tt>/etc/apt/sources.list</tt> with e.g. editor <tt>vi</tt> or <tt>nano</tt>:

deb http://ftp.de.debian.org/debian unstable main

Then update with apt-get:

apt-get update

The up-to-date source package is available through git at '''git://git.debian.org/git/collab-maint/navit.git''' ([http://git.debian.org/?p=collab-maint/navit.git;a=summary browse]).

===Set up the maps you want===

====The Easy Way====
Use [http://maps.navit-project.org/download/ Navit pre-processed OSM maps]. Navigate to the region you want, and click select to select it, select the region you want, then click download. [[Image:osmdownload.jpg|200px|thumb|Download OpenStreetMaps]]

If you just want the entire planet (as of this writing, ~1.8 GB), it's [http://maps.navit-project.org/planet.bin here].

[http://downloads.cloudmade.com/ CloudMade] also has up-to-date maps from OpenStreetMap by country (by state in the US).

====From the command line====
'''OpenStreetMap''' - follow directions at http://wiki.navit-project.org/index.php/OpenStreetMaps
* There are some pre-processed, up-to-date maps that can be grabbed with wget:

<pre>wget -O germany.bin http://maps.navit-project.org/api/map/?bbox=5.185546875,46.845703125,15.46875,55.634765625</pre>

You can put a shell script into <tt>/usr/local/bin/update-maps</tt>
#!/bin/sh
echo "Update OpenstreetMaps"
echo "---------------------"
echo " download and store OSM maps on /media/card/maps"
wget -O /media/card/germany.bin http://maps.navit-project.org/api/map/?bbox=5.185546875,46.845703125,15.46875,55.634765625
echo "update germany.bin finished"
You have to make the script executable with:
chmod u+x /usr/local/bin/update-maps
Then you can update with this script all your maps on the SD-card if you have internet connection:
update-maps

* Here's an example to get the maps for the area around Seattle, WA:
** Find the map coordinates using http://informationfreeway.org/?lat=47.520270037501454&lon=-122.20130713167327&zoom=9&layers=B000F000
** Download 4 regions from OpenStreetMaps ([[Navit#Script_to_download_OSM_maps|see below]] for a script to do this for you automatically for largish areas):

<pre>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</pre>

* A binary Navit map file needs to be created. The following uses osm2navit, and it's recommended that this command be used on something more powerful than the Neo:

<pre>cat *.osm | osm2navit --dedupe-ways mymap.bin</pre>

===Copy the map to the NEO===
To copy the map using scp (replace ''/directory'' as is appropriate in the following):
<pre>scp mymap.bin root@neo:/directory</pre>
If you copy the map <tt>germany.bin</tt> to the SD card on the Neo use e.g.
<pre>scp germany.bin root@neo:/media/card</pre>

Once it's somewhere on the NEO, Navit needs to know that it's there.
<pre>mkdir ~/.navit
cp /usr/share/navit/navit.xml ~/.navit/navit.xml
vi ~/.navit/navit.xml</pre>
In the navit.xml file, put the following into a new <mapset> section (and disable the default <mapset> just above - or else it will not work):
<pre><map type="binfile" enabled="yes" data="/directory" /></pre>
For example with a <tt>germany.bin</tt> on the SD-card you use:
<mapset enabled="yes">
<map type="binfile" enabled="yes" data="/media/card/germany.bin" />
</mapset>
or if you store all downloaded maps in the directory <tt>/media/card/maps</tt> then add the following lines to <tt>navit.xml</tt>.
<mapset enabled="yes">
<map type="binfile" enabled="yes" data="/media/card/maps/*.bin"/>
</mapset>
Note that the bin-file and the map set both have to be enabled.

Disable unused mapset sections by setting enabled to <tt>no</tt>, e.g. the pre-installed sample maps at line 370 in <tt>navit.xml</tt>.
<mapset enabled="no">
<xi:include href="$NAVIT_SHAREDIR/maps/*.xml"/>
</mapset>

* Run navit
** Start [[gllin]] (for GTA01)
** Start [[gpsd]] ( gpsd /tmp/nmeaNP )
** Start navit

* The version of osm2navit with which you build the maps should match the version of navit you have. If in doubt, build the maps on the Openmoko.

===Tips and Tricks===
====Center on Vehicle====
Navit supports a "always center on vehicle" option.

To activate this add
follow="3"
to the <tt>vehicle</tt> tag in navit.xml.
<vehicle name="Local GPS" profilename="car" enabled="yes" active="1" follow="3"
source="gpsd://localhost" gpsd_query="w+xj" color="#0000ff">
The "3" causes to give the gui time to do something between the repaints (drag the map or browse the menu). When its set to "1" navit does nothing more than repainting the map continuously.

==Routing==
[[Image:navit_main_menu.png|100px|thumb|Navit Main Menu]]
[[Image:navit_action_menu.png|100px|thumb|Navit Action Menu]]
The main menu has 4 submenus
* Action
* Settings
* Tools
* Route
Normally you would assume the entering a town can be found under the submenu Route, but Town is hidden under submenu Action. Route will provide the description of the route as text and a height profile of your trip. Tools was not working on 08/2009 Version of navit on SHR (see [[SHR User Manual]]).

===Select Destination===
[[Image:navit_select_country.png|100px|thumb|Select Country]]

When you click in the main menu on Action the Action menu appears with 4 subitems.
* Bookmarks of previous locations (stored in <tt>/home/root/.navit/destinations.txt</tt>
* a globe showing a location as destination,
* a vehicle that shows the current GPS position of the vehicle. If the freerunner receives no GPS signal the locations of the vehicle is set to 0.0.0N and 0.0.0E.
* Town is the action to enter a destination.
* Quit navit is the last action in this submenu.

Select the icon Town.

====Select Country====
[[Image:navit_country_selected.png|100px|thumb|Country Options]]
[[Image:navit_destination_details.png|100px|thumb|Enter Bookmark Details]]

Before you can search for City you have to select a Country. To do that, click on the icon in the left upper corner of the search field (could look like a white square with blue top-left quadrant).

Just type in the first letter of the country (e.g. "G") and Navit makes suggestions (e.g. Gabon, Germany).

====Enter Town====

When you have selected the country (e.g. Germany) the flag appears and you can select the town.
Then you can save the town as bookmark and enter more details like streets to the selected town.

The search is still a little buggy.

====Enter Street====
You can enter the street and streetnumber and save it as bookmark when you use the destination often.

====Bookmarks====
Navigation and planning of routes with Navit can be organized with bookmarks.
* set a bookmark as current position
* set a bookmark as destination
Then you can see the suggested route in blue on the map.

The GPS-location (if GPS-signal is available) will be highlighted with a small blue circle:
* a dot in the blue circle is indicating that your are not moving,
* an arrowhead is indicating the direction, when you are moving.
Then routing can start and in the map the route is highlighted.

====Screenshots in Navit Documentation====
The screenshots are made with <tt>gpe-scap</tt>, that can be installed by:
opkg install gpe-scap
if not installed already. Navigation through your installed application navit and login via ssh on your Freerunner
ssh -l root 192.168.0.202
assuming that your Freerunner has the IP 192.168.0.202.
Any time you want to make a screenshot just start via your desktop computer
gpe-scap
and save the screenshot to you freerunner.
Download the screenshot to your desktop computer with
desktop# sftp://root@192.168.0.202

== News ==
A deeper look into configuring Navit can be found in the [http://wiki.navit-project.org/index.php/Configuring_Navit Navit-Wiki].

=== Getting the display right ===

If using SHR the keyboard in country/town/street search mode does not fit on the street, make sure your gui configuration is set to the following line:

<gui type="internal" font_size="350"/>

The example line provided for freerunners hides some important icons. Namely, instead of typing your city name first, you will first have to click the button on the top left, to go into country search mode. Enter your country name, then the city name, in order to enable the search function. This requires your map data to be searchable.

You can start in fullscreen mode with fullscreen="1"

<gui type="internal" font_size="350" fullscreen="1"/>

If you want to enable "+" and "-" as Zoom-In and Zoom-Out buttons on the bottom of the map enable the button with the following xml-tags:
<osd enabled="yes" type="button" x="-96" y="-96" command="zoom_in()" src="zoom_in.xpm"/>
<osd enabled="yes" type="button" x="0" y="-96" command="zoom_out()" src="zoom_out.xpm"/>

=== Speech ===
Navit can speak if you install [http://espeak.sourceforge.net/ eSpeak] + [http://www.freebsoft.org/speechd speech-dispatcher] and updates your navit.xml file.
For adventurous people, one way to do this (in SHR starting <tt>navit</tt> did not work anymore after this procedure):

* mokoTTS aims to integrate these packages in OM:
http://projects.openmoko.org/projects/mokotts/

install espeak, dotconf, and then speech-dispatcher.
note: running 2008.8 updating from zecke's "testing" repo does not require "dotconf"

* 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.

'''Note: Package speech-dispatcher broke my audio after suspend with current SHR (2009-04-13, though the problem's not shr, but speech-dispatcher itself).''' See this [http://trac.shr-project.org/trac/ticket/494 bug report]. A solution is to disable starting of speech-dispatcher with:
update-rc.d -f speech-dispatcher remove
And then edit /usr/bin/navit, so that it starts speech-dispatcher before navit, and stops it afterwards. See http://lists.openmoko.org/nabble.html#nabble-td1088795

'''Alternatively''', you can make speech-dispatcher restart on resume, see http://trac.shr-project.org/trac/ticket/494

=== 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://api.openstreetmap.org/api/0.6/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, currLon, currLat, nextLon, nextLat))

currLon = nextLon
mapCount = mapCount + 1

currLat = nextLat

(minLat, maxLat, minLon, maxLon) = map(float, sys.argv[1:])
getOsms('map', minLat, maxLat, minLon, maxLon)
</pre>

<onlyinclude>
{{ApplicationBox|
Name=[[Navit]]|
Description=Navit is a car navigation system with routing engine.|
Screenshot=Screenshot-3.png|
Homepage=http://navit.sourceforge.net|
TestedOn=|
PackageName=
}}
</onlyinclude>

[[Category:GPS Applications]]

Navit

2009-09-09T08:52:56Z

Janvlug: added link to speech dispatcher and e-speak

{{Application|Navit}}

As described on the [http://navit.sourceforge.net/ Navit home page],

"'''Navit''' is a car navigation system with routing engine.

Its modular design is capable of using vector maps of various formats for routing and rendering of the displayed map. It's even possible to use multiple maps at a time.

The GTK+ or SDL user interfaces are designed to work well with touch screen displays. Points of Interest of various formats are displayed on the map.

The current vehicle position is either read from gpsd or directly from NMEA GPS sensors."

Some people say Navit is also a good choice for pedestrian and bicycle navigation.

[[Image:Navit-2241.png|thumb|Navit-r2241]]

== Acknowledgment ==

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

===Install Navit===
==== FSO (OM2008.x,SHR,...) ====

You can now simply add a feed from there : http://download.navit-project.org/navit/openmoko/svn/

Essentially, to enable this directory as [[Om_2008.8_Installer#How to add a Repository ?|feed]] and install or update navit do:
* Only for the first time:
echo src navit http://download.navit-project.org/navit/openmoko/svn > /etc/opkg/navit-feed.conf
opkg update

* Always:
opkg install navit

Navit will be auto-updated when you run opkg upgrade later

Navit might not be able to use gpsd at startup:
navit:plugin_load:can't load '/usr/lib/navit/vehicle/
libvehicle_gpsd.so', Error 'libgps.so.16: cannot open shared object
file: No such file or directory'
navit:vehicle_new:invalid type 'gpsd'

to solve this issue (necessary for SHR):

opkg install libgps17
ln -s /usr/lib/libgps.so.17 /usr/lib/libgps.so.16

====Debian====
Navit is now in Debian [http://packages.debian.org/source/testing/navit testing] and [http://packages.debian.org/source/unstable/navit unstable].

Add the following line to <tt>/etc/apt/sources.list</tt> with e.g. editor <tt>vi</tt> or <tt>nano</tt>:

deb http://ftp.de.debian.org/debian unstable main

Then update with apt-get:

apt-get update

The up-to-date source package is available through git at '''git://git.debian.org/git/collab-maint/navit.git''' ([http://git.debian.org/?p=collab-maint/navit.git;a=summary browse]).

===Set up the maps you want===

====The Easy Way====
Use [http://maps.navit-project.org/download/ Navit pre-processed OSM maps]. Navigate to the region you want, and click select to select it, select the region you want, then click download. [[Image:osmdownload.jpg|200px|thumb|Download OpenStreetMaps]]

If you just want the entire planet (as of this writing, ~1.8 GB), it's [http://maps.navit-project.org/planet.bin here].

[http://downloads.cloudmade.com/ CloudMade] also has up-to-date maps from OpenStreetMap by country (by state in the US).

====From the command line====
'''OpenStreetMap''' - follow directions at http://wiki.navit-project.org/index.php/OpenStreetMaps
* There are some pre-processed, up-to-date maps that can be grabbed with wget:

<pre>wget -O germany.bin http://maps.navit-project.org/api/map/?bbox=5.185546875,46.845703125,15.46875,55.634765625</pre>

You can put a shell script into <tt>/usr/local/bin/update-maps</tt>
#!/bin/sh
echo "Update OpenstreetMaps"
echo "---------------------"
echo " download and store OSM maps on /media/card/maps"
wget -O /media/card/germany.bin http://maps.navit-project.org/api/map/?bbox=5.185546875,46.845703125,15.46875,55.634765625
echo "update germany.bin finished"
You have to make the script executable with:
chmod u+x /usr/local/bin/update-maps
Then you can update with this script all your maps on the SD-card if you have internet connection:
update-maps

* Here's an example to get the maps for the area around Seattle, WA:
** Find the map coordinates using http://informationfreeway.org/?lat=47.520270037501454&lon=-122.20130713167327&zoom=9&layers=B000F000
** Download 4 regions from OpenStreetMaps ([[Navit#Script_to_download_OSM_maps|see below]] for a script to do this for you automatically for largish areas):

<pre>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</pre>

* A binary Navit map file needs to be created. The following uses osm2navit, and it's recommended that this command be used on something more powerful than the Neo:

<pre>cat *.osm | osm2navit --dedupe-ways mymap.bin</pre>

===Copy the map to the NEO===
To copy the map using scp (replace ''/directory'' as is appropriate in the following):
<pre>scp mymap.bin root@neo:/directory</pre>
If you copy the map <tt>germany.bin</tt> to the SD card on the Neo use e.g.
<pre>scp germany.bin root@neo:/media/card</pre>

Once it's somewhere on the NEO, Navit needs to know that it's there.
<pre>mkdir ~/.navit
cp /usr/share/navit/navit.xml ~/.navit/navit.xml
vi ~/.navit/navit.xml</pre>
In the navit.xml file, put the following into a new <mapset> section (and disable the default <mapset> just above - or else it will not work):
<pre><map type="binfile" enabled="yes" data="/directory" /></pre>
For example with a <tt>germany.bin</tt> on the SD-card you use:
<mapset enabled="yes">
<map type="binfile" enabled="yes" data="/media/card/germany.bin" />
</mapset>
or if you store all downloaded maps in the directory <tt>/media/card/maps</tt> then add the following lines to <tt>navit.xml</tt>.
<mapset enabled="yes">
<map type="binfile" enabled="yes" data="/media/card/maps/*.bin"/>
</mapset>
Note that the bin-file and the map set both have to be enabled.

Disable unused mapset sections by setting enabled to <tt>no</tt>, e.g. the pre-installed sample maps at line 370 in <tt>navit.xml</tt>.
<mapset enabled="no">
<xi:include href="$NAVIT_SHAREDIR/maps/*.xml"/>
</mapset>

* Run navit
** Start [[gllin]] (for GTA01)
** Start [[gpsd]] ( gpsd /tmp/nmeaNP )
** Start navit

* The version of osm2navit with which you build the maps should match the version of navit you have. If in doubt, build the maps on the Openmoko.

===Tips and Tricks===
====Center on Vehicle====
Navit supports a "always center on vehicle" option.

To activate this add
follow="3"
to the <tt>vehicle</tt> tag in navit.xml.
<vehicle name="Local GPS" profilename="car" enabled="yes" active="1" follow="3"
source="gpsd://localhost" gpsd_query="w+xj" color="#0000ff">
The "3" causes to give the gui time to do something between the repaints (drag the map or browse the menu). When its set to "1" navit does nothing more than repainting the map continuously.

==Routing==
[[Image:navit_main_menu.png|100px|thumb|Navit Main Menu]]
[[Image:navit_action_menu.png|100px|thumb|Navit Action Menu]]
The main menu has 4 submenus
* Action
* Settings
* Tools
* Route
Normally you would assume the entering a town can be found under the submenu Route, but Town is hidden under submenu Action. Route will provide the description of the route as text and a height profile of your trip. Tools was not working on 08/2009 Version of navit on SHR (see [[SHR User Manual]]).

===Select Destination===
[[Image:navit_select_country.png|100px|thumb|Select Country]]

When you click in the main menu on Action the Action menu appears with 4 subitems.
* Bookmarks of previous locations (stored in <tt>/home/root/.navit/destinations.txt</tt>
* a globe showing a location as destination,
* a vehicle that shows the current GPS position of the vehicle. If the freerunner receives no GPS signal the locations of the vehicle is set to 0.0.0N and 0.0.0E.
* Town is the action to enter a destination.
* Quit navit is the last action in this submenu.

Select the icon Town.

====Select Country====
[[Image:navit_country_selected.png|100px|thumb|Country Options]]
[[Image:navit_destination_details.png|100px|thumb|Enter Bookmark Details]]

Before you can search for City you have to select a Country. To do that, click on the icon in the left upper corner of the search field (could look like a white square with blue top-left quadrant).

Just type in the first letter of the country (e.g. "G") and Navit makes suggestions (e.g. Gabon, Germany).

====Enter Town====

When you have selected the country (e.g. Germany) the flag appears and you can select the town.
Then you can save the town as bookmark and enter more details like streets to the selected town.

The search is still a little buggy.

====Enter Street====
You can enter the street and streetnumber and save it as bookmark when you use the destination often.

====Bookmarks====
Navigation and planning of routes with Navit can be organized with bookmarks.
* set a bookmark as current position
* set a bookmark as destination
Then you can see the suggested route in blue on the map.

The GPS-location (if GPS-signal is available) will be highlighted with a small blue circle:
* a dot in the blue circle is indicating that your are not moving,
* an arrowhead is indicating the direction, when you are moving.
Then routing can start and in the map the route is highlighted.

====Screenshots in Navit Documentation====
The screenshots are made with <tt>gpe-scap</tt>, that can be installed by:
opkg install gpe-scap
if not installed already. Navigation through your installed application navit and login via ssh on your Freerunner
ssh -l root 192.168.0.202
assuming that your Freerunner has the IP 192.168.0.202.
Any time you want to make a screenshot just start via your desktop computer
gpe-scap
and save the screenshot to you freerunner.
Download the screenshot to your desktop computer with
desktop# sftp://root@192.168.0.202

== News ==
A deeper look into configuring Navit can be found in the [http://wiki.navit-project.org/index.php/Configuring_Navit Navit-Wiki].

=== Getting the display right ===

If using SHR the keyboard in country/town/street search mode does not fit on the street, make sure your gui configuration is set to the following line:

<gui type="internal" font_size="350"/>

The example line provided for freerunners hides some important icons. Namely, instead of typing your city name first, you will first have to click the button on the top left, to go into country search mode. Enter your country name, then the city name, in order to enable the search function. This requires your map data to be searchable.

You can start in fullscreen mode with fullscreen="1"

<gui type="internal" font_size="350" fullscreen="1"/>

If you want to enable "+" and "-" as Zoom-In and Zoom-Out buttons on the bottom of the map enable the button with the following xml-tags:
<osd enabled="yes" type="button" x="-96" y="-96" command="zoom_in()" src="zoom_in.xpm"/>
<osd enabled="yes" type="button" x="0" y="-96" command="zoom_out()" src="zoom_out.xpm"/>

=== Speech ===
Navit can speak if you install [http://espeak.sourceforge.net/ eSpeak] + [http://www.freebsoft.org/speechd speech-dispatcher] and updates your navit.xml file.
For adventurous people, one way to do this (in SHR starting <tt>navit</tt> did not work anymore after this procedure):

* mokoTTS aims to integrate these packages in OM:
http://projects.openmoko.org/projects/mokotts/

install espeak, dotconf, and then speech-dispatcher.
note: running 2008.8 updating from zecke's "testing" repo does not require "dotconf"

* 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.

'''Note: Package speech-dispatcher broke my audio after suspend with current SHR (2009-04-13, though the problem's not shr, but speech-dispatcher itself).''' A solution is to disable starting of speech-dispatcher with:
update-rc.d -f speech-dispatcher remove
And then edit /usr/bin/navit, so that it starts speech-dispatcher before navit, and stops it afterwards. See http://lists.openmoko.org/nabble.html#nabble-td1088795

'''Alternatively''', you can make speech-dispatcher restart on resume, see http://trac.shr-project.org/trac/ticket/494

=== 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://api.openstreetmap.org/api/0.6/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, currLon, currLat, nextLon, nextLat))

currLon = nextLon
mapCount = mapCount + 1

currLat = nextLat

(minLat, maxLat, minLon, maxLon) = map(float, sys.argv[1:])
getOsms('map', minLat, maxLat, minLon, maxLon)
</pre>

<onlyinclude>
{{ApplicationBox|
Name=[[Navit]]|
Description=Navit is a car navigation system with routing engine.|
Screenshot=Screenshot-3.png|
Homepage=http://navit.sourceforge.net|
TestedOn=|
PackageName=
}}
</onlyinclude>

[[Category:GPS Applications]]

SHR User Manual

2009-09-06T17:07:43Z

Janvlug: Added link to user experience

{{Languages|SHR User Manual}}
{| align="right"
| __TOC__
|}

==SHR Introduction==

Welcome to '''[[SHR]]''', a community driven distribution for (not only) Openmoko Neo phones.

{{Note|As SHR doesn't provide testing images at the moment this manual was based on unstable images available on the beginning of August 2009. The unstable images get changed very often - the download location changes, default applications change, bugs get hunted and fixed, meaning that some parts of this manual are already outdated.
Some users write their SHR experiences on their user page:
* [[User:Khiraly|Khiraly]]}}

'''SHR''' (Stable Hybrid Release) is here to provide you with Root FileSystem images that you can easily install onto your phone to use as a daily phone. There are many prepackaged programs available that can be installed upon demand by users, it can also be used by developers as a base image for customized and flavored distribution or release. SHR unstable is a testing environment before software get stabilized and it is the main testing ground for [[FSO]] releases. SHR testing images (currently not available) provide as much stability as possible for day-to-day usage.

SHR users, readers of this manual, please report improvements, discrepancies or missing features on this page to <tt>vanous @ penguin . cz</tt>. Thank you.

[http://shr-project.org SHR Project page]

==Installation==

===Getting SHR===

First, determine which model of phone you have, the GTA01(neo1973) or the GTA02(FreeRunner).

You need to download two files for your version as above, kernel and root filesystem. Depending whether you will be installing into the internal [[NAND memory]] or on [[µSD]] card, you need to either get .jffs2 file for nand or .tar.gz file for µSD.

At this point, there are no recent testing images so for the GTA02 Freerunner you need to download the images of unstable release from http://build.shr-project.org/shr-unstable/images/om-gta02/

- Get the latest kernel from the above linkpage. Starts with uImage-...

- Get the root filesystem, for nand: [http://build.shr-project.org/shr-unstable/images/om-gta02/lite-om-gta02.jffs2 lite-om-gta02.jffs2], (for µSD): [http://build.shr-project.org/shr-unstable/images/om-gta02/lite-om-gta02.tar.gz lite-om-gta02.tar.gz]

The image is marked as '''lite''' which can be upgraded to the full image by running

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

The 20090808-om-gta02 image doesn't have the <tt>opkg</tt> command, use <tt>opkg-cl</tt>. After an <tt>opkg-cl update</tt> and <tt>opkg-cl upgrade</tt> the command <tt>opkg</tt> works normally.

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

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

|-

| Media ||

* Vagalume
* Intone
||

|-

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

|-

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

|-
|}

===Installation on Flash===

In order to install your SHR distribution directly to your Freerunner Flash memory (NAND), you need to get the desired filesystem file ( <tt>.jffs2</tt> ) as described above and flash your device using the <tt>dfu-util</tt> tool.

Please visit [[Flashing the Neo FreeRunner]] for more details about flashing and see [[Dfu-util]] for detailed information about the dfu-util.

Command to flash the filesystem and the kernel

dfu-util -a rootfs -R -D shr-image-om-gta02.jffs2
dfu-util -a kernel -R -D uImage-om-gta02-latest.bin

===Installation on µSD Card===

Installing SHR on your µSD Card depends on the Bootloader you are using, ''uBoot'' or ''Qi''.

In simply words, difference between both systems resides on how you must prepare your µSD Card and files you use to fill them:

* If you use ''uBoot'', you need to create two partitions. First partition, not so big, in FAT16 where you have to place the kernel file (<tt>uImage-om-gta02-latest.bin</tt>) and second partition in ext2 or ext3 where you have to uncompress the filesystem file (<tt>shr-image-om-gta02.tar.gz</tt>).

* If you use ''Qi'', you only need an ext2 partition into your µSD Card where you uncompress the filesystem image file (<tt>shr-image-om-gta02.tar.gz</tt>). In this case Qi Bootloader is going to look for the kernel image into the <tt>/boot</tt> directory for file named <tt>uImage-GTA02.bin</tt> .

Please visit links below for detailed information and tips:
*For [[Booting from SD | uBoot]] and for [[Qi]].

===SHR version===

Should you ever later wonder what version of SHR you have actually installed, please run

cat /etc/shr-version

or check SHR Settings -> Other -> Image information

===Booting===
Press the power button until you feel a soft vibration to start the phone. The booting splash screen will appear. The first boot after a new installation always takes a bit longer. It is recommended to reboot after this first boot, to make sure all packages got initialized properly.

[[Image:Shr-boot-preview.png|200px|thumb|center|SHR Boot Splash screen]]

===Initial Setup===

[[Image:SHR-Setup-Language.png|200px|thumb|Initial setup]]
On the first boot, Setup is automatically initiated to walk the user through basic setup of the Enlightenment desktop environment. You are able to choose preferred language of the desktop environment, Illume SHR themed profile or select default menu (only one at the moment).

On the Add icon screen you can add icons for some application. If you add a terminal based application like mplayer, you will see an icon but no application running upon click, as it will run in the background.
Last screen allow settin up quick launch applications.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Setup-Profile.png|200px|thumb|Theme profile]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |

[[Image:SHR-Setup-Menu.png|200px|thumb|Menu]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |

[[Image:SHR-Setup-Add-Icons.png|200px|thumb|Add icons]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |

[[Image:SHR-Setup-Quick-Launch.png|200px|thumb|Quick launch]]

|}

==Running SHR==

===SIM Auth===

[[Image:SHR-SIM-Auth.png|200px|thumb|center|SIM Auth]]
SIM Pin is asked for upon start up.

===First look===
[[Image:SHR-First-Look.png|200px|thumb|Desktop screen]]
'''Illume desktop''' is the default home screen of the SHR desktop. Application files located in /usr/share/applications are displayed here. All applications are ran fullscreen and you can switch between them by using the Task switcher in the top shelf or by using the '''<''' left or right '''>''' arrows in the top shelf.

The Illume desktop can be easily customized - slide the top shelf down and tap the Settings icon (Wrench).

{{Note|TIP: for better access of the Settings icon, tap and hold the Settings icon, then drag it to the right.}}

'''Illume settings''' (the wrench) provides various options to alter the desktop environment. You can change sizes of elements, single or double click, wallpaper. To access all the various options, open Illume Settings and slide the visible icons to the left, to preview more options on the right hand side.

The little applets in the top shelf (for example Battery, GSM, Bluetooth etc.) are called '''shelf gadgets''' and you can configure whether they are visible (on the front part of the top shelf) or hidden (you can access them by sliding the top shelf) through Illume Settings -> Display -> Shelf gadget.

Some screens are not resized properly to fit the phone's display - for example the Wallpapper setting. This is a known bug already reported upstream.



===Phone applications===

Besides other software, SHR comes with 4 main phone applications: ''Dialer'', ''Contacts'', ''Messages'' and ''Phone log''.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Dialer.png|200px|thumb|Dialer]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Contacts.png|200px|thumb|Contacts]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Contacts-Options.png|200px|thumb|Contact options]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Contact-Add.png|200px|thumb|Add new contact]]
|}

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Mesages.png|200px|thumb|Messages]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |

[[Image:SHR-Messages-Options.png|200px|thumb|Messages options]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Message-View.png|200px|thumb|View message]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Message-View-chars.png|200px|thumb|Unicode support]]

|}

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Mesages-Options.png|200px|thumb|Message options]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |

[[Image:SHR-Phonelog.png|200px|thumb|Phonelog]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |

[[Image:SHR-Dialer-Active.png|200px|thumb|Active call]]

|}

Upon a missed call or an unread message there is a notifier that presents a screen with button to run Messages or Phonelog application, or you can simply close the Notifier with the Top Shelf cross.

===Post-Installation Script===
After flashing your phone you can do some modification mentioned below in this manual. The shell commands are collected in a [[SHR post-installation]] that you can transfer to your phone via ''scp'' and execute it with ''sh''.
Please go through the script and check if the applications to be installed is that want you want. If do not understand, what is going on in the script, proceed with this manual and select every step manually. If understand the script it might save you some time:
desktop#
scp SHRpostinstallation.sh root@192.168.0.202/home/root/SHRpostinstallation.sh
Start the shell script on your phone with:
neo# sh /home/root/SHRpostinstallation.sh

===First steps===

Right after installation and first boot you might want to do a few initial steps:
====Network Connection====
''Establish network connection'' and SSH into your phone. The <tt>root</tt> account uses no password by default. You can establish connection either via USB to your desktop and enable NAT or you can connect through Wifi. If you use USB, some setup is required on the desktop side, please read [[USB_Networking]]. For Wifi, you can use [[#Network manager|Network Manager]]

====GSM Network====
''Check if GSM is working correctly'' - observe the GSM gadget in the Top Shelve and see reported signal of your GSM operator. If GSM Gadget seems not be running, click ''Settings'' and later on ''Phone''. Move ''GSM Antenna'' to ''On''.

====Audio: Volume====
''Check and set call volume'' - this is handled by alsa state files in <tt>/usr/share/shr/scenarii/</tt> . To customize speaker volume edit <tt>/usr/share/shr/scenarii/gsmhandset.state</tt> and change <tt>control 4</tt>. Values between from 105 to 120 might be sufficient:

vi /usr/share/shr/scenarii/gsmhandset.state

control.4 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 127'
iface MIXER
name 'Speaker Playback Volume'
value.0 116
value.1 116
}

Should you want to alter more parameters be aware that each file is a set of value for the 94 parameters. Some of the important ones are:

Control 48: internal mic of the tel (set to 2 or 3)
Control 4 : internal speaker (set from 110 to 120)
Control 49: headset mic
Control 3 : headset speaker

====Set Regional Codes====
For the default SHR phone applications to be able to correctly parse incoming calls/messages and match them with your contacts, you will need to edit the following file:

vi /etc/phone-utils.conf

And change the file to reflect your country and area, example for Czech republic:

[local]
international_prefix = 00
national_prefix = 0
#for the cz
country_code = 42
area_code = 0

Another example:
5667
0-179-5667
00-49-179-5667
+49-179-5667
are equivalent numbers for German O2 service number ("-" for clarity only). So
international_prefix = 00
national_prefix = 0
country_code = 49 (without any leading "00" or "+"!)
for area code it seems wise to use "179" here, though that's the GSM-network code, not the code of your geographical area.
area_code = 179

====Initializing the opkg database====
''Initialize the opkg database'' in order to install some applications from SHR repositories or from other sources, for example [[http://opkg.org opkg.org]]. While still being online, you need to first run

opkg update

Searching in the opkg database can take a long time. You can speed things up by dumping the database into a file and grepping it through.

Do this only once or after every opkg update:

opkg list > packages.txt

Then you can search quickly for package name, for example for navit:

grep navit packages.txt

=====20090808 Image opkg startup=====
In the 20090808 Image, opkg update does not work you will get: -sh: opkg: not found.

There is a missing opkg symlink to opkg-cl. this is fixed in the SHR repositories.

To update:

opkg-cl update

And to upgrade

opkg-cl upgrade

opkg should work fine now.

====SwapSpace====
{{Main|SwapSpace}}
When the RAM is used up applications get killed. This is particularly bad while doing opkg upgrade. Therefore you might want to create a swap partition.

WARNING: Read [[SwapSpace]])

dd if=/dev/zero of=/swapfile bs=1024 count=65536

Add a line to fstab so next time you boot there will be swap

echo "/swapfile swap swap defaults 0 0">> /etc/fstab

Make swap

mkswap /swapfile

Make the swap file work now:

swapon /swapfile

====Changing root password====

SHR is shipped without root password (just press enter)

This is very dangerous if you connect using wifi, or USB. You need to activate the root password:

passwd

then type your selected password (2 times)

A much more convenient way might be to install your public-key to ~/.ssh/authorized_keys. For running
cmd | ssh root@neo anycommand
from your host this might be even mandatory, e.g if you want to pipe anything to the ssh.

====Locate lost phone by GPS====
To locate your phone in case of loss or theft by getting SMS with GPS location install '''sms-sentry''':

opkg install sms-sentry

Then, upon sending an SMS with the text sentry:location to your phone, the phone will turn on GPS, wait for a fix and send back an SMS with the current location.

[[openBmap]] and [[Cellhunter]] are projects with the objective to collect GPS location of GSM network cells. If this project is finished then SMS-sentry could send the a rough location just by identifying the current distances (strength of signal) to the available GSM network cells, even when the GPS satellites are not available (e.g. in a house).

===Localization===
[[Image:SHR-Illume-Settings-Languages.png|200px|thumb|Setting Language]]

You can change the language of the SHR desktop environment by using the Settings of Illume. For Example, for Czech language: in the Illume top shelf go to Wrench (Settings) -> Language -> Language Settings -> and choose: Čeština. If your language is not in the menu you can install by using opkg.

You can list all available languages by running:

opkg list | grep glibc-locale-

And install the language of your choice (for example czech):

opkg install glibc-locale-cs

After this, the Language Settings of Illume will offer Czech.

This will localize the Illume environment and will also set correct lang environment variable. If you wish to have translations for other applications, you need to install them again (presuming they are available):

This will install czech localisation for SHR phone applications, SHR Settings and TangoGps:

opkg install libframeworkd-phonegui-efl-locale-cs shr-settings-locale-cs tangogps-locale-cs

For localized terminal environment (ssh login) set lang variables set /etc/profile, example for Czech language:

export LANG=cs_CZ
export LC_ALL=cs_CZ

The Illume keyboard offers english dictionary correction by default. You can list all the dictionaries available for installation:

opkg list | grep illume-dic

If your language is not available and english is bothering you, you can set an empty dictionary:

echo "" > /usr/lib/enlightenment/modules/illume/dicts/None.dic

By using it, it will get filled by the words you use and after time will start helping and correcting your typing.

===Date and time===

The local timezone is automatically retrieved from the GSM network. Date and time are automatically set from GPS or Network. The easiest way of setting the time for the first time is to run TangoGps (GPS & Map icon) and obtaining GPS fix. Time will then be set automatically after several minutes.

Time can set time also manually.

Via SHR-Settings -> Date/time -> Set time

From linux based desktop:

ssh root@192.168.0.202 "date -u -s `date -u +%m%d%H%M%Y.%S`"

You can also set the hardware clock to the system time:

hwclock --systohc

It is possible to instruct framework on how to set the time and timezone in /etc/frameworkd.conf :

[otimed]
# a list of time/zone sources to use or NONE
timesources = GPS,NTP
zonesources = GSM
# use an ip address here, otherwise DNS resolution will block
ntpserver = 134.169.172.1

To disable automatic date/zone settings, simply create an empty [otimed] section in /etc/frameworkd.conf

===File transfer===

After you have established network connection, it is very easy to access and transfer files. The easiest solution is to use Konqueror or Nautilus on your desktop computer and type the following on your location bar. This should provide you with a view of the client's file system on Konqueror or Nautilus and you can easily drag-drop and copy-paste files.

sftp://root@192.168.0.202

===Data synchronization===
[[Image:SHR-PISI.png|200px|thumb|PISI contact synchronization]]
[[Image:SHR-PISI-dates.png|200px|thumb|PISI calendar synchronization]]

You can synchronize your contacts and appointments data with various sources. The sync can by done by program called [http://pisi.projects.openmoko.org/ PISI] . SIM contacts and calendar entries are currently possible to sync on SHR. You can also synchronize OPIMD contacts, these data are however so far no used in the current shr phone applications, but are used by for example Litephone.

For calendar install dates

opkg install dates

Supported Contacts data sources:
* SIM via DBUS (e.g. SHR)
* QTopia address book (e.g. OM 2008.12)
* LDAP (read only)
* VCF files (local / webdav)
* Google contacts
* OPIMD

Supported Calendar data sources:
* Google calendars
* ICalendar files (local / webdav)

To install PISI, run

<pre>
opkg install http://www.opkg.org/packages/1_python-vobject_0.8.1_armv4t.ipk \\
http://www.opkg.org/packages/0_python-webdav_0.1.2_armv4t.ipk python-sqlite3 \\
python-pygtk python-pygobject python-pycairo python-netserver python-netclient \\
http://www.opkg.org/packages/1_python-gdata_1.3.0_armv4t.ipk python-misc \\
http://www.opkg.org/packages/0_python-ldap_2.3.6_armv4t.ipk \\
http://www.opkg.org/packages/1_python-dateutil_1.4.1_armv4t.ipk \\
http://www.opkg.org/packages/openldap_2.3.43_armv4t.ipk \\
http://projects.openmoko.org/frs/download.php/891/pisi_0.4.5_armv4t.ipk
</pre>

Configuration example, .pisi/conf to sync contacts and calendar with google calendar and contacts with google mail:

[googleCalendar]
description=My Google Calendar
module=calendar_google
user=user@gmail.com
password=secret
calendarid=user@gmail.com

[pimlicodates]
description= Pimlico Dates
module=calendar_ics
path=/home/root/.evolution/calendar/local/system/calendar.ics
postprocess=killall e-calendar-factory

[googlecontacts]
description=Google Contacts Account
module=contacts_google
user=user@gmail.com
password=secret

[remoteIcs]
description= Remote ICS on Webdav
module=calendar_remoteics
url=http://webdav.davserver.net/private/pim/
file=remotecalendar.ics
username=<LOGIN>
password=<PASSWORD>

[shrsim]
description=SHR SIM Card Contacts
module=contacts_dbussim
max_simentries = 250
simentry_name_maxlength=18

Another way of importing contacts via Vcard file is possible with [gopher://gopher.fnordpol.de/9/data/DbusAccessScripts_0.0.0.tar.gz this] script written by [[User:Zem#DBus_Access_Scripts|Zem]].

===Reporting bugs===

SHR is a work in progress. If you experience issues, please report them back to SHR. With your report provide logs from

/var/log/ophonekitd
/var/log/frameworkd

To report a bug, please go to http://shr-project.org/trac/report

Check if the bug is already reported. If not, add a ticket, be as much precise as you can in the title and the description, in what circumstances the issue happened and so on.

==Car Navigation==
''Navit'' is a car navigation system with routing engine. It can calculate a route and do on screen and voice road navigation. Maps need to be downloaded beforehand, please check [http://wiki.navit-project.org/index.php/Main_Page#Maps Navit website]. You can get Openstreetmaps through [http://maps.navit-project.org/download/ Navit map extractor], after you download the map it needs to be specified in the .navit/navit.xml file.

===Add opkg feed===
To install <tt>navit</tt> as a car navigation system on your phone you have to add the feed for the installer <tt>opkg</tt>
http://download.navit-project.org/navit/openmoko/svn/
You can do this by:
echo src navit http://download.navit-project.org/navit/openmoko/svn > /etc/opkg/navit-feed.conf
opkg update

===Install Navit===
Install [[Navit]]: [[Image:navit1.png|200px|thumb|Navit on SHR with OpenStreetMaps]]
opkg install navit
Navit will be auto-updated when you run <tt>opkg upgrade</tt> later (sometimes not: workaround remove navit and reinstall the new one).

===Workaround libgps for Navit===
Navit on SHR has in the currently available version (08/2009) a <tt>libgps</tt> problem. You solve this by:
opkg install libgps17
ln -s /usr/lib/libgps.so.17 /usr/lib/libgps.so.16
(The whole GPS issue didn't work without that).

===Install Maps===
Use [http://maps.navit-project.org/download/ Navit pre-processed OSM maps]. With your browser on desktop:
* Navigate to the region you want,
* mark a rectangle for your map (e.g. for Germany) and click select the rectanglular map. [[Image:osmdownload.jpg|200px|thumb|Download OpenStreetMaps]]
* then click on download and save the file to <tt>country.bin</tt> (e.g. <tt>germany.bin</tt>) on your desktop computer.
* copy the file to on your phone. Because of the size of the maps you copy map to the Micro-SD card on your phone. Create a directory for the maps and copy the files from desktop to phone:
mkdir /media/card/maps
scp germany.bin root@192.168.0.202:/media/card/maps
* Create a directory <tt>.navit</tt> and copy the <tt>navit.xml</tt> to this directory:
mkdir /home/root/.navit
cp /usr/share/navit/navit.xml /home/root/.navit/navit.xml
* Add and enable the map for the application in navit by changing the lines (at approx line number 370)

<mapset enabled="yes">
<map type="binfile" enabled="yes" data="/media/card/maps/*.bin"/>
</mapset>
You can explicitly mention the downloaded maps in the mapset, e.g.:

<mapset enabled="yes">
<map type="binfile" enabled="yes" data="/media/card/maps/germany.bin"/>
<map type="binfile" enabled="no" data="/media/card/maps/france.bin"/>
</mapset>
Disable unused mapset sections by setting enabled to <tt>no</tt>, e.g. the pre-installed sample maps at line 370 in <tt>navit.xml</tt>.
<mapset enabled="no">
<xi:include href="$NAVIT_SHAREDIR/maps/*.xml"/>
</mapset>

===Start Navit===
Start <tt>Navit</tt> on your phone for your first test. For further configuration details see [http://wiki.openmoko.org/index.php?title=Navit OpenMoko Article for Navit] or the project website of [http://wiki.navit-project.org/index.php/Configuring_Navit Navit-Project].

===No sound after installing Navit===

Navit tends to depend on speech-dispatcher and after a suspend, the phone does not ring anymore for incoming calls or messages, it only vibrates. To correct this remove speech-dispatcher:

opkg remove -force-depends speech-dispatcher

==Bicycle Navigation with TangoGPS==
[[TangoGPS]] comes already installed with the SHR-Image. You can use TangoGPS for navigation too, for example with bicycle tour downloaded from http://www.bicirutas.net (see [http://www.bicirutas.net/de/rutas/deutschland/friederspitz/ bicirutas-Example] in Germany). You can also upload your favorite bicycle tour on the web to share the tour with others.

To make your life easier you can use
{{opkg.org|178|bicirutas}}, because this application looks for mtb routes in http://www.bicirutas.net (routes in Spain, Portugal, United Kingdom, France, Italy and Germany). It gets the current position from the gps system and downloads nearby routes. Then you can follow them with tangogps application. You need to be online for this feature. Otherwise you have to select your route before, download and transfer the route to your freerunner.

==SHR Settings==
[[Image:SHR-Settings-main.png|200px|thumb|SHR Settings]]

SHR Settings is the main setting application of SHR. It provides an easy way of setting up your phone to your liking - from phone related settings, to requesting resources in order to prevent screen dim or suspend (for example while using GPS).

Please refer to [http://wiki.openmoko.org/wiki/FSO_Resources#Automatic_way this wiki page] about a better way to manage preventing screen dim or suspend.

While some settings are persistent over reboots, others are not.

===Main Screen===
The main screen is divided into eight categories, which contain several modules. Every SHR Settings module has a specified task - for example controlling the GSM antenna power, setting the time etc.

===Settings: Phone===
Here you can set if the GSM antenna is on and if your phone number is shown when you call someone.

'''GSM'''
In GSM settings you can turn off and on GSM module. After turning off antenna, whole GSM modem is turned off.

To list available providers, click on Operators button. Scanning can take some time. After a while, a list of operators should pop up.

You can't connect to operators marked [forbidden]. After a connection failure, a message is displayed.

Selecting an operator from the list also changes modem registration mode to manual. It won't register to other network, even if some is available and has better signal strengh. To return to automatic mode, click "Automatic" button in operator list.

'''Call'''
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Phone.png|200px|thumb|Phone settings]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-List-providers.png|200px|thumb|List providers]]

|}

You can set if your phone number should be displayed to other party. You can either depend on network decision ("By network") or force it manually ("Manual")

'''SIM'''

Here you can view some informations about your SIM card and clean phone and messagebooks.

'''Others'''

'''Profile'''

Here you can select the current profile, which the device should use to determine ring tone etc.

'''Current profile'''

Here you can adjust properties of the currently used profile. Available settings: ring tone, ring volume, ring vibration, ring loop, ring length, message tone, message volume, message vibration, message loop, message length.

To change the ring tone, click the "Change" button.

To use your own ring tone, place it in /usr/share/sounds directory.

After selecting a sid tune as the ring tone, there are available controls to select tune number from the file.

This is changing settings in /etc/freesmartphone/opreferences/conf/phone/default.yaml

ring-volume # Ring Volume control 0 (mini) to ? maxi)
ring-length # min time for ringtone. Must be greater than the duration of you ringtone
ring-loop # define the number of loop of ringtone to play
ring-tone: "ringtone_ringnroll.ogg" # .ogg example
ring-tone: "Arkanoid_PSID.sid" # .sid example, use default tune
ring-tone: "Arkanoid_PSID.sid;tune=2" # .sid example, plays the second tune of that

If you like to test a .sid you can play it using this command on the FR:

gst-launch filesrc location=Arkanoid_PSID.sid ! siddec tune=2 ! alsasink

Note that it's a ! used and not a | to construct the gstreamer pipe command.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Profiles.png|200px|thumb|Profiles]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Profiles-Ringtones.png|200px|thumb|Ringtones]]

|}

===Settings: Connectivity===

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Connectivity.png |200px|thumb|Connectivity top]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Connectivity2.png |200px|thumb|Connectivity bottom]]
|}

'''WiFi'''

With the "WiFi radio" toggle you can set, if the wifi module is powered. WiFi radio has to be turned on before trying to connect to a WiFi network, unless you try to connect through Mokonnect which is capable of powering it up.

'''GPRS'''

To enter APN, login and password fields, just click on the actual value (default: "internet"). Keyboard will pop up.
If you don't know APN, login and passwork, ask your provider.}}

{{Note|You can also use Mokonnect to manage your GPRS connection}}

To connect to the GPRS network, just click the "Connect" button. Entered values will be saved after successful connection.

'''USB'''

With this toggle you can switch USB port between device (Neo to PC) or host (device to Neo) modes.

'''Bluetooth'''

To power up Bluetooth module, switch the "Bluetooth radio" toggle to "On". After that, the "Visibility" toggle should arrive - set it to "On" if you want your FR to be visible by other Bluetooth devices on scanning.

===Settings: GPS===

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-GPS.png |200px|thumb|center|GPS]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-GPS-Satelites.png |200px|thumb|GPS Satelite details]]
|}

'''GPS'''

By default, GPS is turned on only when requested (when you turn on TangoGPS, Navit, omgps or other GPS app). That state corresponds to "Auto" setting. After changing to "Manual", you can force set it to on or off.

'''GPS information'''

This page can be used to monitor GPS status. If some value isn't known, then "unknown" is displayed.

You can also view information about every visible satellite and check, which are used for getting a fix. To do that, click "Satellite details".

If you experience problems with GPS, turn it off, click "Remove AGPS data" and reboot your Neo.

===Settings: Date/time===

[[Image:SHR-Settings-Date-Time.png |200px|thumb|Date & Time]]

'''Time'''

Here you can view and set the time. By default, the time is just displayed, To adjust it, click on "Set time".

After finishing adjusting, click the "OK" button.

'''Date'''

This module displays the current date.

===Settings: Power===

'''Battery'''

This module displays informations about battery state - charge, voltage, remaining time etc. To update the data, click the "Update" button.

Here you can also force enable 500mA charging.

'''Display'''

With this slider you can easily set the backlight brightness.

{{Note|This setting isn't permanent over sessions. At boot backlight is set back to 100%.}}

'''Power'''

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Power.png |200px|thumb|Power]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Timeouts.png |200px|thumb|Timeouts]]
|}

Here you can turn on or off automatic dimming or suspend after idle timeout (see: Timeouts module)

'''Timeouts'''

Here you can set up values of idle timeouts used by the device. Timeouts are reached in this order: idle -> idle dim -> idle prelock -> lock -> suspend. Idle, idle prelock and lock aren't used by default in SHR at the moment. This setting changes parameters in /etc/frameworkd.conf :

[odeviced.idlenotifier]
suspend = 20
lock = 2
idle_prelock = 12
idle = 10
idle_dim = 20

===Settings: Services===

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Services.png |200px|thumb|center|Services]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Service-restart.png |200px|thumb|Services debug screen]]
|}

Here is listed every interesting script from /etc/init.d/ directory.

After clicking on one, you can either start, restart or stop the service and view the result.

===Settings: Others===

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Others.png |200px|thumb|Others]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Splash-Preview.png |200px|thumb|Splash preview]]
|}

'''Splash'''

With this selector you can select the theme used by shr-splash at boot and shutdown. After clicking "Preview", the selected boot image will be displayed for 5 seconds.

'''PIM'''

Module used by opimd developers. Doesn't have influence on behaviour of default SHR image.

Every opimd domain has different backends to store its data. The domain reads data from every backend and writes data to the default backend. So with the selector in shr-settings you can choose the backend that stores newly generated data, it doesn't copy or move existing data to a different backend.

'''Userspace backups'''

Here you can either archive or restore your files and configurations.

'''Image information'''

This module contains basic information about the installed image - name of buildhost, used revision, branch and time of build.

'''Theming'''
[[Image:SHR-Neo-Theme.png|200px|thumb|Neo theme]]
Find available themes by running

opkg list | grep theme-illume

install it by

opkg install e-wm-theme-illume-sixteen elementary-theme-sixteen

http://opkg.org has a very fast theme called nEo

opkg install http://www.opkg.org/packages/e-wm-theme-neo_0.2_armv4t.ipk
opkg install http://www.opkg.org/packages/elementary-theme-neo_0.2_armv4t.ipk
opkg install http://www.opkg.org/packages/etk-theme-neo_0.2_armv4t.ipk
opkg install -force-overwrite http://www.opkg.org/packages/libframeworkd-phonegui-efl-theme-neo_0.2_armv4t.ipk

If you also want the GTK+ Applications to fit in with the rest of the Systems look execute

opkg install http://www.opkg.org/packages/gtk-theme-neo_0.1_armv4t.ipk

For a completely monolithic look additionally execute

opkg install -force-overwrite http://www.opkg.org/packages/gpe-theme-neo_0.1_armv4t.ipk
opkg install http://www.opkg.org/packages/icon-theme-neo_0.2_armv4t.ipk

Please observe the command line output when installing these themes, since it will tell you how to activate the themes.

{{Note|some of the theme packages have to be reinstalled after an opkg upgrade.}}

Reverting back can be done by

opkg install e-wm-theme-illume-sixteen shr-theme-gtk-e17lookalike -force-reinstall
opkg install libframeworkd-phonegui-efl0 e-wm-theme-default etk-theme-shr shr-theme -force-reinstall

==FSO Resources==

FSO is in control of each device. These are called ''resources''. If the software wanting to use the device is capable of requesting this resource via <tt>d-bus</tt>, FSO will do this, otherwise you might need to power the device manually. After the requested resource is released, FSO will power it down. Manual resource request can be done through ''SHR Setting'' or you can use <tt>fsoraw</tt> command. (Using fsoraw is faster and better then running dbus commands)

opkg install fsoraw

Example of usage fsoraw:

fsoraw -r Display mokomaze

See [[FSO Resources]] for more details on using the following resources:

'''Wifi'''

Unless this resource is enabled you've no eth0 and wifi module is completely un-powered. Use the network manager to set up networks, Mokonnect will power Wifi up automatically when needed.

'''Bluetooth'''

You need to have this resource requested to have bluetooth module powered.

'''GPS'''

The fso-gpsd is a daemon waiting for gsmd connections, automatically powering the device on and off. When a connection exists, it powers up the GSM. In SHR Settings you can switch GPS completely off SHR Settings -> GPS -> Manual > Off

'''GSM'''

You need to have this resource requested to have GSM module powered.

'''Display'''

While this resource is requested the display won't be blanked and suspend is disabled.

'''CPU'''

Default rules.yaml checks for this resource to disable automatic suspend when it's requested. While this resource is kept suspend is disabled (but screen can be blanked).

'''Test'''

A test resource

==Network manager==

While there are several ways of networking - Wifi, USB, Bluetooth and Gprs - By default, USB networking is enabled in <tt>/etc/network/interfaces</tt>.

Enhanced configuration is possible through direct editing of /etc/network/interfaces or through Mokonnect.

The <tt>connmand</tt> daemon with Mokonnect are the recommended user level applications for setting up networking. At the moment, Mokonnect can manage USB, Wifi and Gprs connections, as well as routing and NAT. The Wifi device is not required to be manually turned on via SHR-Settings as Mokonnect will automatically enable the device when needed and disable it after use.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |
[[Image:SHR-Mokonnect.png|200px|thumb|Mokonnect]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |

[[Image:SHR-Mokonnect-Wifi.png|200px|thumb|Mokonnect Wifi]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |

[[Image:SHR-Mokonnect-Wifi-Scan.png|200px|thumb|Mokonnect Wifi Scan]]

|}

==Bluetooth==

Bluetooth can be used for several different applications - file transfer, networking, HIDD, music playing (A2DP), calling etc. In some occasions, the devices need to be authorized - paired. At the moment, support for some bluetooth functions is better than for others - it is possible to do all mentioned above with the notice that phone calls with bluetooth headset are always routed to the bluetooth even if it is not around, making it quite difficult to use.

Don't forget you need to turn the bluetooth radio on in SHR Settings -> Connectivity -> Bluetooth Radio: On, where you can also make the bluetooth device visible.

SHR uses bluez4 which is completely different from bluez3. The bluetoothd is taking care of most of the bluetooth now. Please see [[Manually using Bluetooth]] for detailed information about using bluetooth and also for a list of supported devices.

===OBEX file transfer===

There are several obex programs allowing file transfer, all in console at the moment. Obexpush installs obextool, and opd daemon:

opkg install obexpush

Default receiving path (editable in /etc/default/opd_args ) does not exist, so create it

mkdir /var/obexpush

Files are then received automatically, no notice, no confirmation... they just silently appear in /var/obexpush

To send some files, first scan for devices:

hcitool scan
Scanning ...
00:16:41:F5:A5:BC laptop

Then send it onto bt address found in the scan:

obextool push image.jpg 00:16:41:F5:A5:BC 10

===Connect Bluetooth keyboard===

hidd --search

===Pairing===

This comes from [[Manually_using_Bluetooth#Once_Again.2C_Bluetooth_Headset_on_Freerunner]]

Now, you must pair the bluetooth headset with your phone. Make sure the bluetooth chip is powered up (can be done through the Connectivity section in the SHR-Unstable settings manager) and that bluetoothd is running:
/etc/init.d/bluetooth start
Now, to actually pair the bluetooth headset, you will need the simple-agent script. If you already have it, excellent. If you, like me, do not, then you can get it here: http://dl.getdropbox.com/u/453116/simple-agent

Put it in /usr/bin/ and run ===chmod a+x /usr/bin/simple-agent===

Now put your headset into pairing mode and run

hcitool scan

Find your headset and use its address in the command

simple-agent hci0 XX:XX:XX:XX:XX:XX

If you give a third parameter (what it is doesn't matter) to simple-agent, it will disconnect then reconnect to the headset (reset pairing).

===GSM phone calls with bluetooth headset===

Your bluetooth headset device must be paired first.

====Configuring bluez====

Older SHR releases you need to uncomment <tt>SCORouting=PCM</tt> setting in <tt>[General]</tt> section of

/etc/bluetooth/audio.conf

like this:

# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
SCORouting=PCM

do not forget to restart bluetoothd after that.

/etc/init.d/bluetooth stop
/etc/init.d/bluetooth start

====Configuring FSO====

Now we must tell frameworkd that you have a bluetooth headset. Headset parameters should be set in

/etc/freesmartphone/opreferences/conf/phone/default.yaml

Parameters bt-headset-enabled and bt-headset-address (see opreferences/schema/phone.yaml for semantics).

You need to restart FSO for the changes to take effect.

/etc/init.d/frameworkd restart

example of my /etc/freesmartphone/opreferences/conf/phone/default.yaml:

message-length: 7
message-tone: notify_message.wav
message-vibration: 1
message-volume: 10
ring-loop: 1
ring-tone: ringtone_ringnroll.wav
ring-vibration: 1
ring-volume: 10
bt-headset-enabled: 1
bt-headset-address: 00:09:DD:31:92:98

====Re-Connecting the bt device====

You might need to get the bluetooth headset connected manually on the beginning and also after suspend:

mdbus -s org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_xx_xx_xx_xx_xx_xx org.bluez.Headset.Connect

where xx_xx_xx_xx_xx_xx is address of the device, for example:

mdbus -s org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_00_09_DD_31_92_98 org.bluez.Headset.Connect

Hopefully, your bluetooth headset now works. Good luck!

==System Customizing==

===Changing the splash screen===

list available splash screen themes

opkg list | grep splash-theme

and install one of the available themes

opkg install shr-splash-theme-dontpanic

Then go to SHR Settings -> Others -> Themes. Here you can preview installed themes and change the default one.

===Enable mouse cursor===

edit line 121 of /etc/X11/Xinit and erase -hide-cursor

ARGS="$ARGS -dpi ${DPI} -screen ${SCREEN_SIZE} -mouse tslib -root-ppm /usr/share/pixmaps/xsplash-vga.ppm vt1"

===Improve speed of Elementary applications===

Set the Elementary rendering engine used for Evas to x11-16 (Software X11 16bpp engine, may have bugs and will be lower quality, but faster):
echo -e "#!/bin/sh\n\nexport ELM_ENGINE=x11-16" > /etc/profile.d/set-elm-engine.sh

Additionally in the SHR-Unstable repositories there are theme packages optimized for 16bpp color. Both packages can be installed with the following command:

opkg install e-wm-theme-illume-sixteen elementary-theme-sixteen

You can then append the /etc/profile.d/set-elm-engine.sh with:

# Set Optimized theme
export ELM_THEME=sixteen

You can also then change Illume to use the sixteen theme by clicking the wrench->Look->Theme-illume-sixteen->OK. Then switch Illume to use the 16bpp Engine by clicking the wrench->Advanced(you will need to drag and slide the top menu)->Engine->Software_16->OK. This should give you a much faster interface without the low quality look the default SHR themes have at this lower color depth.

Read http://trac.enlightenment.org/e/wiki/Elementary

If you try to change Wallpaper or Theme and Illume keeps on crashing, it might be caused by the whole Illume running in Software_16 mode. Go to Illume Settings, slide the icon bar and select Advanced. There tap on Engine and select Software. After this, you can change your Wallpaper or Theme. Selecting Software_16 later on again will speed up the desktop's response (though causing it to be a bit uglier).

===Speedup of suspend and wake up===

I you are using Qi and installation on a µSD card, you can change the kernel parameter loglevel=1 1 in /boot/append-GTA02 . For u-boot and installation in nand just type

klogd -c 1

into the console. This saves you from 3 seconds worth of console output on every resume.

If you like the effect of this command and want it to be executed at every startup, you just have to log into your phone and type the following:

cat > /etc/init.d/resumespeedup << EOF
#!/bin/sh
/sbin/klogd -c 1
EOF
chmod +x /etc/init.d/resumespeedup
ln -s ../init.d/resumespeedup /etc/rc1.d/S06resumespeedup
ln -s ../init.d/resumespeedup /etc/rc2.d/S06resumespeedup
ln -s ../init.d/resumespeedup /etc/rc3.d/S06resumespeedup
ln -s ../init.d/resumespeedup /etc/rc4.d/S06resumespeedup
ln -s ../init.d/resumespeedup /etc/rc5.d/S06resumespeedup

===Opimd utils===

Opimd utils is a set of several testing scripts to play with the new opimd backends. It also provides opimd-messages program and mainly new opimd-notifier that is much better then the standard one.

opkg install opimd-utils

===opkg upgrade issues===

As '''opkg''' had some '''issues''' recently, installation might get broken due to that. You can fix it or prevent by using the following scripts

Safe update packages:

#!/bin/sh

opkg list_upgradable | awk '!/(kernel|Multiple)/ {print $1}' | \
while read line; do
echo "installing pack $line"
opkg install $line -force-reinstall
done

Force reinstall all installed packages

#!/bin/sh

opkg list_installed | awk '!/(kernel|Multiple)/ {print $1}' | \
while read line; do
echo "installing pack $line"
opkg install $line -force-reinstall
done

===Random errors===
No icons, no GSM functions etc. - this is mostly due to '''errors on your µSD''' card. Remove your card and fix it in card reader or by booting to another partition (nand) or by reboot and mount read only, then run fsck.

For reboot into nand and fix 1st partition of ext2 on your card

fsck.ext2 /dev/mmcblk0p1

===Replace dropbear with openssh===

Set password
passwd

Install ssh server (and sftp)
opkg install openssh-sshd openssh-sftp-server openssh-scp -force-depends

Remove dropbear and start openssh

screen
opkg remove dropbear -force-depends; /etc/init.d/sshd start

You will get disconnected from the ssh session, wait until keys get generated and log in again.
{{Note|'''Remove old SSH Key from <tt>.ssh/known_hosts</tt>:''' On your Linux box you will find a file <tt>known_host</tt> in the subdirectory <tt>.ssh/</tt> in you home directory. This contains a ssh key for the connection to your phone. If new keys are generated or if you flash your phone with SHR then you have to remove the line with <tt>openmoko</tt> or the IP-address of your phone from the file. Otherwise you might not be able to login in again until the former key is removed from <tt>known_hosts</tt>. If several distributions are alternately used on the same particular phone, it may be more convenient to copy the key files from one phone distribution to the rest. }}

===Video playback===

Install intone-video

opkg install elementary libsqlite3-0 http://www.opkg.org/packages/intone-video_0.11_arm.ipk

If intone complaints about missing libraries, please run
#!/bin/sh
cd /usr/lib
ls *ver-svn-02*|while read nombre
do
final="`echo $nombre | sed s/-ver-svn-02/-ver-pre-svn-01/`"
ln -s /usr/lib/$nombre /usr/lib/$final
done

On your desktop, encode your video:

mencoder video-file -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf scale=320:240,eq2=1.2:0.5:-.025,rotate=2 -oac mp3lame -lameopts br=64:cbr -o video-file-FR.avi

===Adding your phone to your hosts===

You can add your phone to your hosts file for a name resolving:

You can use the name <tt>neo</tt> if you added the host <tt>neo</tt> in <tt>/etc/hosts</tt> on your desktop computer (add the following line for host <tt>neo</tt> assuming that the IP-address of your phone is <tt>192.168.0.202</tt>.
echo "192.168.0.202 neo neo" >> /etc/hosts

You can then access your phone like this:

ssh root@neo

Which is shorter than this:

ssh root@192.168.0.202

==Installing Software==

You can use opkg for installing software packages or you can try SHR Installer from http://git.shr-project.org/git/?p=shr-installer.git;a=summary . It requires packagekitd

opkg install packagekitd

If you wan to use opkg after you used the installer, make sure packagekitd is not running

killall packagekitd

'''Cool applications'''

SHR comes with only a few preinstalled applications but its repository provides more cool stuff. Also, there are applications that are not in SHR repos at the moment but can still be installed. The following few examples are here just to spark your interest:

'''SHR Launcher'''

[[Image:Launcher.png|200px|thumb|SHR Launcher]]
Launcher is an elementary based alternative home screen application and event notifier for SHR. It displays current time, has a user tweak-able launcher with categories and features missed calls and messages applets.

opkg install libsqlite3-0 http://www.opkg.org/packages/launcher_0.30_arm.ipk

A newer version is announced at http://lists.openmoko.org/pipermail/community/2009-August/054207.html

If you don't see some icons, copy all icons from /usr/share/icons/shr/86x86/apps/* to /usr/share/pixmaps.

For '''PIM''' applications you can get dates for calendar, tasks for todos, neote for notes:

opkg install dates tasks

opkg install http://neote.googlecode.com/files/neote_0.2.0-r0_all.ipk

'''Paroli''' is available in SHR images, you can install it:

opkg install paroli

fix the conf files that the paroli installer messes with (might get fixed in the next couple of days.)

cp /etc/old_frameworkd.conf /etc/frameworkd.conf
cp /etc/freesmartphone/oevents/old_rules.yaml /etc/freesmartphone/oevents/rules.yaml

now if you want to disable the shr phone apps without removing them comment all of the lines out in

/etc/X11/Xsession.d/89notifier and /etc/X11/Xsession.d/80ophonekitd

if you want the bind-home to ease upgrades add this line to fstab.

/media/card/bind-home /home/root none bind 0 0

You should now have a functional paroli on SHR setup. Once you have a working setup I would advise against doing opkg upgrades and only upgrade specific packages when needed.

''GPE contacts'' saves the contacts in a SQLite database that can be synchronized with VCard files. Gpe-contacts don't allow you to dial directly via shr-dialer. Install gpe-contacts:

opkg install gpe-contacts

After installation you'll find to icons with ''MyVCard''. If you want to remove it, delete the file <tt>/usr/share/applications/edit-vcard.desktop</tt>

'''Litephone'''

[[Image:SHR-Litephone.png|200px|left|thumb|Litephone]]

Litephone is a new alternative set of phone applications written in Qt. In it's single application interface it provides basic phone functionality (contacts, calls, messages, phone log, settings). Its main advantage is that it uses opimd for storage of the user data.

opkg install http://pvtrace.com/litephone/libqtcore4_4.4.3-r3_armv4t.ipk
opkg install http://pvtrace.com/litephone/libqtxml4_4.4.3-r3_armv4t.ipk
opkg install http://pvtrace.com/litephone/libqtdbus4_4.4.3-r3_armv4t.ipk
opkg install http://pvtrace.com/litephone/libqtgui4_4.4.3-r3_armv4t.ipk
opkg install http://pvtrace.com/litephone/qt4-x11-free_4.4.3-r3_armv4t.ipk
opkg install http://pvtrace.com/litephone/litephone_0.0.1-r3_armv4t.ipk

'''Mokomaze''' is an eye-candy game using accelerators embedded in your device.

opkg install mokomaze

If you tweak the exec procedure in /usr/share/applications/mokomaze.desktop into this:
fsoraw -r Display mokomaze
the screen will not blank while playing.

'''[[Cellhunter]]''' is a game to collect information about mobile phone cells. This information can later be used to roughly determine your position without powering on the GPS chip. [http://78.47.116.33/~hole/cellhunter/ CellHunter homepage]

opkg install cellhunter

'''OMGps''' and '''TangoGPS''' are GPS application showing you your position on a map (Openstreetmap, Google maps etc.). You can track your position, save it and use later, save and view points of interest, images or measure your trip. OMGps allows you to overlay different maps on top of each other, set GPS into different modes (walking, car, flying). Maps are downloaded online and used even in offline.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |
[[Image:SHR-TangoGPS-OSM.png|200px|thumb|TangoGPS]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |
C
[[Image:SHR-OMGPS-GM.png |200px|thumb|OMGps]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |

[[Image:SHR-Mokomaze.png|200px|thumb|Mokomaze]]

|}

'''Screenshots''' can be made with ''gpe-scap'' (available by default in SHR full image). To take a screenshot, run gpe-scan from shell while connected in via ssh.

'''Literki''' is a full qwerty keyboard with configurable layout, always transparent, therefore applications don't need to redraw screens and popup is therefore very fast. The keys are big enough for everyday use with your fat fingers. To pop up the keyboard: slide your finger upwards from the bottom right corner. To hide the keyboard: slide your finger down on the keyboard. [http://www.opkg.org/package_232.html Opkg page]

opkg install http://pvtrace.com/literki_0.0.2-r3_armv4t.ipk

[[Category:SHR]]

SHR User Manual

2009-08-28T09:40:30Z

Janvlug: /* SHR Introduction */

{{Languages|SHR User Manual}}
{| align="right"
| __TOC__
|}

==SHR Introduction==

Welcome to '''[[SHR]]''', the world of community driven distribution for (not only) OpenmokoNeo phones.

{{Note|As SHR doesn't provide testing images at the moment this manual was based on unstable images available on the beginning of August 2009. The unstable images get changed very often - the download location changes, default applications change, bugs get hunted and fixed, meaning that some parts of this manual are already outdated.}}

'''SHR''' (Stable Hybrid Release) is here to provide you with Root FileSystem images that you can easily install onto your Freerunner to use as a daily phone. It's filled with prepackaged software that can be installed upon demand by users, it can also be used by developers as a base image for customized and flavored distribution or release. SHR unstable is a testing environment before software get stabilized and it is the main testing ground for [[FSO]] releases. SHR testing images (currently not available) provide as much stability as possible for day-to-day usage.

'''SHR''' has been evolving from a simple release of customized software into a full distribution. Therefore, in SHR you can choose from several different graphical toolkits (for example GTK or EFL), different phone managers (SHR or Zhone), web browsers and other programs.

The SHR Team is busy with system maintenance and software building so you can concentrate on programming, using and [http://shr-project.org/trac/report reporting bugs].

SHR users, readers of this manual, please report improvements, discrepancies or missing features on this page to <tt>vanous @ penguin . cz</tt>. Thank you.

[http://shr-project.org SHR Project page]

==SHR Specific==

At this point, there are some applications and procedures that are purely specific to SHR and would not run on another distribution. For example the phone applications (Dialer, Messages and Contacts) and SHR Settings depend heavily on the ophonekitd daemon.

As SHR is based on [[FSO]], basically any application using FSO has a chance to run, should all required libraries be available.

==Stability==

While many people use SHR as their daily phone, there are still occasional glitches and issues. This hurts the most when GSM stops working but this happens less and less. We wish you to have the best experiences with SHR.

==Installation==

===Getting SHR===

First, determine which model of phone you have, the GTA01(neo1973) or the GTA02(FreeRunner).

You need to download two files for your version as above, kernel and root filesystem. Depending whether you will be installing into the internal NAND memory or on µSD card, you need to either get .jffs2 file for nand or .tar.gz file for µSD.

At this point, there are no recent testing images so for the GTA02 Freerunner you need to download the images of unstable release from http://build.shr-project.org/shr-unstable/images/om-gta02/

- Get the latest kernel: [http://build.shr-project.org/shr-unstable/images/om-gta02/uImage-om-gta02-latest.bin uImage-om-gta02-latest.bin]

- Get the root filesystem, for nand: [http://build.shr-project.org/shr-unstable/images/om-gta02/full-om-gta02.jffs2 full-om-gta02.jffs2], (for µSD): [http://build.shr-project.org/shr-unstable/images/om-gta02/full-om-gta02.tar.gz full-om-gta02.tar.gz]

These are full images. You can also choose image with less packages, marked as '''lite''' which can be upgraded to the full image by running

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

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

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

|-

| Media ||

* Vagalume
* Intone
||
* pythm

|-

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

|-

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

|-
|}

===Installation on Flash===

In order to install your SHR distribution directly to your Freerunner Flash memory (NAND), you need to get the desired filesystem file ( <tt>.jffs2</tt> ) as described above and flash your device using the <tt>dfu-util</tt> tool.

Please visit [[Flashing the Neo FreeRunner]] for more details about flashing and see [[Dfu-util]] for detailed information about the dfu-util.

Command to flash the filesystem and the kernel

dfu-util -a rootfs -R -D shr-image-om-gta02.jffs2
dfu-util -a kernel -R -D uImage-om-gta02-latest.bin

===Installation on µSD Card===

Installing SHR on your µSD Card depends on the Bootloader you are using, ''uBoot'' or ''Qi''.

In simply words, difference between both systems resides on how you must prepare your µSD Card and files you use to fill them:

* If you use ''uBoot'', you need to create two partitions. First partition, not so big, in FAT16 where you have to place the kernel file (<tt>uImage-om-gta02-latest.bin</tt>) and second partition in ext2 or ext3 where you have to uncompress the filesystem file (<tt>shr-image-om-gta02.tar.gz</tt>).

* If you use ''Qi'', you only need an ext2 partition into your µSD Card where you uncompress the filesystem image file (<tt>shr-image-om-gta02.tar.gz</tt>). In this case Qi Bootloader is going to look for the kernel image into the <tt>/boot</tt> directory for file named <tt>uImage-GTA02.bin</tt> .

Please visit links below for detailed information and tips:

For [[Booting from SD | uBoot]] and for [[Qi]].

===SHR version===

Should you ever later wonder what version of SHR you have actually installed, please run

cat /etc/shr-version

or check SHR Settings -> Other -> Image information

===Booting===
Press the power button until you feel a soft vibration to start the FreeRunner. Booting splash screen will appear. First boot after new installation takes always a bit longer. Sometimes, it is recommended to reboot after this first boot, to make sure all packages got initialized properly.

[[Image:Shr-boot-preview.png|200px|thumb|center|SHR Boot Splash screen]]

===Initial Setup===

[[Image:SHR-Setup-Language.png|200px|thumb|Initial setup]]
On the first boot, Setup is automatically initiated to walk the user through basic setup of the Enlightenment desktop environment. You are able to choose preferred language of the desktop environment, Illume SHR themed profile or select default menu (only one at the moment).

On the Add icon screen you can add icons for some application. If you add a terminal based application like mplayer, you will see an icon but no application running upon click, as it will run in the background.
Last screen allow settin up quick launch applications.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Setup-Profile.png|200px|thumb|Theme profile]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |

[[Image:SHR-Setup-Menu.png|200px|thumb|Menu]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |

[[Image:SHR-Setup-Add-Icons.png|200px|thumb|Add icons]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |

[[Image:SHR-Setup-Quick-Launch.png|200px|thumb|Quick launch]]

|}

==Running SHR==

===SIM Auth===

[[Image:SHR-SIM-Auth.png|200px|thumb|center|SIM Auth]]
SIM Pin is asked for upon start up.

===First look===
[[Image:SHR-First-Look.png|200px|thumb|Desktop screen]]
'''Illume desktop''' is default home screen of the SHR desktop. Application files located in /usr/share/applications are displayed here. All applications are ran fullscreen and you can switch between them by using the Task switcher in the Top Shelve or by using the '''<''' left or right '''>''' arrows in the Top Shelve.

The Illume desktop can be easily customized - slide the Top Shelve down and tap the Settings icon (Wrench).

{{Note|TIP: for better access of the Settings icon, tap and hold the Settings icon, then drag it to the right.}}

'''Illume settings''' (the wrench) provides various options to alter the desktop environment. You can change sizes of elements, single or double click, wallpaper. To access all the various options, open Illume Settings and slide the visible icons to the left, to preview more options on the right hand side.

The little applets in the Top Shelve (for example Battery, GSM, Bluetooth etc.) are called '''Shelve gadgets''' and you can configure whether they are visible (on the front part of the top shelve) or hidden (you can access them by sliding the top shelve) through Illume Settings -> Display -> Shelve gadget.

Some screens are not resized properly to fit the Freerunner's display - for example the Wallpapper setting. This is a known bug already reported upstream.



===Phone applications===

Besides other software, SHR comes with 4 main phone applications: ''Dialer'', ''Contacts'', ''Messages'' and ''Phone log''.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Dialer.png|200px|thumb|Dialer]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Contacts.png|200px|thumb|Contacts]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Contacts-Options.png|200px|thumb|Contact options]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Contact-Add.png|200px|thumb|Add new contact]]
|}

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Mesages.png|200px|thumb|Messages]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |

[[Image:SHR-Messages-Options.png|200px|thumb|Messages options]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Message-View.png|200px|thumb|View message]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Message-View-chars.png|200px|thumb|Unicode support]]

|}

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:SHR-Mesages-Options.png|200px|thumb|Message options]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |

[[Image:SHR-Phonelog.png|200px|thumb|Phonelog]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |

[[Image:SHR-Dialer-Active.png|200px|thumb|Active call]]

|}

Upon a missed call or an unread message there is a Notifier that presents a screen with button to run Messages or Phonelog application, or you can simply close the Notifier with the Top Shelve cross.

===Post-Installation Script===
After flashing your Openmoko Freerunner you can do some modification mentioned below in this manual. The shell commands are collected in a [[SHR post-installation]] that you can transfer to your Freerunner via ''scp'' and execute it with ''sh''.
Please go through the script and check if the applications to be installed is that want you want. If do not understand, what is going on in the script, proceed with this manual and select every step manually. If understand the script it might save you some time:
desktop#
scp SHRpostinstallation.sh root@192.168.0.202/home/root/SHRpostinstallation.sh
Start the shell script on you Freerunner with:
neo# sh /home/root/SHRpostinstallation.sh

===First steps===

Right after installation and first boot you might want to do a few initial steps:
====Network Connection====
''Establish network connection'' and SSH into your Freerunner. The <tt>root</tt> account uses no password by default. You can establish connection either via USB to your desktop and enable NAT or you can connect through Wifi. If you use USB, some setup is required on the desktop side, please read [[USB_Networking]]. For Wifi, you can use [[#Network manager|Network Manager]]

====GSM Network====
''Check if GSM is working correctly'' - observe the GSM gadget in the Top Shelve and see reported signal of your GSM operator. If GSM Gadget seems not be running, click ''Settings'' and later on ''Phone''. Move ''GSM Antenna'' to ''On''.

====Audio: Volume====
''Check and set call volume'' - this is handled by alsa state files in <tt>/usr/share/shr/scenarii/</tt> . To customize speaker volume edit <tt>/usr/share/shr/scenarii/gsmhandset.state</tt> and change <tt>control 4</tt>. Values between from 105 to 120 might be sufficient:

vi /usr/share/shr/scenarii/gsmhandset.state

control.4 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 127'
iface MIXER
name 'Speaker Playback Volume'
value.0 116
value.1 116
}

Should you want to alter more parameters be aware that each file is a set of value for the 94 parameters. Some of the important ones are:

Control 48: internal mic of the tel (set to 2 or 3)
Control 4 : internal speaker (set from 110 to 120)
Control 49: headset mic
Control 3 : headset speaker

====Set Regional Codes====
For the default SHR phone applications to be able to correctly parse incoming calls/messages and match them with your contacts, you will need to edit the following file:

vi /etc/phone-utils.conf

And change the file to reflect your country and area, example for Czech republic:

[local]
international_prefix = 00
national_prefix = 0
#for the cz
country_code = 42
area_code = 0

Another example:
5667
0-179-5667
00-49-179-5667
+49-179-5667
are equivalent numbers for German O2 service number ("-" for clarity only). So
international_prefix = 00
national_prefix = 0
country_code = 49 (without any leading "00" or "+"!)
for area code it seems wise to use "179" here, though that's the GSM-network code, not the code of your geographical area.
area_code = 179

====Init opkg database====
''Initialize opkg database'' in order to install some applications from SHR repositories or from other sources, for example [[http://opkg.org opkg.org]]. While still being online, you need to first run

opkg update

Searching in the opkg database can take a long time. You can speed things up by dumping the database into a file and grepping it through.

Do this only once or after every opkg update:

opkg list > packages.txt

Then you can search quickly for package name, for example for navit:

grep navit packages.txt

====SwapSpace====
{{Main|SwapSpace}}
The Freerunner has only 128mb ram, when this is used up applications get killed. This is particularly bad while doing opkg upgrade.

WARNING: this mights kill your sd card, since there might be a lot of read/writes to the same spot. (all recent tests failed to harm SDcards by torture write tests, so probably you just shouldn't worry)

dd if=/dev/zero of=/swapfile bs=1024 count=65536

Add a line to fstab so next time you boot there will be swap

echo "/swapfile swap swap defaults 0 0">> /etc/fstab

Make swap

mkswap /swapfile

Make the swap file work now:

swapon /swapfile

====Changing root password====

SHR is shipped without root password (just press enter)

This is very dangerous if you connect using wifi, or USB. You need to activate the root password:

passwd

then type your selected password (2 times)

A much more convenient way might be to install your public-key to ~/.ssh/authorized_keys. For running
cmd | ssh root@neo anycommand
from your host this might be even mandatory, e.g if you want to pipe anything to the ssh.

====Locate lost phone by GPS====
To locate your freerunner in case of lost or theft by getting SMS with GPS location install '''sms-sentry''':

opkg install sms-sentry

Then, upon sending an sms with text sentry:location to your Freerunner, the phone will turn on GPS, wait for a fix and send back sms with current location.

[[openBmap]] and [[Cellhunter]] are projects with the objective to collect GPS location of GSM network cells. If this project is finished then sms-sentry could send the a rough GPS location just by identifying the current distances (strength of signal) to the available GSM network cells, even when the GPS satellites are not available (e.g. in a house).

===Localization===
[[Image:SHR-Illume-Settings-Languages.png|200px|thumb|Setting Language]]

You can change the language of the SHR desktop environment by using the Settings of Illume. For Example, for Czech language: in Illume Top Shelve go to Wrench (Settings) -> Language -> Language Settings -> and choose: Čeština. If your language is not in the menu you can install by using opkg.

You can list all available languages by running:

opkg list | grep glibc-locale-

And install the language of your choice (for example czech):

opkg install glibc-locale-cs

After this, the Language Settings of Illume will offer Czech.

This will localize the Illume environment and will also set correct lang environment variable. If you wish to have translations for other applications, you need to install them again (presuming they are available):

This will install czech localisation for SHR phone applications, SHR Settings and TangoGps:

opkg install libframeworkd-phonegui-efl-locale-cs shr-settings-locale-cs tangogps-locale-cs

For localized terminal environment (ssh login) set lang variables set /etc/profile, example for Czech language:

export LANG=cs_CZ
export LC_ALL=cs_CZ

The Illume keyboard offers english dictionary correction by default. You can list all the dictionaries available for installation:

opkg list | grep illume-dic

If your language is not available and english is bothering you, you can set an empty dictionary:

echo "" > /usr/lib/enlightenment/modules/illume/dicts/None.dic

By using it, it will get filled by the words you use and after time will start helping and correcting your typing.

===Date and time===

Timezone is automatically retrieved from the GSM network. Date and time are automatically set from GPS or Network. The easiest way of setting the time for the first time is to run TangoGps (GPS & Map icon) and obtaining GPS fix. Time will then be set automatically after several minutes.

Time can set time also manually.

Via SHR-Settings -> Date/time -> Set time

From linux based desktop:

ssh root@192.168.0.202 "date -u -s `date -u +%m%d%H%M%Y.%S`"

You can also set the hardware clock to the system time:

hwclock --systohc

It is possible to instruct framework on how to set the time and timezone in /etc/frameworkd.conf :

[otimed]
# a list of time/zone sources to use or NONE
timesources = GPS,NTP
zonesources = GSM
# use an ip address here, otherwise DNS resolution will block
ntpserver = 134.169.172.1

To disable automatic date/zone settings, simply create an empty [otimed] section in /etc/frameworkd.conf

===File transfer===

After you have established network connection, it is very easy to access and transfer files. The easiest solution is to use Konqueror or Nautilus on your desktop computer and type the following on your location bar. This should provide you with a view of the client's file system on Konqueror or Nautilus and you can easily drag-drop and copy-paste files.

sftp://root@192.168.0.202

===Data synchronization===
[[Image:SHR-PISI.png|200px|thumb|PISI Contact Sync]]
[[Image:SHR-PISI-dates.png|200px|thumb|PISI Calendar Sync]]

You can synchronize your contacts and appointments data with various sources. The sync can by done by program called [http://pisi.projects.openmoko.org/ PISI] . SIM contacts and calendar entries are currently possible to sync on SHR. You can also synchronize OPIMD contacts, these data are however so far no used in the current shr phone applications, but are used by for example Litephone.

For calendar install dates

opkg install dates

Supported Contacts data sources:
* SIM via DBUS (e.g. SHR)
* QTopia address book (e.g. OM 2008.12)
* LDAP (read only)
* VCF files (local / webdav)
* Google contacts
* OPIMD

Supported Calendar data sources:
* Google calendars
* ICalendar files (local / webdav)

To install PISI, run

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="left";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:80%; text-align:left " |

opkg install http://www.opkg.org/packages/1_python-vobject_0.8.1_armv4t.ipk http://www.opkg.org/packages/0_python-webdav_0.1.2_armv4t.ipk python-sqlite3 python-pygtk python-pygobject python-pycairo python-netserver python-netclient http://www.opkg.org/packages/1_python-gdata_1.3.0_armv4t.ipk python-misc http://www.opkg.org/packages/0_python-ldap_2.3.6_armv4t.ipk http://www.opkg.org/packages/1_python-dateutil_1.4.1_armv4t.ipk http://www.opkg.org/packages/openldap_2.3.43_armv4t.ipk http://projects.openmoko.org/frs/download.php/891/pisi_0.4.5_armv4t.ipk

|

|}

Configuration example, .pisi/conf to sync contacts and calendar with google calendar and contacts with google mail:

[googleCalendar]
description=My Google Calendar
module=calendar_google
user=user@gmail.com
password=secret
calendarid=user@gmail.com

[pimlicodates]
description= Pimlico Dates
module=calendar_ics
path=/home/root/.evolution/calendar/local/system/calendar.ics
postprocess=killall e-calendar-factory

[googlecontacts]
description=Google Contacts Account
module=contacts_google
user=user@gmail.com
password=secret

[remoteIcs]
description= Remote ICS on Webdav
module=calendar_remoteics
url=http://webdav.davserver.net/private/pim/
file=remotecalendar.ics
username=<LOGIN>
password=<PASSWORD>

[shrsim]
description=SHR SIM Card Contacts
module=contacts_dbussim
max_simentries = 250
simentry_name_maxlength=18

Another way of importing contacts via Vcard file is possible with [gopher://gopher.fnordpol.de/9/data/DbusAccessScripts_0.0.0.tar.gz this] script written by [[User:Zem#DBus_Access_Scripts|Zem]].

===Reporting bugs===

SHR is a work in progress. Should you experience issues, please report them back to SHR. With your report provide logs from

/var/log/ophonekitd
/var/log/frameworkd

To report a bug, please go to http://shr-project.org/trac/report

Check if the bug is already reported. If no, add a ticket, be as much precise as you can in the title and the description, in what circumstances the issue happened and so on.

==Car Navigation==
''Navit'' is a car navigation system with routing engine. It can calculate a route and do on screen and voice road navigation. Maps need to be downloaded beforehand, please check [http://wiki.navit-project.org/index.php/Main_Page#Maps Navit website]. You can get Openstreetmaps through [http://maps.navit-project.org/download/ Navit map extractor], after you download the map it needs to be specified in the .navit/navit.xml file.

===Add opkg feed===
To install <tt>navit</tt> as a car navigation system on your freerunner you have to add the feed for the installer <tt>opkg</tt>
http://download.navit-project.org/navit/openmoko/svn/
You can do this by:
echo src navit http://download.navit-project.org/navit/openmoko/svn > /etc/opkg/navit-feed.conf
opkg update

===Install Navit===
Install [[Navit]]: [[Image:navit1.png|200px|thumb|Navit on SHR with OpenStreetMaps]]
opkg install navit
Navit will be auto-updated when you run <tt>opkg upgrade</tt> later.

===Workaround libgps for Navit===
Navit on SHR has in the currently available version (08/2009) a <tt>libgps</tt> problem. You solve this by:
opkg install libgps17
ln -s /usr/lib/libgps.so.17 /usr/lib/libgps.so.16

===Install Maps===
Use [http://maps.navit-project.org/download/ Navit pre-processed OSM maps]. With your browser on desktop:
* Navigate to the region you want,
* mark a rectangle for your map (e.g. for Germany) and click select the rectanglular map. [[Image:osmdownload.jpg|200px|thumb|Download OpenStreetMaps]]
* then click on download and save the file to <tt>country.bin</tt> (e.g. <tt>germany.bin</tt>) on your desktop computer.
* copy the file to on your freerunner. Because of the size of the maps you copy map to the Micro-SD card on your freerunner. Create a directory for the maps and copy the files from desktop to freerunner:
mkdir /media/card/maps
scp germany.bin root@192.168.0.202:/media/card/maps
* Create a directory <tt>.navit</tt> and copy the <tt>navit.xml</tt> to this directory:
mkdir /home/root/.navit
cp /usr/share/navit/navit.xml /home/root/.navit/navit.xml
* Add and enable the map for the application in navit by changing the lines (at approx line number 370)

<mapset enabled="yes">
<map type="binfile" enabled="yes" data="/media/card/maps/*.bin"/>
</mapset>
You can explicitly mention the downloaded maps in the mapset, e.g.:

<mapset enabled="yes">
<map type="binfile" enabled="yes" data="/media/card/maps/germany.bin"/>
<map type="binfile" enabled="no" data="/media/card/maps/france.bin"/>
</mapset>
Disable unused mapset sections by setting enabled to <tt>no</tt>, e.g. the pre-installed sample maps at line 370 in <tt>navit.xml</tt>.
<mapset enabled="no">
<xi:include href="$NAVIT_SHAREDIR/maps/*.xml"/>
</mapset>

===Start Navit===
Start <tt>Navit</tt> on your Freerunner for your first test. For further configuration details see [http://wiki.openmoko.org/index.php?title=Navit OpenMoko Article for Navit] or the project website of [http://wiki.navit-project.org/index.php/Configuring_Navit Navit-Project].

===No sound after installing Navit===

Navit tends to depend on speech-dispatcher and after a suspend, the freerunner does not ring anymore for incoming calls or messages, it only vibrates. To correct this remove speech-dispatcher:

opkg remove -force-depends speech-dispatcher

==SHR Settings==
[[Image:SHR-Settings-main.png|200px|thumb|SHR Settings]]

SHR Settings is the main setting application of SHR. In the background it uses [[FSO]] specific dbus calls as well as low level commands. The graphical interface is Elementary-Python based. It provides an easy way of setting up your phone to your liking - from phone related settings, to requesting resources in order to prevent screen dim or suspend (for example while using GPS).

Please refer to [http://wiki.openmoko.org/wiki/FSO_Resources#Automatic_way this wiki page] about a better way to manage preventing screen dim or suspend.

While some settings are persistent over reboots, other are not.

===Main Screen===
Main screen is divided into few categories, which contain modules. Every SHR Settings module has specified task - control GSM antenna power, set actual time etc.

===Settings: Phone===
Here you can check if the GSM antenna is on and if your phone number is shown when you call someone.

'''GSM'''
In GSM settings you can turn off and on GSM module. After turning off antenna, whole GSM modem is turned off.

To list available providers, click on Operators button. Scanning can take some time. After while, list of operators should pop up.

You can't connect to operators marked [forbidden]. After failed connect, message is displayed.

Selecting operator from list also changes modem registration mode to manual. It won't register to other network, even if some is available and has better signal strengh. To return to automatic mode, click "Automatic" button in operator list.

'''Call'''
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Phone.png|200px|thumb|Phone settings]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-List-providers.png|200px|thumb|List providers]]

|}

You can set if your phone number should be displayed to other party. You can either depend on network decision ("By network") or force it manually ("Manual")

'''SIM'''

Here you can view some informations about your SIM card and clean phone and messagebooks.

'''Others'''

'''Profile'''

Here you can select current profile, which device should use to determine ring tone etc.

'''Current profile'''

Here you can adjust properties of currently used profile. Available settings: ring tone, ring volume, ring vibration, ring loop, ring length, message tone, message volume, message vibration, message loop, message length.

To change ring tone, click on "Change" button.

To use your own ring tone, place it in /usr/share/sounds directory.

After selecting sid tune as ring tone, there are available controls to select tune number from file.

This is changing settings in /etc/freesmartphone/opreferences/conf/phone/default.yaml

ring-volume # Ring Volume control 0 (mini) to ? maxi)
ring-length # min time for ringtone. Must be greater than the duration of you ringtone
ring-loop # define the number of loop of ringtone to play
ring-tone: "ringtone_ringnroll.ogg" # .ogg example
ring-tone: "Arkanoid_PSID.sid" # .sid example, use default tune
ring-tone: "Arkanoid_PSID.sid;tune=2" # .sid example, plays the second tune of that

If you like to test a .sid you can play it using this command on the FR:

gst-launch filesrc location=Arkanoid_PSID.sid ! siddec tune=2 ! alsasink

Note that it's a ! used and not a | to construct the gstreamer pipe command.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Profiles.png|200px|thumb|Profiles]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Profiles-Ringtones.png|200px|thumb|Ringtones]]

|}

===Settings: Connectivity===

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Connectivity.png |200px|thumb|Connectivity top]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Connectivity2.png |200px|thumb|Connectivity bottom]]
|}

'''WiFi'''

With "WiFi radio" toggle you can set, if wifi module should be powered. WiFi radio has to be turned on before trying to connect to WiFi network, unless you try to connect through Mokonnect which is capable of powering it up.

'''GPRS'''

To enter APN, login and password fields, just click on actual value (default: "internet"). Keyboard will pop up.
If you don't know APN, login and passwork, ask your provider.}}

{{Note|You can also use Mokonnect to manage your Gprs connection}}

To connect to GPRS network, just click "Connect" button. Entered values will be saved after successful connection.

'''USB'''

With this toggle you can switch USB port between device (Neo to PC) or host (device to Neo) modes.

'''Bluetooth'''

To power up Bluetooth module, swith "Bluetooth radio" toggle to "On". After that, "Visibility" toggle should arrive - set it to "On" if you want your FR to be visible by other Bluetooth devices on scanning.

===Settings: GPS===

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-GPS.png |200px|thumb|center|GPS]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-GPS-Satelites.png |200px|thumb|GPS Satelite details]]
|}

'''GPS'''

By default, GPS is turned on only when requested (when you turn on TangoGPS, Navit, omgps or other GPS app). That state corresponds to "Auto" setting. After changing to "Manual", you can force set it to on or off.

'''GPS information'''

This page can be used to monitor GPS status. If some value isn't known, then "unknown" is displayed.

You can also view information about every visible satellite and check, which are used for getting fix. To do that, just click "Satellite details".

If you experience problems with GPS, turn it off, click "Remove AGPS data" and reboot your Neo.

===Settings: Date/time===

[[Image:SHR-Settings-Date-Time.png |200px|thumb|Date & Time]]

'''Time'''

Here you can view and set actual time. By default, time is just displayed, To adjust it, click on "Set time".

After finishing adjusting, click "OK" button.

'''Date'''

This module displays current date.

===Settings: Power===

'''Battery'''

This module displays informations about battery state - charge, voltage, remaining time etc. To update data, click "Update" button.

Here you also force enable 500mA charging.

'''Display'''

With this slider you can easily tweak backlight power.

{{Note|This setting isn't permanent over sessions. At boot backlight is set back to 100%.}}

'''Power'''

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Power.png |200px|thumb|Power]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Timeouts.png |200px|thumb|Timeouts]]
|}

Here you can turn on or off automatic dimming or suspend after idle timeout (see: Timeouts module)

'''Timeouts'''

Here you can set up values of idle timeouts used by device. Timeouts are reached in this order: idle -> idle dim -> idle prelock -> lock -> suspend. Idle, idle prelock and lock aren't used by default in SHR at the moment. This setting changes parameters in /etc/frameworkd.conf :

[odeviced.idlenotifier]
suspend = 20
lock = 2
idle_prelock = 12
idle = 10
idle_dim = 20

===Settings: Services===

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Services.png |200px|thumb|center|Services]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Service-restart.png |200px|thumb|Services debug screen]]
|}

Here is listed every interesting script from /etc/init.d/ directory.

After clicking on some, you can either start, restart or stop service and view result.

===Settings: Others===

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Others.png |200px|thumb|Others]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Splash-Preview.png |200px|thumb|Splash preview]]
|}

'''Splash'''

With this selector you can select theme used by shr-splash at boot and shutdown. After clicking "Preview", selected boot image will be displayed for 5 seconds.

'''PIM'''

Module used by opimd developers. Doesn't have influence on behaviour of default SHR image.

Every opimd domain has different backends to store it's data. The domain reads data from every backend and writes data to the default backend. So with the selector in shr-settings you can choose the backend that stores newly generated data, it doesn't copy or move existing data to a different backend.

'''Userspace backups'''

Here you can either archive or restore your files and configurations.

'''Image information'''

This module contains basic information about installed image - name of buildhost, used revision, branch and time of build.

'''Theming'''
[[Image:SHR-Neo-Theme.png|200px|thumb|Neo theme]]
Find available themes by running

opkg list | grep theme-illume

install it by

opkg install e-wm-theme-illume-sixteen elementary-theme-sixteen

http://opkg.org has a very fast theme called nEo

opkg install http://www.opkg.org/packages/e-wm-theme-neo_0.2_armv4t.ipk
opkg install http://www.opkg.org/packages/elementary-theme-neo_0.2_armv4t.ipk
opkg install http://www.opkg.org/packages/etk-theme-neo_0.2_armv4t.ipk
opkg install -force-overwrite http://www.opkg.org/packages/libframeworkd-phonegui-efl-theme-neo_0.2_armv4t.ipk

If you also want the GTK+ Applications to fit in with the rest of the Systems look execute

opkg install http://www.opkg.org/packages/gtk-theme-neo_0.1_armv4t.ipk

For a completely monolithic look additionally execute

opkg install -force-overwrite http://www.opkg.org/packages/gpe-theme-neo_0.1_armv4t.ipk
opkg install http://www.opkg.org/packages/icon-theme-neo_0.2_armv4t.ipk

Please observe the command line output when installing these themes, since it will tell you how to activate the themes.

{{Note|some of the theme packages have to be reinstalled after an opkg upgrade.}}

Reverting back can be done by

opkg install e-wm-theme-illume-sixteen shr-theme-gtk-e17lookalike -force-reinstall
opkg install libframeworkd-phonegui-efl0 e-wm-theme-default etk-theme-shr shr-theme -force-reinstall

==FSO Resources==

FSO is in control of each device. These are called ''resources''. If the software wanting to use the device is capable of requesting this resource via <tt>d-bus</tt>, FSO will do this, otherwise you might need to power the device manually. After the requested resource is released, FSO will power it down. Manual resource request can be done through ''SHR Setting'' or you can use <tt>fsoraw</tt> command. (Using fsoraw is faster and better then running dbus commands)

opkg install fsoraw

Example of usage fsoraw:

fsoraw -r Display mokomaze

See [[FSO Resources]] for more details on using the following resources:

'''Wifi'''

Unless this resource is enabled you've no eth0 and wifi module is completely un-powered. Use the network manager to set up networks, Mokonnect will power Wifi up automatically when needed.

'''Bluetooth'''

You need to have this resource requested to have bluetooth module powered.

'''GPS'''

The fso-gpsd is a daemon waiting for gsmd connections, automatically powering the device on and off. When a connection exists, it powers up the GSM. In SHR Settings you can switch GPS completely off SHR Settings -> GPS -> Manual > Off

'''GSM'''

You need to have this resource requested to have GSM module powered.

'''Display'''

While this resource is requested the display won't be blanked and suspend is disabled.

'''CPU'''

Default rules.yaml checks for this resource to disable automatic suspend when it's requested. While this resource is kept suspend is disabled (but screen can be blanked).

'''Test'''

A test resource

==Network manager==

While there are several ways of networking - Wifi, USB, Bluetooth and Gprs - By default, USB networking is enabled in <tt>/etc/network/interfaces</tt>.

Enhanced configuration is possible through direct editing of /etc/network/interfaces or through Mokonnect.

The <tt>connmand</tt> daemon with Mokonnect are the recommended user level applications for setting up networking. At the moment, Mokonnect can manage USB, Wifi and Gprs connections, as well as routing and NAT. Wifi device is not required to be manually turned on via SHR-Settings as Mokonnect will automatically enable the device when needed and disable after use.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |
[[Image:SHR-Mokonnect.png|200px|thumb|Mokonnect]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |

[[Image:SHR-Mokonnect-Wifi.png|200px|thumb|Mokonnect Wifi]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |

[[Image:SHR-Mokonnect-Wifi-Scan.png|200px|thumb|Mokonnect Wifi Scan]]

|}

==Bluetooth==

Bluetooth can be used for several different applications - file transfer, networking, HIDD, music playing (A2DP), calling etc. In some occasions, the devices need to be authorized - paired. At the moment, support for some bluetooth functions is better then for others - it is possible to do all mentioned above with the notice that phone calls with bluetooth headset are always routed to the bluetooth even if it is not around, making it quite difficult to use.

Don't forget you need to turn the bluetooth radio on in SHR Settings -> Connectivity -> Bluetooth Radio: On, where you can also make the bluetooth device visible.

SHR user bluez4 which completely different from bluez3. The bluetoothd is taking care of most of the bluetooth now. Please see [[Manually using Bluetooth]] for detailed information about using bluetooth and also for list of supported devices.

===OBEX file transfer===

There are several obex programs allowing file transfer, all in console at the moment. Obexpush installs obextool, and opd daemon:

opkg install obexpush

Default receiving path (editable in /etc/default/opd_args ) doesn exist, so create it

mkdir /var/obexpush

Files are then received automatically, no notice, no confirmation... they just silently appear in /var/obexpush

To send some files, first scan for devices:

hcitool scan
Scanning ...
00:16:41:F5:A5:BC laptop

Then send it onto bt address found in the scan:

obextool push image.jpg 00:16:41:F5:A5:BC 10

===Connect Bluetooth keyboard===

hidd --search

===Pairing===

This comes from [[Manually_using_Bluetooth#Once_Again.2C_Bluetooth_Headset_on_Freerunner]]

Now, you must pair the bluetooth headset with your Freerunner. Make sure the bluetooth chip is powered up (can be done through the Connectivity section in the SHR-Unstable settings manager) and that bluetoothd is running:
/etc/init.d/bluetooth start
Now, to actually pair the bluetooth headset, you will need the simple-agent script. If you already have it, excellent. If you, like me, do not, then you can get it here: http://dl.getdropbox.com/u/453116/simple-agent

Put it in /usr/bin/ and run ===chmod a+x /usr/bin/simple-agent===

Now put your headset into pairing mode and run

hcitool scan

Find your headset and use its address in the command

simple-agent hci0 XX:XX:XX:XX:XX:XX

If you give a third parameter (what it is doesn't matter) to simple-agent, it will disconnect then reconnect to the headset (reset pairing).

===GSM phone calls with bluetooth headset===

Your bluetooth headset device must be paired first.

====Configuring bluez====

Older SHR releases you need to uncomment <tt>SCORouting=PCM</tt> setting in <tt>[General]</tt> section of

/etc/bluetooth/audio.conf

like this:

# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
SCORouting=PCM

do not forget to restart bluetoothd after that.

/etc/init.d/bluetooth stop
/etc/init.d/bluetooth start

====Configuring FSO====

Now we must tell frameworkd that you have a bluetooth headset. Headset parameters should be set in

/etc/freesmartphone/opreferences/conf/phone/default.yaml

Parameters bt-headset-enabled and bt-headset-address (see opreferences/schema/phone.yaml for semantics).

You need to restart FSO for the changes to take effect.

/etc/init.d/frameworkd restart

example of my /etc/freesmartphone/opreferences/conf/phone/default.yaml:

message-length: 7
message-tone: notify_message.wav
message-vibration: 1
message-volume: 10
ring-loop: 1
ring-tone: ringtone_ringnroll.wav
ring-vibration: 1
ring-volume: 10
bt-headset-enabled: 1
bt-headset-address: 00:09:DD:31:92:98

====Re-Connecting the bt device====

You might need to get the bluetooth headset connected manually on the beginning and also after suspend:

mdbus -s org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_xx_xx_xx_xx_xx_xx org.bluez.Headset.Connect

where xx_xx_xx_xx_xx_xx is address of the device, for example:

mdbus -s org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_00_09_DD_31_92_98 org.bluez.Headset.Connect

Hopefully, your bluetooth headset now works. Good luck!

==System Customizing==

===Changing the splash screen===

list available splash screen themes

opkg list | grep splash-theme

and install one of the available themes

opkg install shr-splash-theme-dontpanic

Then go to SHR Settings -> Others -> Themes. Here you can preview installed themes and change the default one.

===Enable mouse cursor===

edit line 121 of /etc/X11/Xinit and erase -hide-cursor

ARGS="$ARGS -dpi ${DPI} -screen ${SCREEN_SIZE} -mouse tslib -root-ppm /usr/share/pixmaps/xsplash-vga.ppm vt1"

===Improve speed of Elementary applications===

Set the Elementary rendering engine used for Evas to x11-16 (Software X11 16bpp engine, may have bugs and will be lower quality, but faster):
echo -e "#!/bin/sh\n\nexport ELM_ENGINE=x11-16" > /etc/profile.d/set-elm-engine.sh

Additionally in the SHR-Unstable repositories there are theme packages optimized for 16bpp color. Both packages can be installed with the following command:

opkg install e-wm-theme-illume-sixteen elementary-theme-sixteen

You can then append the /etc/profile.d/set-elm-engine.sh with:

# Set Optimized theme
export ELM_THEME=sixteen

You can also then change Illume to use the sixteen theme by clicking the wrench->Look->Theme-illume-sixteen->OK. Then switch Illume to use the 16bpp Engine by clicking the wrench->Advanced(you will need to drag and slide the top menu)->Engine->Software_16->OK. This should give you a much faster interface without the low quality look the default SHR themes have at this lower color depth.

Read http://trac.enlightenment.org/e/wiki/Elementary

If you try to change Wallpaper or Theme and Illume keeps on crashing, it might be caused by the whole Illume running in Software_16 mode. Go to Illume Settings, slide the icon bar and select Advanced. There tap on Engine and select Software. After this, you can change your Wallpaper or Theme. Selecting Software_16 later on again will speed up the desktop's response (though causing it to be a bit uglier).

===Speedup of suspend and wake up===

I you are using Qi and installation on µSD card, you can change the kernel parameter loglevel=1 1 in /boot/append-GTA02 . For u-boot and installation in nand just type

klogd -c 1

into the console. This saves you from 3 seconds worth of console output on every resume.

If you like the effect of this command and want it to be executed at every startup, you just have to log into your phone and type the following:

cat > /etc/init.d/resumespeedup << EOF
#!/bin/sh
/sbin/klogd -c 1
EOF
chmod +x /etc/init.d/resumespeedup
ln -s ../init.d/resumespeedup /etc/rc1.d/S06resumespeedup
ln -s ../init.d/resumespeedup /etc/rc2.d/S06resumespeedup
ln -s ../init.d/resumespeedup /etc/rc3.d/S06resumespeedup
ln -s ../init.d/resumespeedup /etc/rc4.d/S06resumespeedup
ln -s ../init.d/resumespeedup /etc/rc5.d/S06resumespeedup

===Opimd utils===

Opimd utils is a set of several testing scripts to play with the new opimd backends. It also provides opimd-messages program and mainly new opimd-notifier that is much better then the standard one.

opkg install opimd-utils

===opkg upgrade issues===

As '''opkg''' had some '''issues''' recently, installation might get broken due to that. You can fix it or prevent by using the following scripts

Safe update packages:

#!/bin/sh

opkg list_upgradable | awk '!/(kernel|Multiple)/ {print $1}' | \
while read line; do
echo "installing pack $line"
opkg install $line -force-reinstall
done

Force reinstall all installed packages

#!/bin/sh

opkg list_installed | awk '!/(kernel|Multiple)/ {print $1}' | \
while read line; do
echo "installing pack $line"
opkg install $line -force-reinstall
done

===Random errors===
No icons, no GSM functions etc. - this is mostly due to '''errors on your µSD''' card. Remove your card and fix it in card reader or by booting to another partition (nand) or by reboot and mount read only, then run fsck.

For reboot into nand and fix 1st partition of ext2 on your card

fsck.ext2 /dev/mmcblk0p1

===Replace dropbear with openssh===

Set password
passwd

Install ssh server (and sftp)
opkg install openssh-sshd openssh-sftp-server openssh-scp -force-depends

Remove dropbear and start openssh

screen
opkg remove dropbear -force-depends; /etc/init.d/sshd start

You will get disconnected from the ssh session, wait until keys get generated and log in again.
{{Note|'''Remove old SSH Key from <tt>.ssh/known_hosts</tt>:''' On your Linux box you will find a file <tt>known_host</tt> in the subdirectory <tt>.ssh/</tt> in you home directory. This contains a ssh key for the connection to your freerunner. If new keys are generated or if you flash your Freerunner with SHR then you have to remove the line with <tt>openmoko</tt> or the IP-address of your Freerunner from the file. Otherwise you might be able to login in again. }}

===Video playback===

Install intone-video

opkg install elementary libsqlite3-0 http://www.opkg.org/packages/intone-video_0.11_arm.ipk

If intone complaints about missing libraries, please run
#!/bin/sh
cd /usr/lib
ls *ver-svn-02*|while read nombre
do
final="`echo $nombre | sed s/-ver-svn-02/-ver-pre-svn-01/`"
ln -s /usr/lib/$nombre /usr/lib/$final
done

On your desktop, encode your video:

mencoder video-file -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf scale=320:240,eq2=1.2:0.5:-.025,rotate=2 -oac mp3lame -lameopts br=64:cbr -o video-file-FR.avi

===Adding freerunner to your hosts===

You can add freerunner to your hosts file for a name resolving:

You can use the name <tt>neo</tt> if you added the host <tt>neo</tt> in <tt>/etc/hosts</tt> on your desktop computer (add the following line for host <tt>neo</tt> assuming that the IP-address of your freerunner is <tt>192.168.0.202</tt>.
echo "192.168.0.202 neo neo" >> /etc/hosts

You can then access your freerunner like this:

ssh root@neo

Which is shorter then this:

ssh root@192.168.0.202

==Installing Software==

You can use opkg for installing software packages or you can try SHR Installer from http://git.shr-project.org/git/?p=shr-installer.git;a=summary . It requires packagekitd

opkg install packagekitd

If you wan to use opkg after you used the installer, make sure packagekitd is not running

killall packagekitd

'''Cool applications'''

SHR comes with only few preinstalled applications but it's repository provides more cool stuff. Also, there are applications that are not in SHR repos at the moment but can still be installed. The following few examples are here just to spark your interest:

'''SHR Launcher'''

[[Image:Launcher.png|200px|thumb|SHR Launcher]]
Launcher is elementary based alternative home screen application and event notifier for SHR. It displays current time, has a user tweak-able launcher with categories and features missed calls and messages applets.

opkg install libsqlite3-0 http://www.opkg.org/packages/launcher_0.23_arm.ipk

If you dont see some icons, copy all icons from /usr/share/icons/shr/86x86/apps/* to /usr/share/pixmaps.

For '''PIM''' applications you can get dates for calendar, tasks for todos, neote for notes:

opkg install dates tasks

opkg install http://neote.googlecode.com/files/neote_0.2.0-r0_all.ipk

GPE contacts saves the contacts in a SQLite database that can be synchronized with VCard files. Gpe-contacts don't allow you to dial directly via shr-dialer. Install gpe-contacts:

opkg install gpe-contacts

After installation you'll find to icons with ''MyVCard''. If you want to remove it, delete the file <tt>/usr/share/applications/edit-vcard.desktop</tt>

'''Litephone'''

[[Image:SHR-Litephone.png|200px|left|thumb|Litephone]]

Litephone is new alternative set of phone applications written in Qt. In it's single application interface it provides basic phone functionality (contacts, calls, messages, phone log, settings). It's main advantage is that it uses opimd for storage of the user data.

opkg install http://pvtrace.com/litephone/libqtcore4_4.4.3-r3_armv4t.ipk
opkg install http://pvtrace.com/litephone/libqtxml4_4.4.3-r3_armv4t.ipk
opkg install http://pvtrace.com/litephone/libqtdbus4_4.4.3-r3_armv4t.ipk
opkg install http://pvtrace.com/litephone/libqtgui4_4.4.3-r3_armv4t.ipk
opkg install http://pvtrace.com/litephone/qt4-x11-free_4.4.3-r3_armv4t.ipk
opkg install http://pvtrace.com/litephone/litephone_0.0.1-r3_armv4t.ipk

'''Mokomaze''' is an excelent eye-candy game using accelerators embedded in your device.

opkg install mokomaze

If you tweak the exec procedure in /usr/share/applications/mokomaze.desktop into this:
fsoraw -r Display mokomaze
the screen will not blank while playing.

'''[[Cellhunter]]''' is a game to collect information about mobile phone cells. This information can later be used to roughly determine your position without powering on the GPS chip. [http://78.47.116.33/~hole/cellhunter/ CellHunter homepage]

opkg install cellhunter

'''OMGps''' and '''TangoGPS''' are GPS application showing you your position on a map (Openstreetmap, Google maps etc.). You can track your position, save it and use later, save and view points of interest, images or measure your trip. OMGps allows you to overlay different maps on top of each other, set GPS into different modes (walking, car, flying). Maps are downloaded online and used even in offline.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |
[[Image:SHR-TangoGPS-OSM.png|200px|thumb|TangoGPS]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |
C
[[Image:SHR-OMGPS-GM.png |200px|thumb|OMGps]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |

[[Image:SHR-Mokomaze.png|200px|thumb|Mokomaze]]

|}

'''Screenshots''' can be made with ''gpe-scap'' (available by default in SHR full image). To take a screenshot, run gpe-scan from shell while connected in via ssh.

'''Literki''' is full qwerty keyboard with configurable layout, always transparent, therefore applications don't need to redraw screens and popup is therefore very fast. The keys are big enough for everyday use with your fat fingers. To pop up the keyboard: slide your finger upwards from the bottom right corner. To hide the keyboard: slide your finger down on the keyboard. [http://www.opkg.org/package_232.html Opkg page]

opkg install http://pvtrace.com/literki_0.0.2-r3_armv4t.ipk

[[Category:SHR]]

SHR post-installation

2009-08-25T10:03:16Z

Janvlug: /* SHR post-installation script */

=== SHR post-installation script===

In the [[SHR User Manual]] there are mentioned some modifications that might help you to improve the features of you SHR distribution.

After flashing your Openmoko Freerunner you can do these modification manually like mentioned in the [[SHR User Manual]] or
* modify on your desktop computer according your demands and
* execute the following script on your Freerunnner.
The selected shell commands of the SHR User Manual are collected in a SHR post-installation so that you can transfer the script to your Freerunner via scp and execute it with sh. Please go through the script and check if the applications to be installed, are the selection that want you really want. If you do not understand, what is going on in the script, proceed with the [[SHR User Manual]] and select every documented step manually. If you understand the following script, it might save you some time.

Copy and paste the following lines and save them to a file called <tt>SHRpostinstallion.sh</tt>.

#!/bin/sh
echo "SHR Post Installation Script"
echo "============================"
echo "Version 1 - 11.08.2009"

# vLANGUAGE="cz"
vLANGUAGE="de"

echo "SHR-PIS Install Navit - Car Navigation"
echo "--------------------------------------"
echo "src navit http://download.navit-project.org/navit/openmoko/svn" > /etc/opkg/navit-feed.conf
opkg update
opkg install navit
opkg install navit-locale-$vLANGUAGE
mkdir /home/root/.navit
echo "Navit: Solve libgps problem"
opkg install libgps17
ln -s /usr/lib/libgps.so.17 /usr/lib/libgps.so.16

# Already done in version SHR 20090808:
echo "SHR-PIS Install a Working Alarm Clock"
echo "-------------------------------------"
opkg remove -force-depends elementary-alarm
opkg install ffalarms

echo "SHR-PIS Install Bluetooth Package"
echo "---------------------------------"
opkg install obexpush
mkdir /var/obexpush

echo "SHR-PIS Install PIM Apps: Tasks and Dates"
echo "-----------------------------------------"
opkg install dates tasks
opkg install http://www.opkg.org/packages/0_python-ldap_2.3.6_armv4t.ipk python-misc python-netclient python-netserver python-pycairo python-pygobject python-pygtk python-sqlite3 http://www.opkg.org/packages/1_python-vobject_0.8.1_armv4t.ipk http://www.opkg.org/packages/0_python-webdav_0.1.2_armv4t.ipk http://www.opkg.org/packages/1_python-gdata_1.3.0_armv4t.ipk http://www.opkg.org/packages/1_python-dateutil_1.4.1_armv4t.ipk http://www.opkg.org/packages/openldap_2.3.43_armv4t.ipk http://projects.openmoko.org/frs/download.php/841/pisi_0.3_armv4t.ipk
mkdir /media/card/pim
ln -s /media/card/pim /home/root/pim

echo "SHR-PIS MokoMaze"
echo "----------------"
opkg install mokomaze
echo ""
# Response on version SHR 20090808:
# -sh: fsoraw: not found
fsoraw -r Display mokomaze

echo "SHR-PIS CellHunter"
echo "------------------"
opkg install cellhunter

===Copy and Execute Script===
Copy and paste the code into an editor of your choice (KDE kwrite or vi), save the file to <tt>SHRpostinstallation.sh</tt> and upload the file to your freerunner. Execute the shell script on you freerunner:
desktop#
scp c root@192.168.0.202/home/root/SHRpostinstallation.sh
Start the shell script on you Freerunner with:
neo# sh /home/root/SHRpostinstallation.sh
If you want to replace <tt>dropbear</tt> by <tt>openssh</tt> you have to start the script from the terminal on your FR and not via SSH, because the installation restarts the SSH daemon and the script will stop, if you start the script via SSH on your Freerunner from your desktop computer.

[[Category:SHR]]

NWA

2009-07-11T20:36:27Z

Janvlug: /* Installation */

=Introduction=
[[Image:Nwa1.png|245px|right]]
WiFi on the freerunner has some problems, see [[WiFi Managers]].

So I decided to start a project to concentrate all the ideas about an ideal (but simple) GUI applet to manage WiFi connection.

The project is actually only a ''prealpha prototype'' to discover issues and implementation solutions. When ideas and needs will be clear it may be reimplemented in a more elegant way and with your preferred toolkit, now I'm using what I know better, C++ and QT with fast and dirty coding style!

It actually manages wpa_supplicant trough dbus and spawns udhcpc directly, replicating some Network Manager features. When a solid rock network manager will be available for the freerunner, and will handle the specific device capabilities/issues, NWA may be migrated to use it's api.

'''Please partecipate with contributions, ideas, hints as this may become your preferred WiFi manager for a while!!! feel free to edit this or the discussion page, and to contact me by email at nicola.mfb at gmail.com'''

=Requirements=
==A supplicant==
The main target is to use wpa_supplicant in a decent way, e.g. as a supplicant! You'll add your preferred wifi networks at home, at work, at your friend house and so on, and it will scan silently for them, connect when they are available and show a notification window/sound to alert you.

User has to be able to:
* enable/disable configured networks (for example any open network sometime is not desiderable)
* change the networks priority (for example use any open network only if other are not available)
* add new network manually or from scanning the area
* configure advanced network properties, WPA enteprise, EAP, LEAP, TTLS etc.

==Static IP vs DHCP==
The user should be able to use dhcp or static ip addresses.

==DNS handling==
It has to be able to restore some default DNS when exiting dhcp (eg. opendns, last used dns ...), suggestions on possible solutions are appreciated.

==System tray applet==
A sys tray icon should be showed changing it's aspect to reflect connection status.
It should indicate:
* inactive state (wifi disabled)
* scanning
* associated
* complete (associated + authenticated)
* key renewal
* complete + ip address received from dhcp or set manually
* signal strenght when associated
* historical signal strenght (like a graph scrolling every x seconds)
* foreign networks presence

Some special handling is required for Window Managers that does not support sys tray specification (like E17).
==Popup messages==
Popup transient messages should be showed when:
* connection fully complete, showing the received ip address
* disconnection
* wifi card enabled/disabled
* network found (if not connected)

The last has to be defined better, should you signal a new network only one? only one per session? etc.
==Sounds==
Popup has to be associated with sounds to warn the user not looking at the device.

''please suggest some free sounds in every format supported by FSO/gstreamer''

As alternative some software synthetizer may be used.

==Configuration==
The configuration file should be in xml format, a default one will be provided that scan and connect to any open network, so the user may use NWA out of the box. When the user changes settings, the default file is copied in $HOME/.nwa.conf, that one will override the default.

The GUI must be complete but simple and should not allow the user to break the configuration with random clicks, all advanced tasks may be achieved editing the configuration file manually:

* dhcp client to use
* custom scripts to launch at iface up/down, ip received
* ...
==Device Integration==
NWA prefers FSO frameworkd based distro but should be capable to run on everywhere, actually it works fine on my laptop too.
==2.6.29 kernel workaround==
On OM 2.6.29 kernels wifi is broken, software putting down the interface (e.g. wpa supplicant in some cases) will break ar6000 module. A workaround has to be implemented and activable in the configuration file.
==Power Managment==
With some AP the atheros power managment creates problems, NWA should support disabling it.
==Suspend/Resume==
It has to restore automagically the connection on suspend/resume cycles (the prototype does that without any special code as the nature of how it works).

=Development status/issues=
Wpa_supplicant dbus interface is not complete, if you quit the program in some hard way (signaling, closing X, etc) network definitions will not be deleted and at the next run NWA will be crazy, some workarounds:

* <del>kill wpa_supplicant at startup, it' not nice</del>
* <del>implement</del>implemented a remove/readadd interface to wpa when NWA is starting (it should delete all network definition, to be tested)
* <del>bore wpa_supplicant authors to implement the full dbus interface</del> a new version of dbus interface is on the road
* implements signal handling hooks (howewer a kill -9 will bypass it)

Another problem is that wpa_supplicant when connects to a networks signal only the state change and not the network id or network dbus path. This is a big problem as I would have the dhcp/static ip configuration associated to that and not to the essid as it may be the same between different networks.

Using the bssid to disambiguate the network may not be always possible for example when connecting to two big WDS networks with the same essid and thousand of AP.

'''Please comment the above problem and suggest alternatives. I'll add dhcp/static ip support when things will be clear'''

<del>as wpa_supplicant does not signal the connected network we have to retrieve the essid with standard AF_INET ioctl, so qnetutils.cpp has to be improved</del>qnetutils.cpp now read the essid of the associated network.

The qt stylesheet has to be improved.

A 2.6.29 rude workaround was implemented, when you quit the NWA it does not kill udhcpc and deconfigure eth0 from wpa_supplicant (always remove networks) but simply release the FSO WiFi resources, removing the interface without deconfiguring. It works only sometimes. We may think to rmmod/insmod ar6000 but it's a very crude hack and sometimes kernel opses.

A startup script, launched when supplicant association is complete, is already implemented, it's a crude way to disable power management if needed.

The second problem for static ip support is that I have to study a bit more rtnetlink to implement static ip without calling exeternals command :) in the mean time I'm planning to support <del>per-network</del> per-essid command file execution and dhcp disabling, so you may use some script to configure the interface with a static address. It should be sufficient for a prototype.

<del>Actually destroying a running thread when application quits leads an "application crashed" on E, I'm not caring of it now</del> a better clean and quit handler has to be implemented.

To play sounds notification spawning a shell sound player may be weight and slow, so I think it's better to use FSO, while to have speech synthesis the script approach may be acceptable, <del>parameter passing has to be implemented in the configuration file (network name, ip address and so on)</del> just use $IFACE$ and $IP$ when you want it be automagically replaced with their respective values.

It seems as udhcpc when got an ip address set/unset/set_again the ipaddress, this is strange. The problem is not present with dhcpcd. Updates: this happens with udhcpc on a Cisco MDS wifi network and not with common AP.

<del>FSO returns random errors when PlaySound is used while a sound is already played</del> on debian sid there is no default dmix alsa configuration, this has to be declared in NWA prerequisites

Some small coding fixes need to be done, and some stupid comments removed :)

The first prealpha prototype is quite ready, it was developed on debian with Matchbox and matchbox-panel as sys trayer, under E qt balloon sys tray messages are showed in a random position on the screen, <del>so some special work around is needed</del> a primitive and animated "tooltip" was implemented. Multiple not overlapping message showing are not supported a queue handler has to be implemented.
I preferred to avoid qt sys tray baloon message on not-E wm too, as if the tray icon is in a middle/left position (becouse other tray icon are present), in some cases they are not readable.
=Installation=
Some guys asked for a preview, if you feel adventurous and want to join and test the prototype do the following:
echo "src/gz noko-testing-armv4t http://noko.sourceforge.net/testing/om2009/armv4t" >/etc/opkg/noko-feed.conf
opkg update
opkg install nwa
''This was tested only on OM2009 testing 5 + opkg update/upgrade''

Please note the not versioning is used so if you want to upgrade you have to:
opkg remove nwa
opkg update
opkg install nwa

Source is cooming soon.

=Using it=
NWA should work out of the box at first startup on the freerunner as it has some hardcoded settings in the xml parser and in the default configuration file targeted for the freerunner, it should connect to any open network as one becomes available without further user intervention.

This is only for demonstration pourpose or when you are traveling :), in normal cases you have to add/remove/edit/enable/disable networks.
==Adding a network==
Go on the "scan page" and click on "scan", after a bit available networks should appear, click on one of them and a wizard dialog will help you to configure the network with every kind of parameter wpa supplicant supports. I was able to add my home wpa/psk network and my campus EAP/TTLS/PAP radius enterprise network without problems.

You may click on "manual add" too without scanning, this is the beginning support for some kind of hidden networks (to be done) asap I have a configurable AP in my hands :)

The network is added and enabled, wpa_supplicant will decide how and when connect to it based on it's status priority etc.
==Enabling/Disabling/Editing/Removing networks==
Go on the "network page", you'll have two box, the upper contains the enabled network, the bottom the available (disabled) network. Clicking on a network shows a menu that permits you to do the needed operation.

So if you want to ignore open networks simply disable the "Any open" profile, and reenable it when walking around in the world.
==Enable/Disable/Autoenable WiFi==
This is the FSO ousaged control, so be warned if you enable wifi from external application you'll see NWA working even if the wifi status is "disabled".

The autoenable button let you choose if autoenable the wifi resource at startup.
==Tray Icon==
On WM with a standard trayer, NWA will show an icon with current wpa_supplicant status and historical signal strenght indication. Clicking on the icon will show the main window, to hide the main window use your window manager capability.

=Configuring=
NWA read $HOME/.nwa.conf configuration file, if it does not exists it read /usr/share/nwa/defaultconfiguration.xml.
When you change some configuration with the GUI the default file is copied in $HOME/.nwa.conf.

All common configuration is done in the GUI, for advanced usage you may edit your $HOME/.nwa.conf file (copy it if it does not exists yet)
==Example configuration file==
<pre>
<xml version="1.0">



<dhcpclients>
<dhcpclient name="udhcpc -f -i $IFACE$" default="yes"/>
<dhcpclient name="none" />
</dhcpclients>

<autoenable value="yes" />

<iface name="eth0" maxquality="255"/>

<networks>
<network name="Any Open" key_mgmt="NONE" enabled="yes"/>
</networks>

<ifupscript path="logger NWA iface $IFACE$ up"/>
<ifdownscript path="logger NWA iface $IFACE$ down"/>

<ipupscript path="logger NWA iface $IFACE$ got ip $IP$"/>
<ipdownscript path="logger NWA iface $IFACE$ losed ip $IP$"/>
<brokenkernelhack value="no"/>
<apscan mode="1"/>

<usefso value="true"/>
<upsound path="/usr/share/nwa/sounds/bonus.ogg"/>
<downsound path="/usr/share/nwa/sounds/gameover.ogg"/>

<alwaysshowwindow value="no" />
</xml>
</pre>

[[Category:Wlan software]]

Community Updates/2009-07-09

2009-07-10T07:43:42Z

Janvlug: language

====='''Period June 25nd to July 9th, 2009'''=====

==Distributions==

* '''[http://activationrecord.net/radekp/qtmoko/ QtMoko V3]''' - QT moko is a debian distribution for the Openmoko FreeRunner phone. Phone and user interface are based on QT Extended, formerly known as Qtopia. Version V3 should be stable as a daily phone. Latest changes include:
** upgrade to QT 4.5.2 which should improve speed
** merge from other QtMoko branches with many bug fixes
** added nice new QtMaze game
** fixed problem so that apt-get should work out of the box now

* '''[http://activationrecord.net/radekp/qtmoko/download/ Experimental QtMoko X4]''' - new QtMoko images that are based on debian and that now support running X application from Qtopia. You have to use QX launcher which will allow you to start X applications in fullscreen. You can exit the application when you press the touchscreen for 5 seconds. The application will then be paused and you can either kill it or continue. The support for switching tasks between Qtopia and X application is still missing.
** images are called x4 (because of X windows support), images without X will be called v4
** logging should now work
** better UI speed
** rotation should work
** apt-get should work out of the box
** new application QX which is used as launcher for X applications
** included tangogps and scummvm
** /dev/mmcblk0p1 mounts to /media/card now and /dev/mmcblk0p4 as swap

* '''[[OpenWrt]]''' - Mirko Vogt and the OpenWrt team have released OpenWrt for the Neo/FreeRunner devices. They provide flashable [http://nanl.de/files/openwrt/openmoko/ images]. Mind - that, as usual for OpenWrt - the default IP of your device will be "192.168.1.1" and the only running service will be <telnet> on port 23. After logging in and setting a password, <telnetd> is getting replaced through <sshd> (port 22).
** kernel 2.6.30.1 is running
** clean, stable and accelerated graphics system
** GPS works
** performance tuned
** software added/upgraded
** a beautiful bootsplash
** phone calls are possible, thanks to paroli
* A new release of FSO is around the corner, see [[OpenmokoFramework/Status Update 7|Openmoko Framework Team Status Report 2009.7]]

==Applications==
===New Applications===

* '''[http://github.com/Sektor/mqutim/ mqutIM]''' - instant messenger for QtMoko. Only ICQ protocol is currently supported.
* '''[http://github.com/Sektor/noxchat/ NoxChat]''' - IRC client for QtMoko.
* '''[http://code.google.com/p/neote/ Neote 0.2.0]''' - note taking application. Its interface aims to be easy and finger friendly. It's written in Python/Elementary and uses SQLite for storing data. Notes can be organized using custom categories that you can add, rename and delete at any time. Currently, only text note type is available. It should run on any system with a revision of python-elementary equal or greater to 40756. Looks like at time of this writing SHR-unstable is the only candidate. Future plans:
** Draw notes
** Record voice notes

===Application Updates===

* '''[http://code.google.com/p/elmdentica/ Elmdentica 0.5.1]''' - the µ-blogging (identi.ca only, so far) client for your Free Smartphone. You can take a look at the screenshot [http://blog.1407.org/2009/07/09/elmdentica-release-051/ here]
** now with pretty bubbles with icons and temporal references
** repeat (or retweet) what other say and reply to others
** counter which warns if you type more than 140 characters ''//somebody double check, please''
** multiple account support (only one active at each moment)
** Fixed some bugs
** added a domain editor
** supports links in status messages

* '''[http://projects.openmoko.org/frs/?group_id=260&release_id=542 ffalarms 0.2.3]''' is a program to set multiple alarms a day using a finger friendly user interface (hence the name). Three clicks to set an alarm time. Progressive volume. Switch off though four buttons puzzle. LED night clock included. ffalarms 0.2.3 includes:
**rewritten using Vala/libeflvala/Elementary (same features as 0.2.2)
**avoids suspend and keeps display on during alarm on FSO platform (such as SHR)
**note: will not stop alarms added by previous versions of ffalarms

* '''[http://gvsigmobileonopenmoko.wordpress.com/ gvSIG Mobile 0.1.4]''' - Mobile GIS
** [http://gvsigmobileonopenmoko.wordpress.com/2009/06/24/with-the-new-courier-mode-openmoko-actively-guides-you-through-the-city/ Courier Mode] - produce and display tours of an area, or use the eature to measure your distance from a point / region
**GUI tweaks including full screen mode
**Arabic translation, thanks to Nawfal Cherqui
**Support for German coordinate systems (EPSG:31466 to EPSG:31469)

==Community==
* On 2008-07-04, according to '''[http://www.openmoko.com/press/Openmoko_20080702.pdf press release]''', Openmoko has opened it's online store for purchase of the Openmoko Neo FreeRunner. Thus this date is considered as official FreeRunner birthday day. Happy birthday FreeRunner!
* Opened Czech Openmoko community portal: '''http://www.openmoko.cz''' and moved [http://www.jabber.cz Jabber] conference from openmoko@chat.linjab.net to openmoko@muc.openmoko.cz
* Kimaidou, author of [[Mokometeo]], has created a google '''[http://code.google.com/p/mokometeo/source/checkout code]''' page with a mercurial repository. Thus you all are encouraged to commit the improvements.
* David Reyes has uploaded the '''[http://www.tuxbrain.com/en/content/buzz-fix-party-barcelona-movie video]''' made at Barcelona Buzz fix party and also made subtitles in English. Sure it can be improved but at least will let follow the conversations for those who are not familiar with Spanish.
* Pictures with comments of the last Buzz fix party on Madrid can be found '''[http://www.tuxbrain.com/en/content/buzz-fix-party-madridphotos here]'''.

==Event News==

* '''2009-07-25''' '''[https://penta.debconf.org/dc9_schedule/events/376.en.html The Debconf9]''' buzz fix party has been scheduled on Saturday.
* '''2009-07-18''' '''[http://openmoko.cz/www/index.php/pages/read/2/Openmoko_sraz_prednaska_a_buzzfix_party_v_Beroun Linux meeting Beroun]''' Czech Openmoko community meeting and buzz fix party in Beroun.

[[Category:Community Update]]

Jalimo

2009-07-06T11:31:49Z

Janvlug: Installation of Jalimo java on SHR Unstable.

website: [http://www.jalimo.org www.jalimo.org]

==Installation on SHR Unstable==
(might also work on other distributions)
# Add the repositories as described here: [https://wiki.evolvis.org/jalimo/index.php/Packages#OpenMoko Packages].
# Install the packages (the <code>-force-depends</code> is needed to workaround a bug somewhere):
opkg install -force-depends cacao classpath classpath-common libswt3.4-gtk-java jamvm
For further details see: [https://wiki.evolvis.org/jalimo/index.php/OpenMoko Jalimo on Openmoko].

Java

2009-07-06T11:24:22Z

Janvlug: /* Status on Openmoko */ Link to Jalimo on Openmoko wiki.

== Introduction ==
There are three main types of Java platforms that can be made available on Openmoko devices such as the Neo1973.
* Java Standard Edition (Java SE)
* Java Micro Edition (Java ME)
* Hybrid Solutions

=== Java Standard Edition (Java SE) ===

This is the incarnation of the desktop version of Sun's Java platform. The majority of its codebase was recently opensourced under the GPL+exception license; the closed bits are quickly being replaced by unencumbered alternatives.

When people talk of Java applications, they're usually referring to software targeted to this platform. Application memory footprints on desktop applications usually include the VM and base libraries, rather than just the application itself (this isn't the case in Java ME).

=== Java Micro Edition (Java ME) ===

This is the 'lite' edition of the Java platform. Modular and optimised for embedded devices, this platform provides a much more restricted set of language and library features.

Java ME applications are usually referred to as MIDlets (Sun's name for these applications).

When talking about games and mobile phone games in general, people are normally referring to this platform. Java ME games and applications are expected to function within the strict memory capabilities of the corresponding platform (application descriptors allow the runtime environment to know for which they are intended).

Memory footprints of MIDlets written for Java ME are typically quoted exclusive of the VM or base libraries -- this is because they are often delivered to Java-enabled devices over the network. Footprint sizes average 10-64KB, with recent devices supporting up to 1MB MIDlets.

MIDlet are delivered as two files:
* a .jad MIDlet metadata descriptor
* a .jar MIDlet container, containing executable bytecode and any required resources

=== Hybrid Solutions ===

Other approaches include mixing and matching Java SE and Java ME in various ways. Standard methods include providing a compatibility layer on top of Java SE (like [http://www.microemu.org/ microemu]) to allow it to run Java ME and expanding Java ME to provide more Java SE features.

Another possible approach would be to have every application compiled to native with gcj when installed and then run without a JVM, with a much faster startup. This may be risky and needs a specialized installer.

== Implementations ==

=== Java SE implementations ===
* [http://openjdk.java.net/ OpenJDK], the open-sourced implementation of the Java Platform Standard Edition.
* [http://en.wikipedia.org/wiki/Icedtea Icedtea], basically OpenJDK with some improvements (initially from Redhat) to ease incorporating into free software distributions.
* [http://www.cacaojvm.org/ Cacao] is a GPL Java-Virtual-Machine(JVM) which uses Just-In-Time(JIT) compilation combined either with Icedtea/OpenJDK or [http://www.gnu.org/software/classpath/ Classpath].
* [http://jamvm.sourceforge.net/ JamVM], another GPL JVM with very small footprint (<160k) combined with [http://www.gnu.org/software/classpath/ Classpath] classes.
* [http://harmony.apache.org/index.html Apache Harmony], is the Java SE project of the Apache Software Foundation.

=== Java ME implementations ===
* [https://phoneme.dev.java.net/ PhoneME] is basically the code base of Sun's commercial Java ME implementation without those components that Sun can't --or won't-- release to the open source community. It is licensed under GPL2. There are actually two versions of PhoneME:
** '''PhoneME Feature:''' is an implementation of the CLDC (Connected Limited Device Configuration) and MIDP2 (Mobile Information Device Profile) as is common on feature phones (e.g. 'normal', non-smart phones).
** '''PhoneME Advanced:''' is an implementation of the more complex CDC (Connected Device Configuration), designed for more advanced handsets.{{Note|this runtime and library can be made available for OpenMoko through OpenEmbedded easily.}}
* [http://midpath.thenesis.org MIDPath] is a Java library which provides a MIDP2 implementation and can be used together with the CLDC version of the Cacao to provide an alternative implementation of CLDC/MIDP.
* [http://www.microemu.org/ Microemu]: a Java ME emulator that runs on top of Java SE. If the overhead is small enough, it should be the "cheapest" solution.

== Status on Openmoko ==
[http://java-pkg.projects.openmoko.org/ Java-pkg] is a [http://projects.openmoko.org/ projects.openmoko.org] [http://projects.openmoko.org/projects/java-pkg/ project] whose aim it is to "Get Java going on Openmoko, and once it's running, maintain it. There are two subprojects, one for JME and one for JSE. Priority is currently given to JME CDC profile." There is currently a work-in-progress recipe for PhoneME Advanced in their SVN, which doesn't fully build, as well as a working recipe for PhoneME Feature, which only works directly on the Neo1973 framebuffer (e.g. you'll have to stop Xfbdev).

[[Jalimo]] is a project to feature the integration of free Java-like implementations for free platforms. They already have [https://wiki.evolvis.org/jalimo/index.php/Packages#OpenMoko packages for Openmoko], covering Cacao, GNU Classpath (with Swing support), PhoneME Advanced Foundation/Personal, SWT and the java-gnome bindings, which allows writing GTK+ applications in Java. Build recipes are part of OpenEmbedded and maintained therein. This [https://wiki.evolvis.org/jalimo/index.php/OpenMoko article] describes, how to get started, if you want to install and use Jalimo on Openmoko based systems.

On [[Debian]], both [http://packages.debian.org/sid/cacao-oj6-jre CacaoVM] and [http://packages.debian.org/sid/jamvm JamVM] SE-JREs have been ported, and although JamVM is considerably faster at start-up, CacaoVM offers a full JSE-1.5 implementation from [http://en.wikipedia.org/wiki/Icedtea Icedtea] than JamVM's [http://www.gnu.org/software/classpath/ GNU-Classpath] classes.
The [http://www.microemu.org/index.html microemu] can be used on top of CacaoVM to run PhoneME applications (MIDlets etc).

== Licensing ==

=== VM Licensing ===

=== MIDlet Licensing ===

== Links ==

Google should be your main resource for most Java-related topics. Below is a selected list of further information resources.

=== Java SE Links ===

In 2006/7 Sun [http://www.deviceforge.com/news/NS9280947932.html acquired the assets of Savaje], which included a port of J2SE to ARM Linux. This was used to build the "JavaFX" modules and, in fact, it runs on the Neo1973 already. They used it to show JavaFX at the JavaOne 2007: http://java.sun.com/javaone/sf/media_shell.jsp?id=193609 See also http://blogs.sun.com/jonathan/entry/when_not_where

=== Java ME Links ===

[[Category:Application Developer]]

Java

2009-07-06T09:09:19Z

Janvlug: /* Status on Openmoko */ Link to Jalimo on Openmoko getting started.

== Introduction ==
There are three main types of Java platforms that can be made available on Openmoko devices such as the Neo1973.
* Java Standard Edition (Java SE)
* Java Micro Edition (Java ME)
* Hybrid Solutions

=== Java Standard Edition (Java SE) ===

This is the incarnation of the desktop version of Sun's Java platform. The majority of its codebase was recently opensourced under the GPL+exception license; the closed bits are quickly being replaced by unencumbered alternatives.

When people talk of Java applications, they're usually referring to software targeted to this platform. Application memory footprints on desktop applications usually include the VM and base libraries, rather than just the application itself (this isn't the case in Java ME).

=== Java Micro Edition (Java ME) ===

This is the 'lite' edition of the Java platform. Modular and optimised for embedded devices, this platform provides a much more restricted set of language and library features.

Java ME applications are usually referred to as MIDlets (Sun's name for these applications).

When talking about games and mobile phone games in general, people are normally referring to this platform. Java ME games and applications are expected to function within the strict memory capabilities of the corresponding platform (application descriptors allow the runtime environment to know for which they are intended).

Memory footprints of MIDlets written for Java ME are typically quoted exclusive of the VM or base libraries -- this is because they are often delivered to Java-enabled devices over the network. Footprint sizes average 10-64KB, with recent devices supporting up to 1MB MIDlets.

MIDlet are delivered as two files:
* a .jad MIDlet metadata descriptor
* a .jar MIDlet container, containing executable bytecode and any required resources

=== Hybrid Solutions ===

Other approaches include mixing and matching Java SE and Java ME in various ways. Standard methods include providing a compatibility layer on top of Java SE (like [http://www.microemu.org/ microemu]) to allow it to run Java ME and expanding Java ME to provide more Java SE features.

Another possible approach would be to have every application compiled to native with gcj when installed and then run without a JVM, with a much faster startup. This may be risky and needs a specialized installer.

== Implementations ==

=== Java SE implementations ===
* [http://openjdk.java.net/ OpenJDK], the open-sourced implementation of the Java Platform Standard Edition.
* [http://en.wikipedia.org/wiki/Icedtea Icedtea], basically OpenJDK with some improvements (initially from Redhat) to ease incorporating into free software distributions.
* [http://www.cacaojvm.org/ Cacao] is a GPL Java-Virtual-Machine(JVM) which uses Just-In-Time(JIT) compilation combined either with Icedtea/OpenJDK or [http://www.gnu.org/software/classpath/ Classpath].
* [http://jamvm.sourceforge.net/ JamVM], another GPL JVM with very small footprint (<160k) combined with [http://www.gnu.org/software/classpath/ Classpath] classes.
* [http://harmony.apache.org/index.html Apache Harmony], is the Java SE project of the Apache Software Foundation.

=== Java ME implementations ===
* [https://phoneme.dev.java.net/ PhoneME] is basically the code base of Sun's commercial Java ME implementation without those components that Sun can't --or won't-- release to the open source community. It is licensed under GPL2. There are actually two versions of PhoneME:
** '''PhoneME Feature:''' is an implementation of the CLDC (Connected Limited Device Configuration) and MIDP2 (Mobile Information Device Profile) as is common on feature phones (e.g. 'normal', non-smart phones).
** '''PhoneME Advanced:''' is an implementation of the more complex CDC (Connected Device Configuration), designed for more advanced handsets.{{Note|this runtime and library can be made available for OpenMoko through OpenEmbedded easily.}}
* [http://midpath.thenesis.org MIDPath] is a Java library which provides a MIDP2 implementation and can be used together with the CLDC version of the Cacao to provide an alternative implementation of CLDC/MIDP.
* [http://www.microemu.org/ Microemu]: a Java ME emulator that runs on top of Java SE. If the overhead is small enough, it should be the "cheapest" solution.

== Status on Openmoko ==
[http://java-pkg.projects.openmoko.org/ Java-pkg] is a [http://projects.openmoko.org/ projects.openmoko.org] [http://projects.openmoko.org/projects/java-pkg/ project] whose aim it is to "Get Java going on Openmoko, and once it's running, maintain it. There are two subprojects, one for JME and one for JSE. Priority is currently given to JME CDC profile." There is currently a work-in-progress recipe for PhoneME Advanced in their SVN, which doesn't fully build, as well as a working recipe for PhoneME Feature, which only works directly on the Neo1973 framebuffer (e.g. you'll have to stop Xfbdev).

[http://www.jalimo.org Jalimo] is a project to feature the integration of free Java-like implementations for free platforms. They already have [https://wiki.evolvis.org/jalimo/index.php/Packages#OpenMoko packages for Openmoko], covering Cacao, GNU Classpath (with Swing support), PhoneME Advanced Foundation/Personal, SWT and the java-gnome bindings, which allows writing GTK+ applications in Java. Build recipes are part of OpenEmbedded and maintained therein. This [https://wiki.evolvis.org/jalimo/index.php/OpenMoko article] describes, how to get started, if you want to install and use Jalimo on Openmoko based systems.

On [[Debian]], both [http://packages.debian.org/sid/cacao-oj6-jre CacaoVM] and [http://packages.debian.org/sid/jamvm JamVM] SE-JREs have been ported, and although JamVM is considerably faster at start-up, CacaoVM offers a full JSE-1.5 implementation from [http://en.wikipedia.org/wiki/Icedtea Icedtea] than JamVM's [http://www.gnu.org/software/classpath/ GNU-Classpath] classes.
The [http://www.microemu.org/index.html microemu] can be used on top of CacaoVM to run PhoneME applications (MIDlets etc).

== Licensing ==

=== VM Licensing ===

=== MIDlet Licensing ===

== Links ==

Google should be your main resource for most Java-related topics. Below is a selected list of further information resources.

=== Java SE Links ===

In 2006/7 Sun [http://www.deviceforge.com/news/NS9280947932.html acquired the assets of Savaje], which included a port of J2SE to ARM Linux. This was used to build the "JavaFX" modules and, in fact, it runs on the Neo1973 already. They used it to show JavaFX at the JavaOne 2007: http://java.sun.com/javaone/sf/media_shell.jsp?id=193609 See also http://blogs.sun.com/jonathan/entry/when_not_where

=== Java ME Links ===

[[Category:Application Developer]]

WiFi Managers

2009-07-06T07:53:14Z

Janvlug: /* Introduction */ Link to connman.

=Introduction=
It's not easy to use WiFi with the freerunner:
* 2.6.29 kernels has major issues on ifconfig up/down
* 2.6.28 kernels has random issues on fake wow events
* 2.6.24 kernels has rare random issues
* on OE based distro the wpa-roaming support is broken, the wpa-conf approach is working fine but it does not renew dhcp ip address when the freerunner changes AP
* using udev to trigger interface configuration does not spawn dhcp, the problem is that the kernels brings the interface up, so networks scripts ignore it
* some AP refuses the power management mode of the atheros 6000, so you have to launch some script to setup it when the interface comes up
* [http://connman.net/ connman] seems to not support WPA/WPA2 enterprise mode (please confirm)
* connman does not set a route if one is already present (always as usb0 has a default route)
* other wifi implementation, that in a rude way scan the networks and generate a wpa_supplicant.conf file, does not support WPA/WPA2 enterprise mode
* connman api changed so Illume wifi gadget does not work anymore (please confirm)

=Proposal=
* patch the damned kernel :)
* bore Illume authors to patch wifi gadget with the new connman api
* bore connman authors to support WPA/WPA2
* write a WM indipendent connman applet
* test other NetworksManager to see if they may run fine on the freerunner
* write a simple WiFi manager interacting with wpa_supplicant by dbus, see a first prototype at [[NWA]]

Who is Who

2009-06-23T17:58:14Z

Janvlug: Links added.

If you subscribe to a mailing list or join an IRC channel, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?
This page should serve as a list of community members and their areas of expertise.

= Community members =

IRC nicknames are in brackets after each name.

== [[Kernel]] ==

* Luca Capello
* Mike Westerhof (mwester)
* Nelson Castillo (Arhuaco)
* Paul Fertser (PaulFertser)
* Timo Juhani Lindfors (lindi-)
* Rod Whitby (rwhitby)
* Werner Almesberger (wpwrak)

== [[FSO]] (freesmartphone.org) ==
* Michael Lauer ([[user:Mickey|Mickey]])
* Jan Luebbe (Shoragan)
* Daniel Willmann (Alphaone)
* Stefan Schmidt

== [[Om2009]] ==
* Angus Ainslie (nytowl)

== [[SHR]] ==
* David Kozub (dent)
* Klaus Kurzmann (mrmoku)
* Wolfgang Kroener (azog)
* Hire
* David Wagner (deubeuliou)
* Montgoss
* Dolf
* Quickdev (RIP)
* Sebastian Spaeth (spaetz)
* Cameron Frazier (Toaster)
* Didier (ptitjes)
* Yorick (yoyo)
* Tom (Tasn)
* Morphis
* Hiciu
* Sebastian Krzyszkowiak (dos)
* Stian Skjelstad (mywave)
* Tilman Sauerbeck (tilman)
* Mike Westerhof (mwester)
* Bobby Martin (wurp2)

== [[hackable:1]] ==
* Marcus Bauer (iscape)
* Jérôme Blondon (jbl2024)
* Sébastien Bocahu (zecrazytux)
* Pierre Pronchery (khorben)
* David Wagner (deubeuliou)

== [[Paroli]] ==
* Mirko Lindner (mirko)

== [[Smedia_Glamo_3362#Hardware_Accelerated_Projects|X.org / Glamo (Graphics subsystem)]] ==
* Lars-Peter Clausen (larsc)
* Thomas White (Weiss)
* Andreas Pokorny (DieMumiee)
* Timo Juhani Lindfors (lindi-)

== [http://activationrecord.net/radekp/openmoko/qtmoko/ QtMoko] ==
* Lorn Potter (lpotter)
* Radekp
* Franky Van Liedekerke (liedekef)
* Fabio Alessandro Locati (fale)

== [[MokoMakefile]] ==
* Rod Whitby (rwhitby)

== [[gta02-core]] ==
(community project to create a new hardware revision of the gta02 hardware)
* Werner Almesberger (wpwrak)

= Officials members of the Openmoko Team =

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

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

[[Category:Openmoko Inc]]

Who is Who

2009-06-23T10:23:30Z

Janvlug: Added link to Mickey's user page.

If you subscribe to a mailing list or join an IRC channel, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?
This page should serve as a list of community members and their areas of expertise.

= Community members =

IRC nicknames are in brackets after each name.

== Kernel ==

* Luca Capello
* Mike Westerhof (mwester)
* Nelson Castillo (Arhuaco)
* Paul Fertser (PaulFertser)
* Timo Juhani Lindfors (lindi-)
* Rod Whitby (rwhitby)
* Werner Almesberger (wpwrak)

== FSO (freesmartphone.org) ==
* Michael Lauer ([[user:Mickey|Mickey]])
* Jan Luebbe (Shoragan)
* Daniel Willmann (Alphaone)
* Stefan Schmidt

== Om2009 ==
* Angus Ainslie (nytowl)

== SHR ==
* David Kozub (dent)
* Klaus Kurzmann (mrmoku)
* Wolfgang Kroener (azog)
* Hire
* David Wagner (deubeuliou)
* Montgoss
* Dolf
* Quickdev (RIP)
* Sebastian Spaeth (spaetz)
* Cameron Frazier (Toaster)
* Didier (ptitjes)
* Yorick (yoyo)
* Tom (Tasn)
* Morphis
* Hiciu
* Sebastian Krzyszkowiak (dos)
* Stian Skjelstad (mywave)
* Tilman Sauerbeck (tilman)
* Mike Westerhof (mwester)
* Bobby Martin (wurp2)

== hackable:1 ==
* Marcus Bauer (iscape)
* Jérôme Blondon (jbl2024)
* Sébastien Bocahu (zecrazytux)
* Pierre Pronchery (khorben)
* David Wagner (deubeuliou)

== Paroli ==
* Mirko Lindner (mirko)

== X.org / Glamo (Graphics subsystem) ==
* Lars-Peter Clausen (larsc)
* Thomas White (Weiss)
* Andreas Pokorny (DieMumiee)
* Timo Juhani Lindfors (lindi-)

== QtMoko ==
* Lorn Potter (lpotter)
* Radekp
* Franky Van Liedekerke (liedekef)
* Fabio Alessandro Locati (fale)

== MokoMakefile ==
* Rod Whitby (rwhitby)

== gta02-core ==
(community project to create a new hardware revision of the gta02 hardware)
* Werner Almesberger (wpwrak)

= Officials members of the Openmoko Team =

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

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

[[Category:Openmoko Inc]]

Om 2009

2009-06-17T20:48:54Z

Janvlug: /* Bugs / missing features */ disabling suspend does not work.

{{Languages|Om 2009}}
[[Image:Paroli.png|thumb|Screenshot of Paroli, the GSM app of OM2009]]
'''Om 2009''' is the next version of the official Openmoko distribution. The latest release is testing5 from June 16th, 2009.

Om2009 testing5 already has all the features most people need for daily phone usage: SMS, calling, phone book, call log, charging, suspend&resume, wifi gui, audio profiles, etc.

Om2009 is currently under developement and should be released in Summer 2009 to replace [[Om 2008]]. It is based on [[FSO|freesmartphone.org]] milestone 5.5 framework and use [[Paroli]] as GSM software.

== Installing ==

=== GSM firmware ===
* If you've not updated your GSM chip firmware, it's Moko8 and REALLY needs to be updated. See [[GSM/Flashing#uSD-card_Image_.28GTA02_only.29|GSM flashing]]

=== bind-home ===
You can add a bind-home directory to the first partition (must be ext2 or ext3 ) of your SD card. On the OM2009 boot it will be mounted as /home/root. This way you can reflash your phone without losing anything in your home directory ([[Paroli]] contacts and settings, maps, etc)

Make sure there isn't a bind-home directory first
ls /media/card/bind-home
If this exists you are already using bind-home, otherwise keep following the directions below
mv /home/root /media/card/bind-home
mkdir /home/root
reboot

=== qi/uboot/OM2009 ===
Also update to the latest versions of [[qi]] or [[Bootloader|uboot]] bootloaders
The latest OM2009 and qi/uboot images are available at http://downloads.openmoko.org/distro/testing/

Installing OM2009 is simple as flashing an image. Actually that's what you need to do.

# Download! You need the correct fso-paroli-image and uImage.bin files for your device. There are also rootfs tarballs for installing onto an SD card. [http://downloads.openmoko.org/distro/testing/NeoFreerunner Freerunner] or [http://downloads.openmoko.org/distro/testing/Neo1973 Neo1973]
# Flash! Detailed instructions for [[Flashing_the_Neo_Freerunner|Freerunner]] and [[Flashing_the_Neo_1973|Neo1973]].
# Start! The image will boot into fullscreen Paroli and all of the features listed above will be available. To learn more about Paroli, see [[Paroli]]

Boot AND REBOOT! The first time it boots there some problems might occur but they're gone after the second boot.

== Using OM2009 ==
'''Write your best tips here!!'''

* To '''learn to use Paroli''', the phone software, go to [[Paroli#FAQ]]
* To '''import vcard -contacts''' to Paroli, check [http://www.mail-archive.com/support@lists.openmoko.org/msg04770.html this]
* '''To prevent suspending when USB plugged in''': unplug usb until LED goes out, then plug usb in: you need to keep the device awake by touching the screen until the LED comes back on. (bug: http://trac.freesmartphone.org/ticket/381)
* '''Angstrom feeds''' Contain many useful packages including mplayer and ffmpeg. Run these commands to add the angstrom feeds '''NOTE:''' You will not be able to upgrade OM2009 after this, it will break!
echo "arch base 50" > /etc/opkg/angstrom-feed.conf
echo "src/gz base http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base" >> /etc/opkg/angstrom-feed.conf

==== Audio quality during call ====
* Audio quality is good by default for some Freerunners. Some units need a new audio profile:
wget http://docs.openmoko.org/trac/raw-attachment/ticket/2121/gsmhandset.state.new -O /usr/share/openmoko/scenarios/gsmhandset.state
* More info can be found here: http://wiki.openmoko.org/wiki/Neo_Freerunner_audio_subsystem

==== Audio problems ====
* If you have problems with audio, try this:
modprobe snd-pcm-oss
* If audio works, load this module on boot:
echo "snd-pcm-oss" > /etc/modutils/snd-pcm-oss
update-modules
* Problems:
** Allowing the FR to suspend or having the screen blackout while using mplayer will sometimes crash the FR
** Plugging in the headset will stop audio from playing out of the phone's speaker. Audio will not return until the phone is shut off or you receive or make a call

== Bugs / missing features ==

* Screen lock is missing
** currently X screen saver is used during screen blank

* (Paroli) GUI to change ring tones missing
* (Paroli) GUI for Bluetooth missing
* Led indication for missed calls or sms missing
* Battery indicator support for GTA01 broken

* Boot time needs to be reduced to less than 2 minutes
** install udev-static-devices - caveat you lose bind-home
** use readahead to cache python dirs before starting framework and paroli
** use readahead to cache dirs for X
** remove unneeded startup programs ( ie portmap )
** prime GSM during init for paroli's use

* gsm0710muxd: "Modem does not respond to AT commands" [http://docs.openmoko.org/trac/ticket/2257 #2257]
* oeventsd rules ignored [http://trac.freesmartphone.org/ticket/381 FSO #381]
* Disabling suspend does not work [http://docs.openmoko.org/trac/ticket/2296 #2296]

== Development ==
'' When we set the very limited goals of OM2009 we had two goals in mind:''

''1. Give those members of the community who only wanted a daily phone, a distro they could use'' 
''2. Introduce technology that would allow the community to come together and improve on these basics''

''Community interaction, open development and user driven decision making are at the core of Om2009. Going forward this will be an effort with the community for the community. I invite you to join the effort to make om2009 with paroli the best Om-labeled distribution for the Freerunner. ''

'''How can you help?'''

''Test the distro, let us know about bugs you find, or even fix them and send us patches.''

''Tell us about your experiences using om2009, what should we change, where can we improve?''

''Paroli has come a long way but it still needs a lot of love and optimizing, so if you are into python or efl, check out the code from git.paroli.org, join #paroli on irc and let's get crackin'. There are lots of things to do, opimd needs to be integrated and improved, the UI needs polishing, overall speed can be increased etc etc''

''More into Chat and email? Feel like writing a jabber/irc/xxx or email client that really fits the screen? Or do you know of one? Let's hear about it. This device has a lot of potential and we are so close to reaching the far corners, the kernel is in good shape, the framework is doing great and telephony apps such as paroli or the shr suite are steadily improving.''

''So, get your Freerunner in shape again. Flash it with a nice current distro and let it do what it was meant to do :)''

''Let's make Om2009 a community product, something all of us can be proud of and say "we did this".''

Mirko/Openmoko at http://lists.openmoko.org/pipermail/community/2009-May/048061.html)

* [http://n2.nabble.com/Om2009-release-plan-tp2410042p2410042.html OM2009 release plan]

* [[Om_2009_get_active]]
* [[Paroli-issues]]

* Paroli: http://www.paroli-project.org/ and [[Paroli]]
* FSO: http://www.freesmartphone.org and [[OpenmokoFramework]]

* BUILDS: [http://downloads.openmoko.org/distro/testing/ Testing] and [http://downloads.openmoko.org/distro/unstable/ Daily/unstable]

=== Reporting Bugs ===

Please enable debugging as [[Om_2009#Using_OM2009|instructed above]]. Attaching frameworkd.log and paroli.log will aid in solving the bug.

Please search the bug list for you issue before adding it to trac. Some of these issues might be [[Paroli]] or FSO issue so you can also check their tracs for solutions or discussions.

* https://docs.openmoko.org/trac (Use the Om2009 tag so that we can track it against this release.)
* http://trac.freesmartphone.org/wiki
* http://www.paroli-project.org/trac

[[Category:Om 2009| ]]

Om 2009

2009-06-17T20:44:16Z

Janvlug: /* Installing */ Improved bind-home instructions

{{Languages|Om 2009}}
[[Image:Paroli.png|thumb|Screenshot of Paroli, the GSM app of OM2009]]
'''Om 2009''' is the next version of the official Openmoko distribution. The latest release is testing5 from June 16th, 2009.

Om2009 testing5 already has all the features most people need for daily phone usage: SMS, calling, phone book, call log, charging, suspend&resume, wifi gui, audio profiles, etc.

Om2009 is currently under developement and should be released in Summer 2009 to replace [[Om 2008]]. It is based on [[FSO|freesmartphone.org]] milestone 5.5 framework and use [[Paroli]] as GSM software.

== Installing ==

=== GSM firmware ===
* If you've not updated your GSM chip firmware, it's Moko8 and REALLY needs to be updated. See [[GSM/Flashing#uSD-card_Image_.28GTA02_only.29|GSM flashing]]

=== bind-home ===
You can add a bind-home directory to the first partition (must be ext2 or ext3 ) of your SD card. On the OM2009 boot it will be mounted as /home/root. This way you can reflash your phone without losing anything in your home directory ([[Paroli]] contacts and settings, maps, etc)

Make sure there isn't a bind-home directory first
ls /media/card/bind-home
If this exists you are already using bind-home, otherwise keep following the directions below
mv /home/root /media/card/bind-home
mkdir /home/root
reboot

=== qi/uboot/OM2009 ===
Also update to the latest versions of [[qi]] or [[Bootloader|uboot]] bootloaders
The latest OM2009 and qi/uboot images are available at http://downloads.openmoko.org/distro/testing/

Installing OM2009 is simple as flashing an image. Actually that's what you need to do.

# Download! You need the correct fso-paroli-image and uImage.bin files for your device. There are also rootfs tarballs for installing onto an SD card. [http://downloads.openmoko.org/distro/testing/NeoFreerunner Freerunner] or [http://downloads.openmoko.org/distro/testing/Neo1973 Neo1973]
# Flash! Detailed instructions for [[Flashing_the_Neo_Freerunner|Freerunner]] and [[Flashing_the_Neo_1973|Neo1973]].
# Start! The image will boot into fullscreen Paroli and all of the features listed above will be available. To learn more about Paroli, see [[Paroli]]

Boot AND REBOOT! The first time it boots there some problems might occur but they're gone after the second boot.

== Using OM2009 ==
'''Write your best tips here!!'''

* To '''learn to use Paroli''', the phone software, go to [[Paroli#FAQ]]
* To '''import vcard -contacts''' to Paroli, check [http://www.mail-archive.com/support@lists.openmoko.org/msg04770.html this]
* '''To prevent suspending when USB plugged in''': unplug usb until LED goes out, then plug usb in: you need to keep the device awake by touching the screen until the LED comes back on. (bug: http://trac.freesmartphone.org/ticket/381)
* '''Angstrom feeds''' Contain many useful packages including mplayer and ffmpeg. Run these commands to add the angstrom feeds '''NOTE:''' You will not be able to upgrade OM2009 after this, it will break!
echo "arch base 50" > /etc/opkg/angstrom-feed.conf
echo "src/gz base http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base" >> /etc/opkg/angstrom-feed.conf

==== Audio quality during call ====
* Audio quality is good by default for some Freerunners. Some units need a new audio profile:
wget http://docs.openmoko.org/trac/raw-attachment/ticket/2121/gsmhandset.state.new -O /usr/share/openmoko/scenarios/gsmhandset.state
* More info can be found here: http://wiki.openmoko.org/wiki/Neo_Freerunner_audio_subsystem

==== Audio problems ====
* If you have problems with audio, try this:
modprobe snd-pcm-oss
* If audio works, load this module on boot:
echo "snd-pcm-oss" > /etc/modutils/snd-pcm-oss
update-modules
* Problems:
** Allowing the FR to suspend or having the screen blackout while using mplayer will sometimes crash the FR
** Plugging in the headset will stop audio from playing out of the phone's speaker. Audio will not return until the phone is shut off or you receive or make a call

== Bugs / missing features ==

* Screen lock is missing
** currently X screen saver is used during screen blank

* (Paroli) GUI to change ring tones missing
* (Paroli) GUI for Bluetooth missing
* Led indication for missed calls or sms missing
* Battery indicator support for GTA01 broken

* Boot time needs to be reduced to less than 2 minutes
** install udev-static-devices - caveat you lose bind-home
** use readahead to cache python dirs before starting framework and paroli
** use readahead to cache dirs for X
** remove unneeded startup programs ( ie portmap )
** prime GSM during init for paroli's use

* gsm0710muxd: "Modem does not respond to AT commands" [http://docs.openmoko.org/trac/ticket/2257 #2257]
* oeventsd rules ignored [http://trac.freesmartphone.org/ticket/381 FSO #381]

== Development ==
'' When we set the very limited goals of OM2009 we had two goals in mind:''

''1. Give those members of the community who only wanted a daily phone, a distro they could use'' 
''2. Introduce technology that would allow the community to come together and improve on these basics''

''Community interaction, open development and user driven decision making are at the core of Om2009. Going forward this will be an effort with the community for the community. I invite you to join the effort to make om2009 with paroli the best Om-labeled distribution for the Freerunner. ''

'''How can you help?'''

''Test the distro, let us know about bugs you find, or even fix them and send us patches.''

''Tell us about your experiences using om2009, what should we change, where can we improve?''

''Paroli has come a long way but it still needs a lot of love and optimizing, so if you are into python or efl, check out the code from git.paroli.org, join #paroli on irc and let's get crackin'. There are lots of things to do, opimd needs to be integrated and improved, the UI needs polishing, overall speed can be increased etc etc''

''More into Chat and email? Feel like writing a jabber/irc/xxx or email client that really fits the screen? Or do you know of one? Let's hear about it. This device has a lot of potential and we are so close to reaching the far corners, the kernel is in good shape, the framework is doing great and telephony apps such as paroli or the shr suite are steadily improving.''

''So, get your Freerunner in shape again. Flash it with a nice current distro and let it do what it was meant to do :)''

''Let's make Om2009 a community product, something all of us can be proud of and say "we did this".''

Mirko/Openmoko at http://lists.openmoko.org/pipermail/community/2009-May/048061.html)

* [http://n2.nabble.com/Om2009-release-plan-tp2410042p2410042.html OM2009 release plan]

* [[Om_2009_get_active]]
* [[Paroli-issues]]

* Paroli: http://www.paroli-project.org/ and [[Paroli]]
* FSO: http://www.freesmartphone.org and [[OpenmokoFramework]]

* BUILDS: [http://downloads.openmoko.org/distro/testing/ Testing] and [http://downloads.openmoko.org/distro/unstable/ Daily/unstable]

=== Reporting Bugs ===

Please enable debugging as [[Om_2009#Using_OM2009|instructed above]]. Attaching frameworkd.log and paroli.log will aid in solving the bug.

Please search the bug list for you issue before adding it to trac. Some of these issues might be [[Paroli]] or FSO issue so you can also check their tracs for solutions or discussions.

* https://docs.openmoko.org/trac (Use the Om2009 tag so that we can track it against this release.)
* http://trac.freesmartphone.org/wiki
* http://www.paroli-project.org/trac

[[Category:Om 2009| ]]

Alternative FSO GIT repository

2009-06-17T09:26:31Z

Janvlug: Created link to official git repository.

The official FSO git repository is this one:

[http://git.freesmartphone.org git.freesmartphone.org]

Currently you can't use freesmartphone.org repository via http:// , so it can be a problem for users behind restrictive firewall.
[http://freesmartphone.org freesmartphone.org] git repository is mirrored to [http://repo.or.cz repo.or.cz]. Instead of:
<pre>
git clone git://git.freesmartphone.org/zhone
</pre>
you can use:
<pre>
git clone http://repo.or.cz/r/zhone
</pre>
And so on.
Have fun!

[[Category:Application Developer]]
[[Category:FSO]]

Om 2009

2009-05-26T11:51:36Z

Janvlug:

[[Image:Paroli.png|thumb|Screenshot of Paroli, the GSM app of OM2009]]
'''Om 2009''' is the next version of the official Openmoko distribution. It is currently under developement and should be released in Summer 2009 to replace [[Om 2008]]. It will be based on [[FSO|freesmartphone.org]] milestone 5.5 framework and use [[Paroli]] as GSM software.

=== Features Status ===

Below is the feature list for Om 2009. It's broken down into features that have been implemented and need testing, and features that still need to be finished. Since [[Paroli]] is the chosen phone application, many of the features come straight from Paroli project.

==== Implemented ====

* incoming and outgoing phone calls
* sms incoming and outgoing
* simple phone book (no images)
* call log
* charging
* suspend and resume
* resume speed < 2 seconds - this is close but waiting on a kernel bug
* battery indicator - works for gta02 battery
* gsm indicator
* switch to elementary
* wifi GUI
* scrolling in UI - fixed by migrating from etk to elementary
* switching profiles
* in-call volume adjustment
* settings tool (this needs to be enabled by editing /etc/paroli/paroli.cfg)

==== Not Yet Implemented or Broken ====

* boot time < 2 minutes - currently examining ways to speed this up
** install udev-static devices - caveat you lose bind-home
** use readahead to cache python dirs before starting framework and paroli
** use readahead to cache dirs for X
** remove uneeded startup programs ( ie portmap )
** prime GSM during init for paroli's use
* screen lock
** currently X screen saver is used during screen blank
* user changeable ring tones - works via command line
* bluetooth - support in FSO milestone 5.5, needs GUI
* led indication for missed calls or sms
* GTA01: battery indicator doesn't work for gta01 battery

==== Bug List and Known Issues ====

* gsm0710muxd: "Modem does not respond to AT commands" [http://docs.openmoko.org/trac/ticket/2257 #2257]
* oeventsd rules ignored [http://trac.freesmartphone.org/ticket/381 FSO #381]
* After some received call or sms, the phone does not suspend anymore [http://trac.freesmartphone.org/ticket/435 FSO #435]
* Problem at Display->Profile: can't get back to illume, and illume, paroli or paroli-illume all look exactly the same
** WORKAROUND: Reboot. The first time it boots there is a problem but it's OK after that.

== Installing ==

* If you've not updated your GSM chip firmware, it's Moko8 and REALLY needs to be updated. See [[GSM/Flashing#uSD-card_Image_.28GTA02_only.29|GSM flashing]]
* Also update to the latest versions of [[qi]] or [[Bootloader|uboot]] bootloaders
* You can add a bind-home directory to the first partition (must be ext2 or ext3 ) of your SD card. On the OM2009 boot it will be mounted as /home/root. This way you can reflash your phone without losing anything in your home directory ( [[Paroli]] contacts and settings, maps, etc )

The latest OM2009 and qi/uboot images are available at http://downloads.openmoko.org/distro/testing/

Installing OM2009 is simple as flashing an image. Actually that's what you need to do..

# Download! You need the correct fso-paroli-image and uImage.bin files for your device. There are also rootfs tarballs for installing onto an SD card. [http://downloads.openmoko.org/distro/testing/NeoFreerunner Freerunner] or [http://downloads.openmoko.org/distro/testing/Neo1973 Neo1973]
# Flash! Detailed instructions for [[Flashing_the_Neo_Freerunner|Freerunner]] and [[Flashing_the_Neo_1973|Neo1973]].
# Start! The image will boot into fullscreen Paroli and all of the features listed above will be available. To learn more about Paroli, see [[Paroli]]

== Using OM2009 ==
'''Write your best tips here!!'''
* To learn to use Paroli, the phone software, go to [[Paroli#FAQ]]
* To have log directory that isn't cleared when you reboot, the /var/log symlink needs to be turned into a directory:
rm /var/log
mkdir /var/log

== Development ==
'' When we set the very limited goals of OM2009 we had two goals in mind:''

''1. Give those members of the community who only wanted a daily phone, a distro they could use'' 
''2. Introduce technology that would allow the community to come together and improve on these basics''

''Community interaction, open development and user driven decision making are at the core of Om2009. Going forward this will be an effort with the community for the community. I invite you to join the effort to make om2009 with paroli the best Om-labeled distribution for the Freerunner. ''

'''How can you help?'''

''Test the distro, let us know about bugs you find, or even fix them and send us patches.''

''Tell us about your experiences using om2009, what should we change, where can we improve?''

''Paroli has come a long way but it still needs a lot of love and optimizing, so if you are into python or efl, check out the code from git.paroli.org, join #paroli on irc and let's get crackin'. There is lots of things to do, opimd needs to be integrated and improved, the UI needs polishing, overall speed can be increased etc etc''

''More into Chat and email? Feel like writing a jabber/irc/xxx or email client that really fits the screen? Or do you know of one? Let's hear about it. This device has a lot of potential and we are so close to reaching the far corners, the kernel is in good shape, the framework is doing great and telephony apps such as paroli or the shr suite are steadily improving.''

''So, get your Freerunner in shape again. Flash it with a nice current distro and let it do what it was meant to do :)''

''Let's make Om2009 a community product, something all of us can be proud of and say "we did this".''

Mirko/Openmoko at http://lists.openmoko.org/pipermail/community/2009-May/048061.html)

* [http://n2.nabble.com/Om2009-release-plan-tp2410042p2410042.html OM2009 release plan]

* [[Om_2009_get_active]]
* [[Paroli-issues]]

* Paroli: http://www.paroli-project.org/ and [[Paroli]]
* FSO: http://www.freesmartphone.org and [[OpenmokoFramework]]

* BUILDS: [http://downloads.openmoko.org/distro/testing/ Testing] and [http://downloads.openmoko.org/distro/unstable/ Daily/unstable]

=== Reporting Bugs ===

Please enable debugging as [[Om_2009#Using_OM2009|instructed above]]. Attaching frameworkd.log and paroli.log will aid in solving the bug.

Please search the bug list for you issue before adding it to trac. Some of these issues might be [[Paroli]] or FSO issue so you can also check their tracs for solutions or discussions.

* https://docs.openmoko.org/trac (Use the Om2009 tag so that we can track it against this release.)
* http://trac.freesmartphone.org/wiki
* http://www.paroli-project.org/trac

[[Category:Om 2009| ]]

Paroli

2009-05-26T11:49:48Z

Janvlug:

[[Image:Paroli.png|thumb|Paroli Screenshot]]
Paroli is a new approach to application development on the Openmoko phones. It is actually able, in combination with [[Om2009]] distribution to make Freerunner work as a simple phone.
It's based on top of the [[OpenmokoFramework|FSO framework]] and enables the use of it via a core and several services.

For more information please visit [http://www.paroli-project.org/ Paroli website]

If you are interested in helping out with paroli, contribute code or test or or or ... Let us know! Send a mail to [mailto:mirko@openmoko.com Mirko] and/or visit #paroli IRC channel!

== Stuff that works ==

Paroli actually makes FR a simple, very working phone!!
* ability to turn off PIN check & change pin! (The first distro that does it ?)
* Connecting to WLAN (with WPA, WPA2, WEP)
* suspend & resume
* etc etc

==Installation / download ==

=== Full distro ===

To install the [[Om2009]] distribution download the uImage and fso-paroli-image from http://downloads.openmoko.org/distro/testing/NeoFreerunner/

=== Only the package ===
In order to get the package from unstable you'll need to adjust the configuration of opkg:

<nowiki>echo src/gz openmoko-unstable-armv4t http://downloads.openmoko.org/repository/unstable/armv4t > /etc/opkg/om-unstable.conf</nowiki>

Then do an opkg-update and opkg install paroli.

This should get you the newest version.

=== Download ===

Download paroli from
[http://downloads.freesmartphone.org/fso-milestone5/feeds//armv4t/paroli_0.2.1+gitr7a2fdc16174258e9276e7c2d80f500b4dd624442-r0_armv4t.ipk http://downloads.freesmartphone.org/fso-milestone5/feeds//armv4t/paroli_0.2.1+gitr7a2...442-r0_armv4t.ipk]

or from http://downloads.openmoko.org/distro/experimental/

=== Getting the sources ===

git clone http://git.paroli-project.org/paroli.git/

== FAQ ==

''' I/O... what's that..'''
* I/O is the phone log. It'll show your dialled, answered and missed calls.
** why do you name something so fundamentally necessary, with such an obscure name?
* Msgs is the place to send & read messages (SMS)
* Tele is the dialler
* People is the phone book

'''How do I get to settings?'''

Go to the home-screen (the one with the big clock) and hold the AUX-button pressed for 2 seconds.

'''How do I get Illume?'''

Open settings, click on "display" and then hit "profile" (once) and be patient, after some rumbling on the screen you will have the standard illume look with paroli in windowed mode.

''' How do I shut it down? '''

Hold the power button down for 10 seconds. It will not give you a visual feedback, it just starts shutting down.

''' How do I change the audio profile '''

* When not on call, short pressing of AUX changes between audio profiles (default / silent).
* When on call, it changes the speaker volume (20-40-60-80-100%). Using level over 80 might cause some echo.

''' Where are the messages folder? Drafts, sent etc.?

'''How do I lock the screen, without going to suspend?

''' How do i set the alarm?

''' How do I contribute? '''

See [[Om 2009 get active#Paroli phone software|Paroli section on Om2009 "get active" page]].

== Known issues ==
See wiki page [[paroli-issues]] for the list of known issues and vital feature requests.

Bug tracker is available at http://www.paroli-project.org/trac

[[Category:Paroli]]

Talk:Flashing the GSM Firmware

2009-05-16T10:03:22Z

Janvlug: /* Flash using uSD card image worked! */

'''please refer to this very wikipage regarding -oo and flowcontrol'''
Stephan_schmidt had exactly same issue and we fixed it yesterday, using these modifications

WARNING : Flash failed ! From Sleg on 2008/11/25 :

I had a problem during flashing my firmware ... I started again the module by typing 's3c24xx-gpio b7=1' as said in the wiki, and it started to flash the firmware. While it was flashing (I could see the progress ...) I failed by a 'Flash operation timeout'

The GSM module seems to not respond anymore :'(

If I retry, I get :

root@om-gta02:/usr/sbin# FLUID_PORT=/dev/ttySAC0 FLUID_FLOWCONTROL=h fluid.exe \
> -oO -b 115200 \
> -f $HOME/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0
FLUID Revision 2.27, (23 Aug 2004). Copyright Texas Instruments, 2001-2004.
Reading image file: '/home/root/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0' (2138kB) ok
Bootloader:

But nothing append even if I start the module by typing in another terminal 's3c24xx-gpio b7=1'

Can somebody please help me ??
sleg AT tsleg -DOT- com

'''Thanks to Stefan Schmidt on the kernel mailing list'''
My GSM went back !

here is what I did :
(Without FLOWCONTROL and with -oo to choose the ROM bootloader)

root@om-gta02:~# opkg install http://people.openmoko.org/joerg/calypso_moko_FW/fluid_0.0+svn20070817-r2_armv4t_eabi.ipk
Downloading http://people.openmoko.org/joerg/calypso_moko_FW/fluid_0.0+svn20070817-r2_armv4t_eabi.ipk
Installing fluid (0.0+svn20070817-r2) to root...
Configuring fluid
root@om-gta02:~# opkg install http://people.openmoko.org/joerg/calypso_moko_FW/s3c24xx-gpio_1.0+svnr4130-r2.1_armv4t.ipk
Downloading http://people.openmoko.org/joerg/calypso_moko_FW/s3c24xx-gpio_1.0+svnr4130-r2.1_armv4t.ipk
Multiple packages (s3c24xx-gpio and s3c24xx-gpio) providing same name marked HOLD or PREFER. Using latest.
Installing s3c24xx-gpio (1.0+svnr4130-r2.1) to root...
Configuring s3c24xx-gpio
root@om-gta02:~# wget http://people.openmoko.org/joerg/calypso_moko_FW/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0
Connecting to 10.194.51.41:3128 (10.194.51.41:3128)
gsm_ac_gp_fd_pu_em_c 100% |**************************************************************************************************| 5419k 00:00:00 ETA
root@om-gta02:~# echo 0 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
root@om-gta02:~# echo 1 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
root@om-gta02:~# cd /usr/sbin
root@om-gta02:/usr/sbin# FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -b 115200 -f $HOME/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0
FLUID Revision 2.27, (23 Aug 2004). Copyright Texas Instruments, 2001-2004.
Reading image file: '/home/root/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0' (2138kB) ok
Bootloader: (reset target) (ROM, version ?) ok
Checksumming (269 * 8kB = 2152kB): ok
Flash Detect: (0xEC, 0x22A0) Samsung K5A3240CT ok
Program: (31 sectors, 243*8k=1944k) (******************) ok
root@om-gta02:/usr/sbin#

And to wake up the GSM in another ssh window :

root@om-gta02:~# echo 0 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
root@om-gta02:~# echo 1 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on

----

i recive instead of

"Program: (34 sectors, 267*8k=2136k) (*******************) ok"

this

"Program: (0 sectors, 0*8k=0k) () ok"

iam currently reflashing the old firmware, that seems to work.

iam using an non-us gsm-freerunner (recived yesterday so most likely the latest hardwar)

thakoman

[2008-11-19 04:46:39] <Wonka> DocScrutinizer: flashing to moko10-beta2 went though cleanly, i already had working ppp connects with the previously non-working SIM.

[2008-11-19 04:48:24] <Wonka> DocScrutinizer: but there are still problems... more often than not, the GSM chip does not answer. pppd opens the device, gets "AT command interpreter ready", utters "AT\n" and gets nothing. power off, power on, reset on, reset off, try gain... sometimes it works, but mostly not.

O2 UK prepay 3G SIM works with moko10-beta2, was previously not
detected. T-mobile UK prepay SIM and old Orange UK contract SIM work
with both old and new. Testing so far is cursory at best, but looks good.
[quote: Alastair Johnson on devel-ML]

[2008-11-21]
I flashed 6 out of our 8 Freerunner V.6 according to the GSM/Flashing- guide. I had no problems and the previously useless 3G- SIMs are
working fine now. It seems like the 3G- SIM Issue, our beloved #666, is solved. You should point it out clearly. I heard a lot of users complain about this. The solution is simple and well hidden on the website. By the way, i have new 3G- SIM cards of the following german providers running without problems (O2, T- Mobile, E-Plus, Vodafone). Before the flashing procedure the Vodafone cards were not detected. Good work guys... thanks!
[[User:Reiner|Reiner]]

== Works now with new gsm firmware moko10beta2 with O2 in Germany ==

Very great, I can make calls now after waiting for 5 month, big surprise :).
Thanks a lot!
--[[User:Kevin|Kevin]] 15:18, 20 November 2008 (UTC)

I'm very happy to be able to report that the update went smoothly for
me (without yielding any surplus "building materials") and that a new
O2 SIM from http://freesim.o2.co.uk/ which never worked in my
Freerunner before now seems to be working fine. Great work!

Tom

--

Thomas White
Department of Materials Science and Metallurgy
Electron Microscopy Group (PhD Student)
University of Cambridge / Downing College

The flash worked without a hitch for me and now I am able to use a Vodafone
prepaid SIM in my 850MHz unit while back in Europe. I am running Om2008.9
with the 20081023 FDOM modifications applied.

Great job!

-Jacob

Hello!

Replying under subject Success :)
I've combined what Michael said (few echo 1 >> .... and echo 0 >> ....
in the other terminal) and Joerg's suggestion (-oo instead of -oO) and
it worked perfectly. The upgrade to moko10 was done.

So I can confirm the freerunner now works with Simobil's (Slovenian
GSM operator) SIM.

Great job and thanks to all that took the time to do it.

Boštjan

== State SD-image? ==

Any update on a SD-image for GSM flashing?

[joerg 2008-12-10 02:43:32]

We're busy on this. Follow wiki instructions, or come up with an automatism by yourself. Expect any update on january.

== bug #1024 ==
[Tebra 2009-01-13 07:45]

Hi. Are you working on moko11 to fix #1024 bug?
Because of that bug I can't use android distribution.

== German/Vodafone ==

Got a new Vodafone Prepaid SIM-Card. Didn't work with QTExtended nor with Android until I've used the procedure to upgrade the GSM-Firmware. Looks like it's not just "swiss sim cards".
Regards, --[[User:Rtreffer|Rtreffer]] 17:14, 25 January 2009 (UTC)

== Broken GTA01bv4 GSM Modem Fix ==

I recently had to do a special process to recover my GTA01bv4 after breaking the gsm modem with a failed flash. The process is actually fairly simple.

* Unplug USB and remove the battery for about 10s to ensure that the GSM chipset is powered off, then replace the battery and re-connect the USB
* boot up from a distro that is neutered so that it does not access or turn on the gsm modem at all
* issue this stty command twice:
stty 0:4:18b2:8a00:0:0:7f:15:4:0:0:0:0:0:0:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0 -F /dev/ttySAC0
* issue this fluid command:
FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -od13,13 -vvv -b115200 -f $HOME/filename.m0
* in another ssh session, issue this command:
echo 1 > /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on

After this, the flashing proceeded as expected, and all seems alright. I'll have to push a new distro to it to be certain, but all looks good so far.
[[User:Quinn Storm|Quinn Storm]] 22:39, 16 March 2009 (UTC)

Added note about battery removal. [[User:Mmontour|Mmontour]] 01:51, 17 March 2009 (UTC)

== Flash using uSD card image worked! ==
I'm now able to use my "MobilePlus" (Mobistar network) SIM which failed to register previously.
Thanks for this excellent tool!

--[[User:M8ram|M8ram]] 15:16, 26 April 2009 (UTC)

== What is FLUID? ==
Please create a link to an explanation of what FLUID is when FLUID is first mentioned at the top of the page.

Android

2009-04-13T21:34:05Z

Janvlug: /* Introduction */ Fixed link.

{{Languages|Android}}
{{Distributions|Android}}

{|align=right
|__TOC__
|}
[[Image:Android-logo.png]]
= Introduction =
This page is the central place for documentation about Android on the [[Neo1973 Hardware|Neo 1973]] and [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] handsets.

[http://code.google.com/android/ Android] is a software stack for mobile devices developed by the [http://www.openhandsetalliance.com/ The Open Handset Alliance.] Although Android is publicized as being [[open source software]] (most of the source code has been released) parts of the code have not been released yet.

A lot of work is being done to get Android functioning properly on the [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] and it is likely, in the near future, to be the distribution most suited for using the FreeRunner as a phone.

= Usage =
See: [[Android usage]] for detailed instructions on using Android on the FreeRunner.

Android is gaining functionality on the FreeRunner all the time and with Michael Trimarchi's [http://panicking.kicks-ass.org/download/ (panicking)] images it is possible to use as an everyday phone. Prerequisites for the best success seem to be:

* Use the jffs version 14.6 and the kernel v17.
* Uboot

You can then hope to achieve :

* GSM calls
* SMS
* Adding, removing and importing contacts
* GPRS
* Wi-Fi

Caveats

* Volume during voice calls is very low.
* Wi-Fi does not reconnect after sleep - [http://wiki.openmoko.org/wiki/Android_usage#Wifi setup]
* You have to disable PIN security on your SIM card.

[http://spreadsheets.google.com/ccc?key=popRpaZG1txEXGHDDboxtIA&hl=en_GB Android function sheet]

== External Links ==

* [http://digg.com/linux_unix/Video_demo_of_Freerunner_running_Android_Cupcake_Tutorial Short Video demo of Android] on [[FreeRunner]] to show how usable it is.

* http://andappstore.com/

* http://slideme.org/

* http://www.openintents.org/

= Installation =

See: [[Android on Freerunner]] for how to [[flash]] your FreeRunner with Android
 You can also install the Koolu beta 4 rc1 directly from SD card onto the NAND see [http://koolu.com/~marcelo/README]

= Development =
See: [[Android porting]]

There are developers being paid to work on the port by [http://koolu.com/ Koolu.]
For details on the project source and some real detailed instructions on building the source, see the [http://trac.koolu.org/ the Koolu Trac Website for Android]. 
There is a Android Freerunner Mailing list hosted by Koolu [http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org]

There is also some great unpaid work going on at [http://panicking.kicks-ass.org/blog/index.php Linux Embedded]

= News =
* 07 March 09 - Panicking released a cupcake [http://panicking.kicks-ass.org/download/ rootfs]
* 26 February 09 - As promised, Sean McNeil has released source code to [[GSM]] libraries [https://review.source.android.com/Gerrit#change,9013 Source]
* 20090204 Koolu releases its Beta3 Android [http://freerunner.android.koolu.com/release-files release].
** Changelog:
*** Added GPS library that supports GPS under Android
*** MAX_PROCESSES patch to enable more background processes to be run (fixes Pictures application)
*** Added Dalvik optimization setting
*** Started including 3rd party applications
*** Updated user interfaces for GPS and Bluetooth to match new kernel
*** Now report RSSI of Wifi signals to upper application layer
*** Enable libsoundpool compilation to support audible clicks

* 20090122 Koolu releases its Beta2 Android [http://freerunner.android.koolu.com/release-files release].

* 20081219 Koolu releases its Beta Android [http://forum.koolu.org/files/androidfs-koolu-1_0.jffs2 Image] and [http://forum.koolu.org/files/uImage-android-patched_bc2caff9cdef8a16.bin kernel].

* 20081202 [http://www.koolu.com Koolu], a Freerunner distributor, has released the source code of their Android port at [http://git.koolu.org http://git.koolu.org]. For details on the project source and some real detailed instructions on building the source, see the [http://trac.koolu.org/ the Koolu Trac Website for Android]. TODO: Find out where this link supposed to go->See the [[Android_porting#Building the Koolu Android Source]] instructions below for how to build an Android image for Freerunner.

* 20081104 The first Android-image has been successfully created by Sean McNeil! - sms and calling works, wifi and bluetooth doesn't. [http://onlinedev.blogspot.com/2008/11/porting-android-phase-3-done.html ''news-source'']

= See also =
* Videos : [http://digg.com/linux_unix/Video_demo_of_Freerunner_running_Android_Cupcake_Tutorial]
* [http://tw.youtube.com/watch?v=m4NbsLmF9j0 YouTube Video 1]
* [http://tw.youtube.com/watch?v=r6Op-7tNTiw YouTube Video 2]

[[Category:Distributions]]

Stable Hybrid Release

2009-03-31T14:06:54Z

Janvlug: /* Feature overview */

{{Languages|SHR}}
{{Distributions|SHR}}
{{SHR}}

== Why SHR exists ==
The [[Stable Hybrid Release]] (SHR) is intended to be a community driven distribution composed of the [[OpenmokoFramework|FSO]] and some basic applications, that can be configured to use several different graphical toolkits, for example GTK or EFL. SHR is based on the FSO build. At first, SHR was introduced in order to use the [[Openmoko2007.2]] GTK software in combination with the new [[OpenmokoFramework|FSO]], but things have changed.

====Why not just use plain FSO?====
[[FSO]] is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.

FSO is by far the most stable & usable release, if all you want is a phone. (I mean *all*. It just has a dialer, which is a demo application.)

FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.

Other people are supposed to put a front end on FSO. So that's what we're doing.

==Feature overview==

In the overview below are all the essential features and their status for the current '''out of the box''' SHR unstable distribution (latest+[http://en.wikipedia.org/wiki/Module_(Linux) modules]+updates). Green indicates that this part is well functioning, red indicates a known requirement which will be implemented later on and orange indicates functionality that can (and should) be fixed easily in the distribution for known fixes are available.

{| cellspacing="0" class="sortable wikitable" border="1" style="font-size: 85%; text-align: left; width: auto;"
|-
! Category
! Name
! Functionality
! Comments
|-
| System
| Power Management
| style="background:#88FF88;"| Suspend
| when slow, use [[Qi]]
|-
| System
| Package manager
| style="background:#FFDD88;"| Installing and upgrading packages
| style="background:#FFDD88;"| [http://trac.shr-project.org/trac/ticket/314 SHR ticket #314]
|-
| System
| Keyboard
| style="background:#FFDD88;"| Offer stylus and finger friendly keyboards
| style="background:#FFDD88;"| install alternative keyboards [http://trac.shr-project.org/trac/ticket/200 SHR ticket #200]
|-
| GSM
| Network
| style="background:#88FF88;"| Connect via SIM and PIN
|
|-
| GSM
| Network
| style="background:#FF8888;"| Flight mode
| style="background:#FF8888;"| [http://trac.shr-project.org/trac/ticket/333 SHR ticket #333]
|-
| GSM
| Dailer
| style="background:#88FF88;"| Receiving Call
| too big delay between selecting answer and stopping ring tone
|-
| GSM
| Dailer
| style="background:#88FF88;"| Making Call
|
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Overview Log (In, Out, Answered, All)
| style="background:#FF8888;"| should be in SHR Illume theme and is very slow in startup
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Making reply Call from Log
|
|-
| GSM
| Phone Log
| style="background:#FF8888;"| Sending reply SMS from Log
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Receiving SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Selecting SMS from Overview
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Viewing SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Sending new SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Sending reply SMS
|
|-
| GSM
| SMS
| style="background:#FF8888;"| Making reply Call
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Deleting SMS
|
|-
| GSM
| GPRS
| style="background:#FFDD88;"| Configuring and Enabling TCP/IP
| style="background:#FFDD88;"| 1) edit shr_gprs.py for credentials and gprs.py for provider 2) Settings->Connectivity: GPRS connect 3) Still not working
|-
| Shared
| Contacts
| style="background:#88FF88;"| Reading SIM contacts
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Selecting SIM contact from Overview
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Editing SIM contact
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Deleting SIM contact
| does not stay at position in list
|-
| Shared
| Contacts
| style="background:#FF8888;"| Quick lookup contact with keyboard
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Calling contact
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Sending SMS to contact
|
|-
| WiFi
| Ethernet
| style="background:#88FF88;"| Configuring and Enabling TCP/IP
| 1) Settings->Connectivity->WiFi radio=On 2) Mofi
|-
| WiFi
| MoFi
| style="background:#FFDD88;"| Network Manager
| style="background:#FFDD88;"| [http://trac.shr-project.org/trac/ticket/338 SHR ticket #338]
|-
| GPS
| Service
| style="background:#88FF88;"| Receiving GPS data
| automatically turned on
|-
| USB
| Ethernet
| style="background:#88FF88;"| Configuring and Enabling TCP/IP
| style="background:#FF8888;"| done automatically with insecure password
|-
| Audio
| Headset
| style="background:#FF8888;"| Handsfree calling
| headphones work, microphone does not work
|-
|}

== Install ==

Installing SHR is very easy. I will explain how to install the [http://build.shr-project.org/shr-testing/images/om-gta02/ testing] version of SHR for GTA02 (Freerunner). It is stable enough for a daily use. Stable version will be available soon ([http://blog.shr-project.org/ Stable announcement]), [http://build.shr-project.org/shr-unstable/images/om-gta02/?C=M;O=D unstable] (for the adventurous testers) is also available, but read [http://blog.shr-project.org/2009/03/time-for-testing.html this blog announcement] on why this is currently not recommended.

I suppose that you know how to use [http://wiki.openmoko.org/wiki/NeoTool NeoTool]

- the [[Qi]] bootloader (optional, u-boot should work as well)

- the [http://build.shr-project.org/shr-testing/images/om-gta02/uImage-om-gta02-latest.bin kernel]

- the root filesystem ([http://build.shr-project.org/shr-testing/images/om-gta02/shr-lite-image-om-gta02.jffs2 flash image] or [http://build.shr-project.org/shr-testing/images/om-gta02/shr-lite-image-om-gta02.tar.gz tarball])

You can view the sources [http://git.shr-project.org/git/ here].

== Connecting your FreeRunner to your computer ==
For the next configuration steps, you will need to type some commands. It is much easier to type on a real keyboard than on a touch screen.
So you need to connect your FR to you computer, and make a bridge to internet.
Use the [[USB Networking]] page for help about configuring your host computer.
NOTE: On first boot after flashing, USB networking can not work. If it's happening, simply reboot and try again.

== Setting local time ==
As any linux system, the UTC time is used by the system. First of all, adjust this time:
date -u -s 010220052009
Fri Jan 2 20:05:00 UTC 2009

Then, you need to "localise" your system.
Search for the appropriate country with:
opkg list | grep tzdata

then install the one corresponding to your area.
opkg install tzdata-europe

Then select your city (search the city available in /usr/share/zoneinfo/your-country, example Paris)
ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime

You can fully localise your system by installing the glibc-binary-localedata correponding to your langage. Search the ones available with:
opkg list | grep glibc-binary-localedata

install with (example for France)
opkg install glibc-binary-localedata-fr-fr

== Changing root password ==
SHR is shipped without root password (just press enter)

This is dangerous if you connect using USB. You need to activate the root password:

passwd

and type your selected password (2 times)

== Customize the RingTone ==
You need to have a file containing the RingTone you want for your FR. You can find some at [http://wiki.openmoko.org/wiki/Ringtones#svn.openmoko.org_ringtones RingTone]

Then transfer it to your FR :
scp file root@192.168.0.202:/usr/share/sounds/

Now you can select ringtone in SHR Settings.

== Sound Control ==

Up to now, there is no graphical interface to control the sound
=== Mic and HP ===
The first idea is to use alsamixer; bad idea! There are 94 controls, and your modifications will be lost at the next reboot.Finding documentation is not easy. Here is my understanding:
Scenari are used for each case. They are located in /usr/share/openmoko/scenarios/
- capturehandset.state
- gsmheadset.state
- headset.state
- voip-handset.state
- gsmhandset.state
- gsmspeakerout.state
- stereoout.state

Each file is a set of value for the 94 parameters. I have identified some:

- Control 48: internal mic of the tel (set to 2 or 3)

- Control 4 : internal speaker (set from 110 to 120)

- Control 49: headset mic

- Control 3 : headset speaker

Generic info to the Neo soundsystem:

* [[Neo 1973 audio subsystem]]
* [[Neo alsamixer#Settings_Descriptions|Neo alsamixer - Settings Descriptions]]
* [[Neo Freerunner audio subsystem]]

=== Ringing ===

You can define a short ringtone, repeated many times, or a long one, repeated 1 time

File: /etc/freesmartphone/opreferences/conf/phone/default.yaml

Parameter: ring-volume # Ring Volume control 0 (mini) to ? maxi)
Parameter: ring-length # min time for ringtone. Must be greater than the duration of you ringtone

File: /etc/freesmartphone/opreferences/schema/phone.yaml
Parameter: ring-loop # define the number of loop of ringtone to play

=== Message alert ===
File: /etc/freesmartphone/opreferences/conf/phone/default.yaml
Parameter: message-volume # Ring Volume control 0 (mini) to ? maxi)
Parameter: message-length # min time for message alert. Must be greater than the duration of you message alert

File: /etc/freesmartphone/opreferences/schema/phone.yaml
Parameter: message-loop # define the number of loop of incoming message music to play

== Known Issues ==
=== Phone ===

GSM network is lost after one day of uptime: restart your FR once a day!

=== Address Book ===

SHR is not implementing a PIM (Personal Information Manager) yet. Work is in progress, but to included in SHR testing this has some consequences on daily use:

* Only contacts on the SIM card are available.

* It is not possible to import a Vcard file.
** It seems to be possible with [gopher://gopher.fnordpol.de/9/data/DbusAccessScripts_0.0.0.tar.gz this] script written by [[User:Zem#DBus_Access_Scripts|Zem]].

== More Information ==

Visit:
* [http://blog.shr-project.org Blog]
* [http://trac.shr-project.org Trac (Bugtracker)]
* [http://git.shr-project.org Git (Sourcecode-repository)]
* [http://build.shr-project.org Buildhost (Downloads)]
* [http://shr-project.org/trac/wiki/Tweaks Tweaks (On the Wiki)]
* [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel SHR Development Mailing List]

[[Category:SHR]]

Talk:Community Updates/2009-03-06

2009-03-03T08:25:32Z

Janvlug: /* Community */

====='''Period 20, Feb~6, Mar, 2009'''=====

==Distributions ==
*'''[[FSO]] 5.1 have released'''. FSO milestone5 to fix some bugs that crept into the release, notably the "not working on bootloaders that mount the root partition read-only".

:The release has been built out of the fso/milestone5 OE branch. Get it at http://downloads.freesmartphone.org/fso-stable/milestone5.1/

* '''Om2009 release plan'''--On the release plan, Openmoko is going to put FSO milestone 5.5, the stable kernel, paroli and the new xorg-glamo drivers together and make most stable distro ever. The builds in March will be called Alpha builds, and will receive only partial testing. Start with Beta builds and full testing in April. From then on only critical features and bug fixes will be backported into the branch. At the end of May, release candidates (RC builds) will start generating.

==Applications ==

===Application Updates===
* '''[[GridPad]] 2.0 have released.'''
:GridPad is an alternative input method for entering text with your finger, a Simple Character Recognizer Software. It’s an approximation to a handwriting recognition program, but in the most simply way that you can think.
::* Install files: http://downloads.om.vptt.ch/GridPad/

::* More information in: [http://downloads.om.vptt.ch/GridPad/GridPad_User_Manual.pdf GridPad User Manual]

::* Code at: [http://svn.om.vptt.ch/trunk/GridPad http://svn.om.vptt.ch/trunk/GridPad]

* '''[[MokoGeocaching]] 0.2 released'''
:It's a litle gtk python script that searches the geocaching.com site for caches near your current position or a user specified lattitude and longitude and add the cache as a poi in tangogps.
:: The script can now:
::* get gps location from phone
::* user can manually set location
::* user can specified range
::* script can download matching geocaches and add as poi
::* read geocaching.com username and password from configuration file threaded gtk and downloading - but unfortunately not searching unicode support.
::* gui input for username and password

::* The package can be found here: http://www.opkg.org/package_141.html

::it only tested it on shr unstable.

* '''[[Voicenote]] 0.3 released'''
:At the new release, you can play the wav files you have recorded with voicenote (or other wav files), and go back the the 1st choice dialog (record or play?) after each action.
:If you want to read more, please visit http://wiki.openmoko.org/wiki/Voicenote .

* '''[[Sephora]] 0.2.2 released'''
:[[Sephora]] is a FreeRunner settings manager in PyGtk for XFCE. You can visit its [https://launchpad.net/sephora home page] to get more information.

* '''[[Neon]] 0.9.8 released'''
: Changes since 0.9.6 :

::* Smoother scrolling in filesystem browser
::* Added a "scrollbar" in filesystem browser. It doesn't allow to scroll the list, it's used only as an indicator of progression.
::* Window can be rotated now via accelerometers data.
::* Minor fixes and code cleanups

:As usual you can get it at : http://projects.openmoko.org/frs/?group_id=239

:BEWARE : If your system uses Python 2.6 (not 2.5) like SHR or FSO, you must install alternative package neon_0.9.8-r1_all_py2.6.ipk

* '''[[Kustomizer]] [http://www.kurppa.fi/freerunner/kustomizer_0.35 0.35] released'''-The major changes of this release is bug fixed , prevented many apps from installing.

==Tips and Tricks==
* In order to record audio, you can use special alsa state file and recording applications like [[Guitartune]], [[Monologue]] and [[Voicenote]]. If you want to get more ideas about how to record audio , You can get more inforamtion [[Recording audio|here]].

==Community ==
* '''moko 11 (Calypso GSM modem firmware) considered to be official'''
: Moko11 is considered to be "official". So far, received reports indicating that moko11 did indeed solve the problems it's supposed to address (i.e., lost wakeups and flow control.)

: The developer now also like to know if anything has gone wrong after installing moko11, e.g., if the changes in IO1 handling have introduced new wakeup problems. Everyone who's tried moko11-beta to please reply, either to the list or to [mailto:werner@openmoko.org Werner] in private.

: About the draft of moko11, the draft is [http://svn.openmoko.org/developers/werner/gsm/moko11/RELNOTES here].

* '''Help developing www.opkg.org'''
::[http://www.opkg.org Opkg.org] needs some developers to develop some features.

::For Opkg.org was not updated for two months, but there are still some features needed, like a better comment system with email notifications, for example. [mailto:tobias.kuendig@gmail.com Tobias]decided to publish the opkg.org source code, by this way, anyone who want to help making www.opkg.org even better than it is today, feel free to contact [mailto:tobias.kuendig@gmail.com Tobias].

===Event News===
[[Image:IEEE-LINUXeOMD.preview.jpg|align|right|200px]]

* '''[http://risto.kurppa.fi/blog/announcing-the-first-programming-competition-for-openmoko-phones/ programming competition for Openmoko phones]'''
::Announcement: March 2nd, 2009
::Registration deadline: March 8th (see below)
::Submission deadline: March 24th, 2009 07:00 UTC
::Required license: GPL v2
::Programming language: c/c++ (no python/bash)

* '''2009-03-02''' [http://risto.kurppa.fi/blog/announcing-the-first-programming-competition-for-openmoko-phones/ Programming competition for Openmoko phones]|Registration deadline: March 8th, submission deadline: March 24th, 2009 07:00 UTC.

* '''2009-03-01/03-31''' [http://wiki.openmoko.org/wiki/user:Harry Harry' Openmoko Survey] | Please help me with my free software and Openmoko related academic research | Harry Tsai of [http://www.cgu.edu.tw Chang Gung Universtiy]

* '''2009-03-11/12''' [http://www.osimworld.com/usa OSiM USA] | The Westin San Francisco, Market Street | Openmoko will give a speech

* '''2009-03-12/14''' [http://www.osidays.com/ OSI Tech Days 2009] | Chennai Trade Center, INDIA | Rakshat Hooja of IDA Systems will be speaking about Openmoko

* '''2009-03-13''' The first Italian National [http://www.neomeeting.tk NeoMeeting] in Milano.

* '''2009-03-13''' Freerunner Meeting in Politecnico di Milano University (Milan, Italy). Please visite [http://www.eshopen.com here] to get more information.

* '''2009-03-23/27''' [http://www.bits-apogee.org/ Apogee 2009] | Rakshat Hooja of IDA Systems will be speaking about Openmoko

Talk:Community Updates/2009-03-06

2009-03-02T08:46:16Z

Janvlug: /* Application Updates */

====='''Period 20, Feb~6, Mar, 2009'''=====

==Distributions ==
*[[FSO]] 5.1 have released. FSO milestone5 to fix some bugs that crept into the release, notably the "not working on bootloaders that mount the root partition read-only".

:The release has been built out of the fso/milestone5 OE branch. Get it at http://downloads.freesmartphone.org/fso-stable/milestone5.1/

==Applications ==

===New Applications===
* '''2009-02-20''' [http://www.kurppa.fi/freerunner/kustomizer_0.35 0.35 pre-release] - give it a try, more packages should now install, the bug was finally found.. Let me know if it works for you!

* Voicenote-Voicenote is a software which allows to record any sound from the microphone into a wav file. It is intended to be an easy and quick way to do so.

* [http://www.netsurf-browser.org/ netsurf]-A new web browser for FreeRunner.

* new Project - Sync with Evolution / notifier

===Application Updates===
* '''[[MokoGeocaching]] 0.2 released'''
:It's a litle gtk python script that searches the geocaching.com site for caches near your current position or a user specified lattitude and longitude and add the cache as a poi in tangogps.
:: The script can now:
::* get gps location from phone
::* user can manually set location
::* user can specified range
::* script can download matching geocaches and add as poi
::* read geocaching.com username and password from configuration file threaded gtk and downloading - but unfortunately not searching unicode support.
::* gui input for username and password

::* The package can be found here: http://www.opkg.org/package_141.html

::it only tested it on shr unstable.

* [[Voicenote]] 0.3 released
:At the new release, you can play the wav files you have recorded with voicenote (or other wav files), and go back the the 1st choice dialog (record or play?) after each action.
:If you want to read more, please visit http://wiki.openmoko.org/wiki/Voicenote .

* Sephora 0.2.2 available

==Tips and Tricks==
* [[Recording audio]]--

==Community ==
* '''moko 11 considered to be official'''
: Moko11 is considered to be "official". So far, received reports indicating that moko11 did indeed solve the problems it's supposed to address (i.e., lost wakeups and flow control.)

: The developer now also like to know if anything has gone wrong after installing moko11, e.g., if the changes in IO1 handling have introduced new wakeup problems. Everyone who's tried moko11-beta to please reply, either to the list or to [mailto:werner@openmoko.org Werner] in private.

: About the draft of moko11, the draft is [http://svn.openmoko.org/developers/werner/gsm/moko11/RELNOTES here].

* '''Help developing www.opkg.org'''
::[http://www.opkg.org Opkg.org] needs some developers to develop some features.

::For Opkg.org was not updated for two months, but there are still some features needed, like a better comment system with email notifications, for example. [mailto:tobias.kuendig@gmail.com Tobias]decided to publish the opkg.org source code, by this way, anyone who want to help making www.opkg.org even better than it is today, feel free to contact [mailto:tobias.kuendig@gmail.com Tobias].

====Event News====

* Munich Stammtisch was a nice meeting as well!

http://freeyourphone.de/portal_v1/viewtopic.php?f=13&t=660&st=0&sk=t&sd=a&start=45#p9531

Not that crowded (4 freerunners) as Karlsruhe.

And: it will be repeated in 1-2 months!

===Branch info ===

Hi all, i have just pushed a new branch on kernel repo which will have
the development efforts we are doing on the DRM kernel driver. It is
called drm-tracking and is based on Tom's approach (thanks!).

Talk:Community Updates/2009-03-06

2009-03-02T08:45:43Z

Janvlug: /* Application Updates */

====='''Period 20, Feb~6, Mar, 2009'''=====

==Distributions ==
*[[FSO]] 5.1 have released. FSO milestone5 to fix some bugs that crept into the release, notably the "not working on bootloaders that mount the root partition read-only".

:The release has been built out of the fso/milestone5 OE branch. Get it at http://downloads.freesmartphone.org/fso-stable/milestone5.1/

==Applications ==

===New Applications===
* '''2009-02-20''' [http://www.kurppa.fi/freerunner/kustomizer_0.35 0.35 pre-release] - give it a try, more packages should now install, the bug was finally found.. Let me know if it works for you!

* Voicenote-Voicenote is a software which allows to record any sound from the microphone into a wav file. It is intended to be an easy and quick way to do so.

* [http://www.netsurf-browser.org/ netsurf]-A new web browser for FreeRunner.

* new Project - Sync with Evolution / notifier

===Application Updates===
* '''[[MokoGeocaching]] 0.2 released'''
:It's a litle gtk python script that searches the geocaching.com site for caches near your current position or a user specified lattitude and longitude and add the cache as a poi in tangogps.
:: The script can now:
::* get gps location from phone
::* user can manually set location
::* user can specified range
::* script can download matching geocaches and add as poi
::* read geocaching.com username and password from configuration file threaded gtk and downloading - but unfortunately not searching unicode support.
::* gui input for username and password

::* The package can be found here: http://www.opkg.org/package_141.html

::it only tested it on shr unstable.

* [[Voicenote]] 0.3 released
:At the new release , you can play the wav files you have recorded with voicenote (or other wav files), and go back the the 1st choice dialog (record or play?) after each action.
:If you want to read more , please visit http://wiki.openmoko.org/wiki/Voicenote .

* Sephora 0.2.2 available

==Tips and Tricks==
* [[Recording audio]]--

==Community ==
* '''moko 11 considered to be official'''
: Moko11 is considered to be "official". So far, received reports indicating that moko11 did indeed solve the problems it's supposed to address (i.e., lost wakeups and flow control.)

: The developer now also like to know if anything has gone wrong after installing moko11, e.g., if the changes in IO1 handling have introduced new wakeup problems. Everyone who's tried moko11-beta to please reply, either to the list or to [mailto:werner@openmoko.org Werner] in private.

: About the draft of moko11, the draft is [http://svn.openmoko.org/developers/werner/gsm/moko11/RELNOTES here].

* '''Help developing www.opkg.org'''
::[http://www.opkg.org Opkg.org] needs some developers to develop some features.

::For Opkg.org was not updated for two months, but there are still some features needed, like a better comment system with email notifications, for example. [mailto:tobias.kuendig@gmail.com Tobias]decided to publish the opkg.org source code, by this way, anyone who want to help making www.opkg.org even better than it is today, feel free to contact [mailto:tobias.kuendig@gmail.com Tobias].

====Event News====

* Munich Stammtisch was a nice meeting as well!

http://freeyourphone.de/portal_v1/viewtopic.php?f=13&t=660&st=0&sk=t&sd=a&start=45#p9531

Not that crowded (4 freerunners) as Karlsruhe.

And: it will be repeated in 1-2 months!

===Branch info ===

Hi all, i have just pushed a new branch on kernel repo which will have
the development efforts we are doing on the DRM kernel driver. It is
called drm-tracking and is based on Tom's approach (thanks!).

Talk:Community Updates/2009-03-06

2009-03-02T08:44:44Z

Janvlug: /* Distributions */

====='''Period 20, Feb~6, Mar, 2009'''=====

==Distributions ==
*[[FSO]] 5.1 have released. FSO milestone5 to fix some bugs that crept into the release, notably the "not working on bootloaders that mount the root partition read-only".

:The release has been built out of the fso/milestone5 OE branch. Get it at http://downloads.freesmartphone.org/fso-stable/milestone5.1/

==Applications ==

===New Applications===
* '''2009-02-20''' [http://www.kurppa.fi/freerunner/kustomizer_0.35 0.35 pre-release] - give it a try, more packages should now install, the bug was finally found.. Let me know if it works for you!

* Voicenote-Voicenote is a software which allows to record any sound from the microphone into a wav file. It is intended to be an easy and quick way to do so.

* [http://www.netsurf-browser.org/ netsurf]-A new web browser for FreeRunner.

* new Project - Sync with Evolution / notifier

===Application Updates===
* '''[[MokoGeocaching]] 0.2 released'''
:It's a litle gtk python script that searches the geocaching.com site for caches near your current position or a user specified lattitude and longitude and add the cache as a poi in tangogps.
:: The script can now:
::* get gps location from phone
::* user can manually set location
::* user can specified range
::* script can download matching geocaches and add as poi
::* read geocaching.com username and password from configuration file threaded gtk and downloading - but unfortunately not searching unicode support.
::* gui input for username and password

::* The package can be found here: http://www.opkg.org/package_141.html

::it only tested it on shr unstable.

* [[Voicenote]] 0.3 released
:At the new releas , you can play the wav files you have recorded with voicenote (or other wav files), and go back the the 1st choice dialog (record or play?) after each action.
:If you want to read more , please visit http://wiki.openmoko.org/wiki/Voicenote .

* Sephora 0.2.2 available

==Tips and Tricks==
* [[Recording audio]]--

==Community ==
* '''moko 11 considered to be official'''
: Moko11 is considered to be "official". So far, received reports indicating that moko11 did indeed solve the problems it's supposed to address (i.e., lost wakeups and flow control.)

: The developer now also like to know if anything has gone wrong after installing moko11, e.g., if the changes in IO1 handling have introduced new wakeup problems. Everyone who's tried moko11-beta to please reply, either to the list or to [mailto:werner@openmoko.org Werner] in private.

: About the draft of moko11, the draft is [http://svn.openmoko.org/developers/werner/gsm/moko11/RELNOTES here].

* '''Help developing www.opkg.org'''
::[http://www.opkg.org Opkg.org] needs some developers to develop some features.

::For Opkg.org was not updated for two months, but there are still some features needed, like a better comment system with email notifications, for example. [mailto:tobias.kuendig@gmail.com Tobias]decided to publish the opkg.org source code, by this way, anyone who want to help making www.opkg.org even better than it is today, feel free to contact [mailto:tobias.kuendig@gmail.com Tobias].

====Event News====

* Munich Stammtisch was a nice meeting as well!

http://freeyourphone.de/portal_v1/viewtopic.php?f=13&t=660&st=0&sk=t&sd=a&start=45#p9531

Not that crowded (4 freerunners) as Karlsruhe.

And: it will be repeated in 1-2 months!

===Branch info ===

Hi all, i have just pushed a new branch on kernel repo which will have
the development efforts we are doing on the DRM kernel driver. It is
called drm-tracking and is based on Tom's approach (thanks!).

Toolchain

2009-02-27T22:02:15Z

Janvlug: /* Installing New Libraries */ Remark about not working repositories

{{Languages|Toolchain}}

= Introduction =

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

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

=Basic toolchain usage=

==Prerequisites==

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

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

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

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

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

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

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

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

==Downloading and installing==

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

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

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

mkdir ~/sources
cd ~/sources

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

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

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

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

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

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

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

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

bitbake meta-toolchain-openmoko

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

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

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

==Installing New Libraries==

Openmoko toolchain doesn't include many libraries by default. However, it can download and install libraries that already exist in the Openmoko repository. (It refers to the [http://downloads.openmoko.org/repository/testing/ Testing Repository] by default.)

'''TODO''' fix repository location. Next instructions do not work.

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

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

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

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

==Building a sample project==

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

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

* copy the downloaded sample application source:

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

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

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

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

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

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

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

om-conf openmoko-sample2

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

cd openmoko-sample2

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

make

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

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

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

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

* copy the downloaded sample application source

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

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

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

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

cp your-sources .
cd ..

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

PKG_NAME="your-project-name"

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

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

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

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

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

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

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

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

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

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

* and by adding the following line

Icon=your-project-name

* move into src/ folder

cd ..
cd src

* modify Makefile.am by updating the following lines

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

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

==Packaging your application==

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

om-make-ipkg openmoko-sample2

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

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

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

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

om-make-ipkg myapp myapp_control

A template of myapp_control:

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

==Where to go from here==

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

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

You may build the newest 2.6.28 kernel with these commands:

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

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

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

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

A different approach explained in more detail can be found at [[Howto compile Openmoko kernel for Neo Freerunner]].

=== Old troubleshooting information ===

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

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

to:

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

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

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

make sure to run om-conf again after this.

==Installing additional libraries into the toolchain==

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

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

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

That's it.

==Getting your application packaged by OE==

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

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

See also [[Customizing the Openmoko Distribution]].

==Troubleshooting==

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

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

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

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

under Ubuntu 8.10. Try do this:

sudo apt-get remove libtool

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

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

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

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

[[Category:Application Developer]]

[[Category:Application Developer]]

Toolchain

2009-02-27T21:44:23Z

Janvlug: /* Installing New Libraries */ English language.

{{Languages|Toolchain}}

= Introduction =

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

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

=Basic toolchain usage=

==Prerequisites==

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

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

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

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

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

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

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

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

==Downloading and installing==

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

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

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

mkdir ~/sources
cd ~/sources

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

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

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

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

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

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

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

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

bitbake meta-toolchain-openmoko

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

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

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

==Installing New Libraries==

Openmoko toolchain doesn't include many libraries by default. However, it can download and install libraries that already exist in the Openmoko repository. (It refers to the [http://downloads.openmoko.org/repository/testing/ Testing Repository] by default.)

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

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

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

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

==Building a sample project==

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

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

* copy the downloaded sample application source:

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

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

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

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

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

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

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

om-conf openmoko-sample2

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

cd openmoko-sample2

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

make

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

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

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

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

* copy the downloaded sample application source

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

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

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

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

cp your-sources .
cd ..

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

PKG_NAME="your-project-name"

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

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

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

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

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

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

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

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

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

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

* and by adding the following line

Icon=your-project-name

* move into src/ folder

cd ..
cd src

* modify Makefile.am by updating the following lines

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

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

==Packaging your application==

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

om-make-ipkg openmoko-sample2

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

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

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

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

om-make-ipkg myapp myapp_control

A template of myapp_control:

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

==Where to go from here==

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

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

You may build the newest 2.6.28 kernel with these commands:

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

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

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

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

A different approach explained in more detail can be found at [[Howto compile Openmoko kernel for Neo Freerunner]].

=== Old troubleshooting information ===

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

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

to:

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

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

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

make sure to run om-conf again after this.

==Installing additional libraries into the toolchain==

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

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

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

That's it.

==Getting your application packaged by OE==

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

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

See also [[Customizing the Openmoko Distribution]].

==Troubleshooting==

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

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

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

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

under Ubuntu 8.10. Try do this:

sudo apt-get remove libtool

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

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

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

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

[[Category:Application Developer]]

[[Category:Application Developer]]

Kernel-new-tmp

2009-02-24T22:49:43Z

Janvlug: /* Branches */

TODO: spellcheck and check grammar.

This page might eventually replace the [[Kernel]] page.

This page is mostly useful for developers and power/curious users. If you are looking for a kernel to flash into your GTA01/GTA02 you might want to check the [[Distributions]] page instead or scroll down for the daily builds we make.

== General ==

External Linux kenel developers and [[Openmoko]] Linux kernel developers provide a working kernel for the [[Freerunner]] (Also known as GTA02) and also for the [[Neo1973]] (Aka GTA01).

Right now there is an ongoing effort to reduce the difference between current Linux 2.6 (mainline) and the kernel in the Openmoko repository and thanks to this work we can run the most recent released version of Linux 2.6.

== Sources ==

The sources of the Openmoko Linux kernel live in a GIT repository.

http://git.openmoko.org/?p=kernel.git;a=summary

[http://git-scm.com GIT] is a fast version control system suited for the workflow that many kernel developers use. It is specially useful when you need to send patches for a project (who might in turn might need to send them upstream). This is an over-simplification but it gives you the idea in case you did not know.

GIT might seem complicated at first but once you learn to use it you will find many ways to increase your productivity by using it. For completeness in this page we include the GIT commands that you need in order to build a working kernel.

If you are very new to git you might want to read [http://git.or.cz/course/ good manuals already available].

If you would like to contribute code we also have a page with [[Hints_on_using_GIT_and_stgit]] where we all hope to share some cool tips and tricks that can help you. You do not need to learn stgit in order to send patches to the Kernel Mailing List but we have to tell you that once you know git, stgit will make you more productive when you need to send a few patch at once (patchsets).

=== Branches ===

GIT allows for different branches that developers use to speed up development. You might have noticed we have a few of them if you visited the web interface (http://git.openmoko.org/?p=kernel.git;a=summary).

The andy-tracking branch is the one where most of the action takes place these days.

=== Daily builds ===

If you just need the last version of the kernel you can download from the daily builds.

Autorev'ed:

http://downloads.openmoko.org/distro/experimental/

Pegged (TODO: Make clear what pegged means):

http://downloads.openmoko.org/distro/unstable/

=== Building the andy-tracking branch ===

Those are the minimum survival commands:

$ git clone git://git.openmoko.org/git/kernel.git linux-2.6
$ cd linux-2.6
$ git-checkout --track -b andy-tracking origin/andy-tracking
$ cp ./arch/arm/configs/gta02_moredrivers_defconfig .config

Before building this kernel you need install a [http://wiki.openmoko.org/wiki/Toolchain#Downloading_and_installing Toolchain].

$ ./build

Once the script finishes you will get two files. The first is ''uImage-GTA02.bin'' and a second file with a longer name but same contents, for instance ''uImage-moredrivers-GTA02_andy-tracking_c16287685cb59f91.bin''. Please use the second file if you publish your kernel in some server or if you talk about it in public (specially in bugs reports) because it will allow others to know what kernel you were trying (in case you don't have local changes).

In order to build the modules you can... TODO: fill.

If you want to update the local copy of the repository so that you get the latest changes, you can type:

$ git-pull

Before reporting that the new kernel does not build please first check for changes in the configuration file.

=== kernel building tips ===

If you are touching kernel code and building it quite often you really want to be using [http://ccache.samba.org ccache]. It will save you a lot of time.

TODO: submit a patch for the build script that makes ccache use easier.

== Contributing ==

The development resources [[Openmoko]] offers are:

* Git repository: http://git.openmoko.org/?p=kernel.git;a=summary
* [http://lists.openmoko.org/mailman/listinfo/openmoko-kernel Mailing list] ([http://lists.openmoko.org/pipermail/openmoko-kernel/ Online Archive])

We appreciate your contributions. Check the Open Issues at the end of this page to check where we need more help.

If in doubt ask in the mailing list.

== FAQ ==

=== Why does Openmoko cares about sending code upstream instead of (insert your task here)? ===

There are two approaches -- both of them doomed if you stick all your resources to them.

The first is not to care about upstream kernel and stick to an old kernel - even if [http://www.kernel.org upstream] is where the people who will help us improve, maintain and support the code running in our devices are.

The second is to care way '''too much''' about upstream (too much purity) the point that we won't ship a temporal dirty hack that make users happy and able to better use their phones.

As many things in engineering we have to find a point in the middle that works well and we will try hard to.

=== Who's Andy and why is he sticking his name in the kernel? ===

He takes some credit and most the blame. It is an usual practice that in kernel development some branches are named after the person who is taking care of them. For instance he takes the work of making sure things still build when Linus and his friends update the upstream kernel and believe us: it is not as fun as it might sound.

== Known issues ==

Some issues might be very difficult because of lack of (correct) documentation from the hardware makers or because not many people are used to dealing with them. If you can help us with one of those issues it would be great.

TODO: make a list with important open tickets

Neovento

2009-02-15T10:06:06Z

Janvlug: Added links.

{{Languages|fyp}}

[[Image:Fyp.png|thumb| Main screen]]

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

'''Status:''' ''first beta image is released''

= Concept =
The main concept is the use of LXDE and Zhone which is embedded in the background and the whole is based on Debian/FSO as a subsystem.
This will allow the user to use the basic functions of the phone in a fingerfriendly way, but also gives the opportunity to take the pen and go surfing the web or do some messaging.

= Features =
* a new Zhone theme
* preinstalled applications (Iceweasel, Pidgin, TangoGPS, Wicd)
* it fits on the 256MB NAND flash

= Installation =

* [http://opensvn.csie.org/fyp/releases/2.13/ download release 2.13]
* flash the image and the kernel with [[NeoTool|NeoTool]]

= Usage =

== Buttons ==

* AUX (short press) shows the keyboard
* Power (short press) pops up the shutdown/suspend menu

== Recommendations ==

* use the recommended Kernel
* make and use a [[SwapSpace|swapfile]] on your µSD (warning: this may destroy the µSD card after uncertain time)
* save the TangoGPS map files on the µSD as there is little space left on the NAND

= Links =
*[http://www.freeyourphone.de FreeYourPhone.de community]
*[http://freeyourphone.de/portal_v1/viewtopic.php?f=63&t=912 fyp thread on FreeYourPhone.de]
*[http://opensvn.csie.org/fyp/ fyp SVN]
*[https://opensvn.csie.org/traccgi/fyp fyp wiki/trac]

[[Category:Distributions]]

Stable Hybrid Release

2009-02-09T15:37:23Z

Janvlug: /* More Information */ Added link to tweaks.

Talk:Community Updates/2009-02-06

2009-02-06T08:06:45Z

Janvlug: /* Distributions */

==Distributions==
* FSO- Freesmartphone.org team is proud to present the fifth milestone release codenamed 'Calling All Stations'. If you like to know more details read them here:

::http://wiki.openmoko.org/wiki/OpenmokoFramework/Status_Update_6. You can grab it on http://downloads.freesmartphone.org/fso-stable/milestone5/ .
:: Have fun and happy hacking.

* [mailto:nytowl@openmoko.org Angus Ainslie] is the new official distribution maintainer of Openmoko. He will be in charge of integration and management of the buildhost server and downloads server, images management and integration for the software team. Feel free to contact him, if you have any questions about images.

==New Applications ==
* [[CellHunter]]-Cellhunter is a game with the goal to find as much unknown mobile cells as you can and submit them. You are playing in groups against other groups and collect the information together. Depending on the type of the collected cell you get points. New cells count more points than already known cells. More information at http://cellhunter.omoco.de

* [[Vala-terminal]]-Command Line Terminal. It is written in (vala) programming-language. Vala produces c-code, which is then compiled binary form, so vala do not add any runtime requirements/dependeries. This is official successor of openmoko-terminal2 (https://kerneltrap.org/mailarchive/openmoko-community/2008/11/13/4084004/thread).

* [[GTick]]-GTick is a metronome application written for GNU/Linux and other UN*X-like operting systems supporting different meters (Even, 2/4, 3/4, 4/4 and more) and speeds ranging from 10 to 1000 bpm. It utilizes GTK+ and OSS (ALSA compatible). It is part of the GNU Project. This program has been originally written by Alex Roberts, but since he didn't have the time to develop and maintain it further, I (Roland Stigge) took it over (initially to package it for Debian, but there were too many "upstream" issues, so I decided to maintain the whole package). Since then, the program has been mainly rewritten (new DSP core, GTK+2 port, added features).

* [[Nethack]]-NetHack is a single player dungeon exploration game that runs on a wide variety of computer systems, with a variety of graphical and text interfaces all using the same game engine. Unlike many other Dungeons & Dragons-inspired games, the emphasis in NetHack is on discovering the detail of the dungeon and not simply killing everything in sight - in fact, killing everything in sight is a good way to die quickly. Each game presents a different landscape - the random number generator provides an essentially unlimited number of variations of the dungeon and its denizens to be discovered by the player in one of a number of characters: you can pick your race, your role, and your gender.

* [mailto:list@elste.org elh] compile a card game [http://www.xskat.de/xskat.html Skat] for FreeRunner. You can download it [http://www.elste.org/downloads/xskat_4.0_armv4t.ipk here].

==Application information updates==
* [[Gwaterpas]]-Version upgrade from 0.2 to 0.3. You can get the source [http://www.ecirc.net/openmoko/gwaterpas-0.3.tgz here]. Downloads opkg file [http://www.ecirc.net/openmoko/gwaterpas_0.3_armv4t.ipk here].

* [mailto:gecco@napodano.com Carlo Minucci] personalized the default keyboard for write sms (for Italian language). You can download package [http://minucci.net/file/keyboard.tar.gz here ].

* [[Kustomizer]] for 2008.12-A script to install all kinds of cool stuff to a clean 2008.12 installation on Freerunner.

* [[Yaouh!]]- [[User:Kelvan|Kelvan]] enhanced the code a bit. You can check [[http://wiki.openmoko.org/wiki/Yaouh!#experimental|here]] for more information.

* [[Paroli]]-[mailto:mirko@openmoko.com Mirko] had made some big changes to Paroli. Like dbus interface is optional and you can work with both modes. Dilar reworked version was added...etc. You can check http://www.paroli-project.org for more informations. Check api section at http://www.paroli-project.org/api/.

* [http://n2.nabble.com/file/n2254283/guitartune_0.20_arm.ipk Guitar Tune] had new release. It's based on alsa and automatically selects the appropriate alsa state. Have tested on FSO Milestone 4 and kernel 2.6.28. and it should work on SHR too. [http://n2.nabble.com/file/n2254283/guitartune-0.2.tar.gz Source code is available].

* [[Neon]]-A new release of Neon is available. [http://projects.openmoko.org/forum/forum.php?forum_id=916 This release is focus on feature enhancement].

== Community ==
* Openmoko had moved to New Office. New office now locate in 9F, No.276, Jiang-Guo Rd. Hsin-Tien City, Taipei County 231 Taiwan.

* OpenWrt now has basic support for the Openmoko "Freerunner"!. kernel (2.6.28) is building and booting. D-Bus and the freesmartphone.org reference implementation. Xglamo with acceleration making good progress to get glamo acceleration working within Xorg. EFL (enlightenment foundation libraries) and enlightenment including illume.

* [[Screen protection - ARMR200 film]]-3M produce a product designed for touch screens called ARMR200. It can help you protect your screen from hurt.
* [mailto:tobias.kuendig@gmail.com Tobias Kündig] set up an a simple repository for [http://www.opkg.org www.opkg.org]. The repository's address is http://www.opkg.org/packages/. Please feel free to test it and report any bugs/mistakes.

*[[User:Kaspernj|Kaspernj]] set up a repository where this application can be downloaded. You can visit Kaspernj's user page , to get more informations.

===Community statistics===
* '''4,947''' total pages in the database.
* '''832''' files have been uploaded.

* '''13,406,497''' page views
* '''65,318''' page edits
* '''13.20''' average edits per page

==Community Events==
[[Image:Freerunner-ita.png|align|right]]
* Hackable:1 Openmoko User Meeting in Paris (HOUM#1),Thursday February 5th from 18:30 on. The organizer will prepare a SD card containing the newest pre-installed , updated copy of hackable:1 to each guest coming to this event. the announcement on openmoko-fr (french) http://openmoko-fr.org/wiki/index.php/2009-02-05_:_40_passage_des_panoramas.

* First FreeRunner Party will hold in Italy at 8 February. Please check http://www.luccalug.it/wiki/Freerunner to get more information. (only in italian ).

==Tips and tricks ==
* While you install Anddroid on FreeRunner. You need to prepairing an SD card with two partitions. There's many ways to make this SD card. And SD card can be formatted from within an [[Android_on_Freerunner#Using_exiting_2008.x_installation_on_FreeRunner|existing 2008.x installation on your FreeRunner]].

[[category:Community Update]]

Talk:Community Updates/2009-02-06

2009-02-03T19:28:42Z

Janvlug: /* Community Events */ Link to www.opkg.org

==Distributions==
FSO- Freesmartphone.org team is proud to present the fifth milestone release
codenamed 'Calling All Stations'. If you like to know more details read them here:
http://wiki.openmoko.org/wiki/OpenmokoFramework/Status_Update_6. You can grab it on http://downloads.freesmartphone.org/fso-stable/milestone5/ . Have fun and happy hacking.

==Application information update==

[[CellHunter]]-Cellhunter is a game with the goal to find as much unknown mobile cells as you can and submit them. You are playing in groups against other groups and collect the information together. Depending on the type of the collected cell you get points. New cells count more points then already known cells. More information at http://cellhunter.omoco.de

[[Vala-terminal]]-Command Line Terminal. It is written in (vala) programming-language. Vala produces c-code, which is then compiled binary form, so vala do not add any runtime requirements/dependeries.

This is official successor of openmoko-terminal2 (https://kerneltrap.org/mailarchive/openmoko-community/2008/11/13/4084004/thread).

[[Gwaterpas]]-Version upgrade from 0.2 to 0.3. You can get the source [http://www.ecirc.net/openmoko/gwaterpas-0.3.tgz here]. Downloads opkg file [http://www.ecirc.net/openmoko/gwaterpas_0.3_armv4t.ipk here].

[[GTick]]-GTick is a metronome application written for GNU/Linux and other UN*X-like operting systems supporting different meters (Even, 2/4, 3/4, 4/4 and more) and speeds ranging from 10 to 1000 bpm. It utilizes GTK+ and OSS (ALSA compatible). It is part of the GNU Project.

This program has been originally written by Alex Roberts, but since he didn't have the time to develop and maintain it further, I (Roland Stigge) took it over (initially to package it for Debian, but there were too many "upstream" issues, so I decided to maintain the whole package). Since then, the program has been mainly rewritten (new DSP core, GTK+2 port, added features).

[[Nethack]]-NetHack is a single player dungeon exploration game that runs on a wide variety of computer systems, with a variety of graphical and text interfaces all using the same game engine. Unlike many other Dungeons & Dragons-inspired games, the emphasis in NetHack is on discovering the detail of the dungeon and not simply killing everything in sight - in fact, killing everything in sight is a good way to die quickly. Each game presents a different landscape - the random number generator provides an essentially unlimited number of variations of the dungeon and its denizens to be discovered by the player in one of a number of characters: you can pick your race, your role, and your gender.

[mailto:list@elste.org elh] compile a card game [http://www.xskat.de/xskat.html Skat] for FreeRunner. You can download it [http://www.elste.org/downloads/xskat_4.0_armv4t.ipk here].

[mailto:gecco@napodano.com Carlo Minucci] personalized the default keyboard for write sms (for Italian language). You can download package [http://minucci.net/file/keyboard.tar.gz here ].

[[Kustomizer]] for 2008.12-A script to install all kinds of cool stuff to a clean 2008.12
installation on Freerunner.
== Community Events==
[[Screen protection - ARMR200 film]]-3M produce a product designed for touch screens called ARMR200. It can help you protect your screen from hurt.

* Hackable:1 Openmoko User Meeting in Paris (HOUM#1),Thursday February 5th from 18:30 on. The organizer will prepare a SD card containing the newest pre-installed , updated copy of hackable:1 to each guest coming to this event. the announcement on openmoko-fr (french) http://openmoko-fr.org/wiki/index.php/2009-02-05_:_40_passage_des_panoramas.

* [mailto:tobias.kuendig@gmail.com Tobias Kündig] set up an a simple repository for [http://www.opkg.org www.opkg.org]. The repository's address is http://www.opkg.org/packages/. Please feel free to test it and report any bugs/mistakes.

Talk:SHR

2009-01-13T08:33:09Z

Janvlug: /* Downloading images */ Link to explanations of images.

The freesmartphone framework daemons (ophoned, opreferencesd, odevicesd, etc...) have all been merged into a single daemon (frameworkd) So you will only need one package for all the freesmartphone functionalities. I am not sure yet of the stability of this daemon though.

Also, if you are looking for a set of applications using the framework, maybe you want to have a look at tichy (disclamer : this is my project) : http://charlie137-2.blogspot.com/2008/07/introducing-tichy.html

If you base your softwares on tichy, all you need to provide in you image is the freesmartphone framework, python, and a few standard python libraries.

--[[User:Charlie|Charlie]] 11:43, 5 July 2008 (UTC)

A conversation between roh, wurp, paulproteus about how to get started on the project:
<pre>
Jul 04 02:37:30 <paulproteus> wurp2|away, Cool, but I'd rather talk about the old-apps-on-FSO project. (-:
Jul 04 02:37:53 <paulproteus> I wonder if we can easily package this for opkg.
Jul 04 02:38:04 <wurp2|away> paulproteus: Sounds good. Sorry, I wsa reading the backlog.
Jul 04 02:38:10 <paulproteus> No prob!
Jul 04 02:39:06 <wurp2|away> I kept asking mickey why someone wasn't doing this (SHR)
Jul 04 02:39:37 <paulproteus> His answer was, everyone else is too busy?
Jul 04 02:39:44 <wurp2|away> And he said someone should, and pointed out that you could just build a phonekit-to-ophoned adapter, so finally today I got off my duff and started it
Jul 04 02:40:02 <wurp2|away> Yeah, I knew he & his little group was too busy
Jul 04 02:40:28 <wurp2|away> But I thought someone from OM could take the relatively small amount of time it *seems* like it should take
Jul 04 02:40:29 * paulproteus nods and listens
Jul 04 02:40:43 <wurp2|away> But, hey, if you want something done...
Jul 04 02:41:17 <wurp2|away> So I'm not sure I have much more to say that isn't on the wiki
Jul 04 02:41:30 <wurp2|away> IMO the first step is to get a good FSO image running from our repo
Jul 04 02:41:33 <roh> hey guys
Jul 04 02:41:39 <paulproteus> Hey now roh.
Jul 04 02:41:42 * mwester hides
Jul 04 02:42:01 <nezza-_-> hey roh
Jul 04 02:42:05 <wurp2|away> Then build a phonekit stub that openmoko2-dialer (or whatever the name is) can pretend to connect to
Jul 04 02:42:06 <paulproteus> wurp2|away, I agree - the first thing to do is just cone the current branch and have a repeatable build system.
Jul 04 02:42:08 <wurp2|away> Hi roh
Jul 04 02:42:11 <roh> about your project... i think youre overshooting the goal by soundling like 'we need to fork'
Jul 04 02:42:29 <paulproteus> I see it more as a branch than a fork. But can you explain what you mean?
Jul 04 02:42:32 <roh> but i see your goal and like it.
Jul 04 02:42:45 <wurp2> roh: If we can get away without it, that would be great. I want to minimize what we're doing
Jul 04 02:42:51 <paulproteus> Hopefully, as FSO people get interested in this, our branch would get rebased and disappears into FSO.
Jul 04 02:42:59 <roh> eventually you should just do it where the main fun happens. in the repos we have. here is what i suggest:
Jul 04 02:42:59 * mwester thinks the community needs commit rights, whatever you call it (fork or whatever)
Jul 04 02:43:09 <wurp2> I fished around for suggestions of how we could go about just labelling, or just branching specific files, but got no feel-good answers
Jul 04 02:43:18 * wurp2 listens.
Jul 04 02:43:31 <roh> you start hacking and coding, and i will see that there is a milestone in trac, where you can organize tickets in
Jul 04 02:43:48 <paulproteus> roh, in the fso trac? I'm sold.
Jul 04 02:43:56 <roh> also about commit-rights.. thats quite easy. currently 2007.2 is basically unmaintained
Jul 04 02:44:22 <paulproteus> So any development would really be the only branch, anyway? (-:
Jul 04 02:44:23 <roh> paulproteus i dunno for sure.
Jul 04 02:44:28 <paulproteus> Sure, but basically.
Jul 04 02:45:41 <roh> the point is: we are currently thinking about reorganizing the buildprocess anyways.. so i would say we should a) see to get less distro-trees b) have a branch where the man with the hat for the branch commits stuff to.
Jul 04 02:46:04 <wurp2> roh: Just to make sure I understand: are you suggesting we commit to the 2007.2 tree?
Jul 04 02:46:14 <paulproteus> That's in svn, right?
Jul 04 02:46:22 <wurp2> or I can just keep listening until you're done with your point :-)
Jul 04 02:46:28 <roh> but the main point is: 2007.2 apps are in the main svn, but unmaintained. if somebody steps up and basically claims maintainership by doing real work i see not why we should hinder that.
Jul 04 02:47:01 <roh> my only concern about that all is: i do not see reason for 'forking' or cluttering stuff even more than it currently is.
Jul 04 02:47:17 <paulproteus> Okay, I can agree with that.
Jul 04 02:47:25 * jeffszusz tries to make sense of the convo
Jul 04 02:47:25 <roh> on the contrary, we need to get better oversight. and thats not what happens by using more different repos
Jul 04 02:47:26 <wurp2> roh: Sounds great!
Jul 04 02:47:42 <paulproteus> Now as far as build process, we'd still use the git OE repos and improve the bitbake files there?
Jul 04 02:47:44 * mwester notes that he currently has a rather poor attitude about OM branches and commits, and steps out of the conversation. :(
Jul 04 02:47:48 <nullpuppy> ok. finally home, now to try and put together a build environment ;)
Jul 04 02:47:57 <paulproteus> We'd just make our own branch in that central OM git repo?
Jul 04 02:47:57 <roh> i dunno for sure, but atm i think we do a daily build of gta01 and gta02 org.openmoko.dev
Jul 04 02:48:06 <roh> the asu branch as well..
Jul 04 02:48:11 * jeffszusz didn't know there were forks/branches in OM
Jul 04 02:48:13 <wurp2> So what do we do to get permission to check stuff into 2007.2?
Jul 04 02:48:21 <roh> but i dunno who even uses these image (non-asu, old gtk based) or if they work at all.
Jul 04 02:48:28 <paulproteus> Right.
Jul 04 02:48:44 <alphabeat> dvarnes: http://wiki.openmoko.org/wiki/Group_Sales_Australia
Jul 04 02:48:54 <wurp2> roh: They didn't work 3 weeks ago, then about 2 weeks ago someone said they (mostly) worked, but I dunno that they're maintained at all, as you say
Jul 04 02:49:03 <roh> wurp2 submit patches. i mean.. the recipe for the 2007.11 stuff should have a fixed svnrev, so even if you would break it it should even have the old states.
Jul 04 02:49:08 <wurp2> s/They/2007.2/
Jul 04 02:49:09 <apt> wurp2 meant: roh: 2007.2 didn't work 3 weeks ago, then about 2 weeks ago someone said they (mostly) worked, but I dunno that they're maintained at all, as you say
Jul 04 02:50:04 <roh> so i suggest: start hacking, start mailing patches.. i see that we clear up the repo as well as buildhost-situation.
Jul 04 02:50:06 <dvarnes> alphabeat, yep .. already sent message to simon mathews with inquiry
Jul 04 02:50:28 <wurp2> roh: OK, I'm very familiar with svn, and I have some experience with darcs and a knowledge of arch (RCSs like git)
Jul 04 02:50:37 <wurp2> But I dunno how we would work off an svn tree
Jul 04 02:50:41 <paulproteus> wurp2, IMHO we should use a git-svn repository to work on our patches then.
Jul 04 02:50:42 <wurp2> and easily share changes with one another
Jul 04 02:50:49 <paulproteus> That is quite feasible.
Jul 04 02:50:56 <roh> its a 2-part story.. one part is basic distribution-building work (means should happen in a branch or head on git)
Jul 04 02:50:59 <paulproteus> Another thing is to try quilt.
Jul 04 02:51:00 <wurp2> then submit patches once we're happy to whoever to merge into main tree
Jul 04 02:51:12 <paulproteus> I have to run in a minute, I'm very sorry to say!
Jul 04 02:51:13 <roh> the other part is porting and changing applications, which should happen where the app lives.
Jul 04 02:51:16 <wurp2> roh: Ah, I'm familiar with how to do it (basically) in git
Jul 04 02:51:29 <paulproteus> roh, Yes, re: distribution work: would we get a branch in the main OM git then?
Jul 04 02:51:35 <paulproteus> That would be fantastic.
Jul 04 02:51:51 <paulproteus> And I *really* appreciate you stepping in here.
Jul 04 02:51:56 <roh> i think that it would be the best way to do this.
Jul 04 02:52:12 <alphabeat> dvarnes: might be a little late. i think he bought a few as overhead so you might be lucky :) we bought 60 but only needed 53 or something
Jul 04 02:52:27 <wurp2> OK, I saw svn sneak in there for a bit, now we're talking about git again... which parts are git and which are svn?
Jul 04 02:52:34 <paulproteus> svn for apps; git for OE work
Jul 04 02:53:15 <wurp2> paulproteus: And you said quilt is a tool to help us share changes in our group, then create patches to submit to the main svn?
Jul 04 02:53:15 <paulproteus> Email patches for apps, and get them in a state to use the FSO backend that way, sharing work between us before they're ready for submission using git-svn.
Jul 04 02:53:16 <paulproteus> git for OE work - we'd get a branch in the OM git.
Jul 04 02:53:16 <paulproteus> That's what I understand.
Jul 04 02:53:26 <paulproteus> wurp2, Yes, quilt is an alternative to git-svn in this workflow.
Jul 04 02:53:27 <Dave> We meet again, Mr. Wurp.
Jul 04 02:53:38 <wurp2> wurp2: Ah, I think I prefer git-svn
Jul 04 02:53:41 <paulproteus> I think so too.
Jul 04 02:53:41 <wurp2> Dave: howdy
Jul 04 02:53:52 <Dave> Howdy ya'll
Jul 04 02:54:06 <wurp2> So we work in git, get it how we like it, then we create a patch
Jul 04 02:54:14 <wurp2> keeping our git in sync w/ svn via git-svn
Jul 04 02:54:25 <roh> wurp2 ?
Jul 04 02:54:29 <wurp2> (er, and we submit the patch back to the svn owner, of course)
Jul 04 02:54:29 <Dave> yep yep :)
Jul 04 02:54:45 <wurp2> roh: Did I drift into crazy talk?
Jul 04 02:55:04 <roh> i do not care how you branch/merge on your machine, but my point is that the app itself currently resides in svn.. and the distro which is 'one layer above' is in git
Jul 04 02:55:10 * jeffszusz pulls out his cardboard Freerunner and pretends to talk on it
Jul 04 02:55:26 <wurp2> roh: I think I understood that
Jul 04 02:55:31 <Dave> Is this not self-evident enough from the repositories themselves?
Jul 04 02:55:44 <Dave> jeffszusz: whoa, cool man, where can I get one? :D
Jul 04 02:55:46 <roh> Dave since we have loads of them, sadly not all the time.
Jul 04 02:55:53 <wurp2> roh: And dealing with the distro seems straightforward; we create a git repo that is a "child"(branch) of the main repo
Jul 04 02:55:57 <Dave> Yeah, I noticed that too, roh :)
Jul 04 02:56:04 <paulproteus> I have to run in 30-60s (-:
Jul 04 02:56:04 <wurp2> and can submit changes back
Jul 04 02:56:11 <wurp2> paulproteus: bye :-(
Jul 04 02:56:15 <SpeedEvil> How long are confirmation emails taking to get sent out?
Jul 04 02:56:19 <Dave> Even occasionally, and if it weren't for tagging, I'd mistake one for another frequently :)
Jul 04 02:56:24 <jeffszusz> Dave: print, cut, paste!
Jul 04 02:56:30 <paulproteus> wurp2, Right - we'll commit to a branch in OM git, and then we can ask the other branches to merge or cherry-pick our changes.
Jul 04 02:56:33 <roh> also most projects are just about apps and not about 'lets build a device.. and while were at it write drivers for it.. ah.. and bootloaders.. and apps.-. and then package it in a linux-distri
Jul 04 02:56:35 <SpeedEvil> Someone not had one after 3.5 hours. Is that overly delayed?
Jul 04 02:56:47 <Dave> heh, true enough :)
Jul 04 02:56:59 <wurp2> roh: But for apps, it seems that we need some way to share changes amongst ourselves w/o waiting for the patch to get accepted into the mainline, or even in some cases when we have things that aren't quite complete, that need another team member to finish
Jul 04 02:56:59 <alphabeat> jeffzusz: did you print out the CAD file and make your own phone out of cardboard too?
Jul 04 02:57:31 <roh> wurp2 for testing they could be applied in the distro dev branch.
Jul 04 02:57:32 <jeffszusz> alphabeat: nope, but i'm tempted
Jul 04 02:57:33 <dvarnes> alphabeat, yep .. understood .. I had looked a couple of times at the Group page, but the Aus one is not linked, so missed it. Not urgent since I already have a Neo :-) Still, am plannig to order a FR ..
Jul 04 02:57:54 <Dave> Oh, I should write that report to the ml now.
Jul 04 02:58:00 <wurp2> roh: So we were suggesting a SHR specific git repo, that would drift a bit from the app's svn until we get small changesets complete, then we would create patches
Jul 04 02:58:05 <paulproteus> You guys, please store the results of this discussion on that wiki page.
Jul 04 02:58:05 <paulproteus> Bye!
Jul 04 02:58:13 <roh> i guess it would start with a -dev only branch.. if that then takes 'form' make it a stable one and branch the new --dev
Jul 04 02:58:15 <wurp2> and keep our git repo in sync w/ the app repo via svn-git
Jul 04 02:58:21 <roh> (the distro)
Jul 04 02:58:43 <digitalslave> <would be happy just to get the emulator to compile blac
Jul 04 02:58:44 * jeffszusz is realizing how little he knows about the progress of OpenMoko
Jul 04 02:58:46 <wurp2> OK
Jul 04 02:58:56 <roh> testing patches is in -dev as patch in oe.. then merge it into the repo (work with minrev and maxrev in the recipes)
Jul 04 02:59:04 <wurp2> I'm hoping that our actual changes are fairly minimal
Jul 04 02:59:48 <roh> i guess so. even then.. really.. nobody would want to hinder future maintainers of apps to evolve ;)
Jul 04 02:59:57 <wurp2> A replacement for phonekit that delegates to ophoned, and a recipe to pull in compatible versions of all the basic apps
Jul 04 02:59:59 <digitalslave> cd ..
Jul 04 02:59:59 <digitalslave> ls
Jul 04 03:00:06 <alphabeat> dvarnes: it looks like he ordered 60 with 52 phones confirmed and payed for and 6 phones unconfirmed which leaves 2 spare. might be lucky hey? ps jealous of buying a neo1973. should have got one :P
Jul 04 03:00:13 <wurp2> digitalslave: Wrong window?
Jul 04 03:00:27 <digitalslave> haha yep damn track pad heh
Jul 04 03:00:48 <wurp2> digitalslave: At least it wasn't your root password
Jul 04 03:01:06 <jeffszusz> wurp2: i did that before
Jul 04 03:01:11 <digitalslave> hahaha
Jul 04 03:01:21 <alphabeat> wurp2|jeffszusz: yah me too xD
Jul 04 03:01:31 <wurp2> roh: I'll have to learn some more more before your -dev and --dev and minrev/maxrev stuff make sense to me :-)
Jul 04 03:01:34 <digitalslave> i like reading all the logs at work from everyone putting there password in for their username :)
Jul 04 03:01:38 <jeffszusz> i was due for a new password anyway... but i was lucky nobody used it before i had a chance to change it
Jul 04 03:01:38 <jeffszusz> heh
Jul 04 03:01:45 <wurp2> alphabeat, jeffszusz: :-(
Jul 04 03:01:50 <alphabeat> digitalslave: you're evil! i like that
Jul 04 03:02:11 <wurp2> It's also amazing what you'll see on a nic in promiscuous mode
Jul 04 03:02:21 <digitalslave> haha true that!
Jul 04 03:02:28 <roh> wurp2 in oe recipes one can define max, min or ranges thus of revisions which patches get applied.
Jul 04 03:02:30 <wurp2> Like people's pwds on all the sites that didn't know enough to use https for login form submission
Jul 04 03:03:04 <roh> wurp2 so if the patch which gets applied is merged, one sets the maxrev to one version below or so (atleast thats how i got it)
Jul 04 03:03:14 <wurp2> roh: I see
Jul 04 03:04:45 <wurp2> roh: How do we submit patches? openmoko-devel? Or is there a list of private email addys?
Jul 04 03:05:08 <roh> yeah.. just the list
Jul 04 03:05:16 <roh> or if you think it makes sense we
Jul 04 03:05:31 <roh> eh we can add a milestone and you add them as attachment to tickets
Jul 04 03:06:06 <wurp2> roh: That could work too... it seems like it would feel more reliable
Jul 04 03:06:22 <wurp2> roh: As in, we can see a comment on the ticket that says submitted, and don't have to search email logs for it
Jul 04 03:06:34 <roh> well.. its only how the 'group' of developers plans its workflow
Jul 04 03:07:01 <wurp2> roh: Is there any material I can read to get some clues about this?
Jul 04 03:07:19 <roh> eh.. which part
Jul 04 03:07:31 <wurp2> Whichever parts have docs :-)
Jul 04 03:07:43 <roh> ehehe
Jul 04 03:08:01 <roh> well.. trac is easy.. it has documentation
Jul 04 03:08:03 <wurp2> bitbake, how you're using milestones, what the procedure has been to submit patches in the past
Jul 04 03:08:12 <wurp2> OK
Jul 04 03:08:20 <wurp2> I've had "read up on trac" in my todo for a long time
Jul 04 03:08:26 <wurp2> Now I guess I'll actually do it
Jul 04 03:08:37 <roh> submitting patches... eh.. well..the opensource-default.. send by mail, do not mangle long lines ;)
Jul 04 03:08:45 <roh> use diff -u eh svn diff -u
Jul 04 03:09:09 <wurp2> Yeah, for that I was more concerned with internal procedures
Jul 04 03:09:33 <wurp2> But I'm not even sure what the questoins are right now, so I'll just try it the way that seems obvious the first time
Jul 04 03:09:34 <Dave> i.e. how the cabal performs its rituals ;)
Jul 04 03:09:37 <wurp2> And get corrected
Jul 04 03:09:44 <wurp2> Dave: exactly
Jul 04 03:09:48 <wurp2> tribal knowledge
Jul 04 03:09:52 <Dave> :)
Jul 04 03:10:11 <Dave> Every tribe is different ;)
Jul 04 03:10:23 <roh> wurp2 i think currently we are happy if people can code and submit good patches.. one easily looks over process minors then
Jul 04 03:10:45 <Dave> That sounds encouraging.
Jul 04 03:10:48 <wurp2> Well, I can code & submit patches
Jul 04 03:10:58 <wurp2> We'll see if you conclude they are good or not ;-)
Jul 04 03:11:27 <Dave> We'll see if you get voted off the island or not. ;)
Jul 04 03:12:12 <wurp2> OK, 2007.2 is OM distro, right? Not apps, mostly?
Jul 04 03:12:30 <wurp2> and 2007.2 is a git branch, yes?
Jul 04 03:17:46 <roh> 2007.2 is a set of apps om did
Jul 04 03:18:59 <wurp2> roh: OK
</pre>

== some thoughts ==

I was wondering what's the difference between this planned SHR and future release of FSO ? I mean, FSO is really great but lacks apps for the moment ; you're planning to port these apps from the GTK or the QT apps.

Why not contribute these ported applications to the FSO milestone 2 ?

I believe you should explain that in the page (or maybe I'm just confused by the description)

[[user:jeremy-list|Jeremy List]]: Presuming this titchy thing is fairly lightweight in requirements it could be ideal for the main UI. However it needs a way of handling more items than will fit on the screen (for example, a scrollbar). and I would prefer using something with a different colour scheme.

: Jeremy : tichy already supports scrolling (I need to make it looks better and faster though), there is also a style system, that allow to dynamically modify not only the color scheme, but also the widgets sizes and look. Beside I modified the default look so that it is better by default. Check out the svn repository for a demonstration. It works fine even on desktop computer, without compiling. --[[User:Charlie|Charlie]] 08:47, 21 July 2008 (UTC)

== Package management ==

I wounder if it would be possible to replace openembeded with Debian, and include some key packages into the debian distribution such as illume, matchbox, the FSO framework, etc. (However that works.. a bunch of different dbus applications I imagine)

I believe the device has enough space to accomadate a full bash and apt-get and such, which would permit the ability to gain access to the huge armel debian package database and install ported software without the need to hassle yourself with bitbake files.

When we see the next generation of open palmtops come out with 64GB of internal flash, we will feel even more silly when we're using busybox and opkg.

== Working parts of FSO ==

The section "Why not FSO?" of this article says: "FSO is by far the most stable & usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)". According to the [[Distributions]] page FSO has more features (and there are none listed for SHR). Which page is correct? Is this page outdated? --[[User:Marko Knöbl|Marko Knöbl]] 22:39, 6 August 2008 (UTC)

== Downloading images ==
http://build.shr-project.org/shr-testing/images/om-gta02/ contains two U-Boot images. Is there a difference between them? Clarifying this in the text would be useful. It confuses me that there are two U-Boot images.

I have tried to clarify that, but the root file system is missing in http://build.shr-project.org/shr-testing/images/om-gta02/ --[[User:Piratebab|Piratebab]] 17:49, 11 January 2009 (UTC)

[[User:Janvlug|Janvlug]] 10:05, 12 January 2009 (UTC) -- So, which root file system should I use when I want to use SHR testing? 
Furthermore, it would be handy if somewhere was explained what the relation is between the files in the [http://build.shr-project.org/shr-testing/images/om-gta02/ testing] dir. For example that http://build.shr-project.org/shr-testing/images/om-gta02/uImage-2.6.24-oe3+gitrfb42ce6724576fc173faf8abfb04aa2c36d213b7-r1-om-gta02.bin and http://build.shr-project.org/shr-testing/images/om-gta02/uImage-om-gta02-latest.bin are the same. 
What is the use of the [http://build.shr-project.org/shr-testing/images/om-gta02/modules-2.6.24-oe3+gitrfb42ce6724576fc173faf8abfb04aa2c36d213b7-r1-om-gta02.tgz modules] file, should the files be copied over the (still to be gotten) root image files? 
Currently, I'm stuck in trying to install SHR testing, because I do not know which images to use. 
I noticed that om-gta2 testing files (including rootfs images) are available in the neo1973 directory at: 
http://build.shr-project.org/shr-testing/images/neo1973/ 
See this [http://lists.openmoko.org/pipermail/community/2009-January/039561.html mail] for more details about the images.

Talk:SHR

2009-01-12T20:56:23Z

Janvlug: om-gta2 testing images available in neo1973 testing directory.