Openmoko - User contributions [en]

Bootloader

2010-08-16T14:20:32Z

Ott--: bootlader kernel size limit

{{Languages|Bootloader}}

The '''bootloader''' is a small program to start up the main operating system. The Openmoko phones can use [[U-Boot]] or [[Qi]] as bootloaders. Qi is actively developed, while the Openmoko version of U-Boot is not.

The default bootloader of the [[Neo 1973]] is U-Boot. The bootloader of the Neo 1973 can be modified, but this is only recommended if a [[debug board]] is available.

The [[Neo FreeRunner]] has two bootloaders. The [[NOR Flash]] contains a version of U-Boot which cannot be modified. Therefore it is always available as a fallback, and the second bootloader can be modified without any risk. This bootloader can be booted into by pressing and holding the AUX button and then pressing the Power button.

Note that the NOR bootloader has a size limit of 2 MB for the kernel. The NAND u-boot loader has the same limit, but you could rather easily increase it by modifying the [[Bootloader_environment|u-boot environment]].

==Links==
*http://en.wikipedia.org/wiki/Bootloader#Boot_loader

[[Category:Bootloaders| ]]

Literki

2010-04-27T23:14:11Z

Ott--: contributed startup script

[[Image:literki1.png | thumb | Screenshot of the touchpad mode]]
[[Image:literki2.png | thumb | Literki in landscape mode]]

'''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. With literki comes the touchpad. With it use can use the bottom of the touchscreen to move a cursor around. You can then use left and right click with it. There are also four scroll buttons, which are useful if your application has very small scroll bars. [http://www.opkg.org/package_232.html Opkg page]

== Installation ==

opkg install http://pvtrace.com/~miki150/literki_0.0.2-r6_armv4t.ipk

== Source code ==
http://git.senfdax.de/?p=literki

== Instructions ==
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.

By doing the same in the bottom left corner, you open the touchpad.

Please have a look at /etc/literki.conf. Things you can change there include colors, window sizes and vibration options.

Instructions for literki.conf:
*http://pvtrace.com/literki_conf.html

== Contributions ==

If you want to have literki always started at system boot and thus don't want to waste space for an icon on the desktop, you can place a script in /etc/X11/Xsession.d:

<pre>
#!/bin/sh

# /etc/X11/Xsession.d/82literki

# use this for log messages
# /usr/bin/literki >>/var/log/literki.log 2>&1 &

# normal operation
/usr/bin/literki >/dev/null 2>&1 &
</pre>

[[Category:Touchscreen keyboards]]

GPRS FSO

2010-04-27T15:11:02Z

Ott--: /* Using scripts */ changed mdbus to mdbus2 in the scripts

{{FSO}}
This page documents the GSM networking solutions (commonly known as GPRS) using the [[OpenmokoFramework|FreeSmartphone.Org]] framework (FSO).

There are other ways to enable wireless communications on the smartphone, including [[Bluetooth]] and [[Wireless_Networking|WLAN]].

== Current state ==

Since milestone 2 the system dbus has been extended with methods that enables connectivity using GPRS. The functionality is available under <code>org.freesmartphone.ogsmd</code> at <code>/org/freesmartphone/GSM/Device</code>.

The implementation should not interfere with other phone functionality, such as placing calls. In other words: you can use GPRS while talking on the phone without hanging up. Note though that depending on hardware and networking, simultaneous data transmission and voice call alerting (let alone performing calls) might not be possible.

Since FSO is a middleware it offers no GUI, however it's fairly easy to use the methods available using any dbus tool.

The methods available:
[METHOD] org.freesmartphone.GSM.PDP.ActivateContext() -> ()
[METHOD] org.freesmartphone.GSM.PDP.DeactivateContext() -> ()
[METHOD] org.freesmartphone.GSM.PDP.GetContextStatus() -> ( s:status, a{sv}:properties )
[METHOD] org.freesmartphone.GSM.PDP.GetCredentials() -> ( s:apn, s:username, s:password )
[METHOD] org.freesmartphone.GSM.PDP.InternalStatusUpdate( s:status, a{sv}:properties ) -> ()
[METHOD] org.freesmartphone.GSM.PDP.SetCredentials( s:apn, s:username, s:password ) -> ()
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus( s:status, a{sv}:properties )

Use ''mdbus -s -l'' to monitor the emitted signals. Signals will look roughly like this:

:ActivateContext
<pre>
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus
from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'outgoing'),
dbus.Dictionary({}, signature=dbus.Signature('sv')))
</pre>
:Once the connection is established (takes 3-4 seconds for me) a new signal is emitted
<pre>
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus
from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'active'),
dbus.Dictionary({}, signature=dbus.Signature('sv')))
</pre>
:DeactivateContext
<pre>
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus
from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'release'),
dbus.Dictionary({}, signature=dbus.Signature('sv')))
</pre>

== Using scripts ==

While we wait for the preferences part of FSO to be completed (and a GUI), we can use two shell scripts. You need to know three things to successfully connect via GPRS (your carrier should provide this information to you):
* the APN to use,
* the username, and
* the password.
If your APN has no username or password, you must still provide a string to satisfy the framework's input requirements. Entering bogus data, such as the "x" above, will suffice.

To connect, put the following in a file and make it executable (<code>chmod +x gprs-on.sh</code>):
<pre>
#!/bin/sh
APN="internet.parlino.se"
USERNAME="x"
PASSWORD="x"
BUSNAME="org.freesmartphone.ogsmd"
OBJECTPATH="/org/freesmartphone/GSM/Device"
SETMETHODNAME="org.freesmartphone.GSM.PDP.SetCredentials"
ACTMETHODNAME="org.freesmartphone.GSM.PDP.ActivateContext"
mdbus2 -s $BUSNAME $OBJECTPATH $SETMETHODNAME $APN "$USERNAME" "$PASSWORD"
mdbus2 -s $BUSNAME $OBJECTPATH $ACTMETHODNAME
</pre>
To disconnect, use the following method instead (<code>chmod +x gprs-off.sh</code>):
<pre>
#!/bin/sh
BUSNAME="org.freesmartphone.ogsmd"
OBJECTPATH="/org/freesmartphone/GSM/Device"
METHODNAME="org.freesmartphone.GSM.PDP.DeactivateContext"
mdbus2 -s $BUSNAME $OBJECTPATH $METHODNAME
</pre>
The ''on'' script, using the ActivateContext method, will:
* setup a ppp interface (normally ppp0) (and assign IP address)
* setup (replace) the default route
* setup DNS
with settings received from the ISP.

For a list of known APN:s, see the [[GPRS APN table]].

== Troubleshooting ==

* When a something like '''org.freedesktop.DBus.Error.UnknownMethod''' appears make sure that:
** frameworkd is started of course
** That the method did not hide in an other place than expected follow the white [[D-Bus|Rabbit]]
* Online script runs without error but pppd did not start
** use '''logread''' to debug....
** Maybe the kernel module ppp-generic is not loaded, try modprobe. ( you can do '''echo ppp-generic > /etc/modutils/ppp-generic''' and then '''update-modules''' to load the module at boot time )
** Maybe you have to do a '''mknod /dev/ppp c 108 0'''
* No MUX Channels available
** Means that the frameworkd has no free channel available to connect to the GSM Modem.
** Restart the frameworkd and the phone Application (aka ophoned or zhone). Works fine for me.
* LCP ProtRej id=0x* 80 fd 01 01 00 15 12 06 00 00 00 00 1a 04 78 00 18 04 78 00 15 03 2f
** Means CHAP authentication is not acceptable with this provider and must be disabled
** Append refuse-chap,refuse-mschap,refuse-mschap-v2,refuse-eap,receive-all to /etc/ppp/options with each option on a new line
* MISC Troubleshooting
** Switch the frameworkd loglevel to DEBUG (/etc/frameworkd.conf)
** use the source!

== Using a GUI ==
[[Framework-settings]]

== SHR (Unstable??) ==
SHR is based on FSO, so I think its GPRS settings should be found here. Shr has its native setting manager which has Connectivity sub-panel which in turn has settings for GPRS. Its very intutive and your GPRS/FR should be up and running in no time.

To enable gprs on-demand you need to do some manual changes in framework code.
Alter, /usr/lib/python2.6/site-packages/framework/subsystems/ogsmd/modems/abstract/modem.py
as:
--- orig.modem.py Sat Jul 18 02:13:29 2009
+++ modem.py Sat Jul 18 02:13:06 2009
@@ -76,6 +76,8 @@
'proxyarp',
'replacedefaultroute',
'usepeerdns',
+ 'demand',
+ 'idle', '20',
]

self._data["pppd-does-setup-and-teardown"] = True # default
is using connect and disconnect scripts

Alter, /usr/lib/python2.6/site-packages/framework/subsystems/ogsmd/modems/abstract/pdp.py
as:
--- orig.pdp.py Sat Jul 18 04:20:13 2009
+++ pdp.py Sat Jul 18 04:19:03 2009
@@ -219,7 +219,8 @@
"""

PPP_DAEMON_SETUP["/etc/ppp/ip-down.d/92removedns"] = """#!/bin/sh -e
-echo nameserver 127.0.0.1 > /etc/resolv.conf
+echo nameserver 208.67.222.222 > /etc/resolv.conf
+echo nameserver 208.67.220.220 >> /etc/resolv.conf
"""

PPP_DAEMON_SETUP[PPP_PAP_SECRETS_FILENAME] = '* * "%s" *\n' % ''

modem.py needs to be updated to setup idle timeout and auto reconnect. While pdp.py needs to be updated so ppp idle timeout resets /etc/resolv.conf to OpenDNS servers

Now, just fire up settings panel (need to be done once per boot) and in connectivity click connect for Gprs...for me it doesn't show connected anymore...but then I don't really care about that as long as the connection works :). To do this on bootup automatically check out the next section.
=== Enable on-demand GPRS at boot ===
* Put init-gprs.py and kill-init-gprs.py in /usr/bin and make them executable.
* Put bootup-gprs in /etc/init.d and make that executable too.
* Next execute 'update-rc.d bootup-gprs defaults 99 01' to install the init script on bootup and shutdown

init-gprs.py
#!/usr/bin/env python
import dbus
from dbus.exceptions import DBusException

from dbus.mainloop.glib import DBusGMainLoop
import gobject
DBusGMainLoop(set_as_default=True)
loop = gobject.MainLoop()

bus = dbus.SystemBus()

def activate_gprs():
print "Activating GPRS"
local_gsm_obj = bus.get_object("org.freesmartphone.ogsmd", "/org/freesmartphone/GSM/Device")
pdpIFace = dbus.Interface(local_gsm_obj, "org.freesmartphone.GSM.PDP");
pdpIFace.ActivateContext("airtelgprs.com", "x", "x")

def on_sim_ready(ready):
print "On ready received: " + str(ready)
if not ready:
print "Waiting for SIM to get ready...its still not up"
return
if loop.is_running():
loop.quit()
activate_gprs()

needLoop = True
try:
gsm_device_obj = bus.get_object("org.freesmartphone.ogsmd", "/org/freesmartphone/GSM/Device")
simIFace = dbus.Interface(gsm_device_obj, "org.freesmartphone.GSM.SIM")

if simIFace.GetSimReady():
print "Sim was already up"
needLoop = False
activate_gprs()
else:
print "Sim is not ready...need to wait"
simIFace.connect_to_signal("ReadyStatus", on_sim_ready)
except DBusException:
print "caught the exception->"
bus.add_signal_receiver(on_sim_ready, signal_name='ReadyStatus', \
dbus_interface='org.freesmartphone.GSM.SIM', \
bus_name='org.freesmartphone.ogsmd')

if needLoop:
loop.run()

kill-init-gprs.py
#!/usr/bin/env python
import dbus

bus = dbus.SystemBus()
gsm_device_obj = bus.get_object("org.freesmartphone.ogsmd", "/org/freesmartphone/GSM/Device")
pdpIFace = dbus.Interface(gsm_device_obj, "org.freesmartphone.GSM.PDP")
pdpIFace.DeactivateContext()

bootup-gprs
#! /bin/sh

NAME=bootup-gprs
PATH=/bin:/usr/bin:/sbin:/usr/sbin

echo "1::$1::/var/run/${NAME}"
case "$1" in
start)
if [ -f /var/run/${NAME} ]; then
echo "Initial gprs connection is already running. If you think its not then delete /var/run/${NAME}"
else
echo "Starting initial gprs connection"
init-gprs.py > /var/run/${NAME} &
fi
;;
stop)
echo "Stopping initial gprs connection"
kill-init-gprs.py
rm -f /var/run/${NAME}
;;
restart|force-reload)
$0 stop
$0 start
;;
*)
echo "Usage: /etc/init.d/bootup-gprs {start|stop|restart|force-reload}"
exit 1
;;
esac

exit 0

Note: We are updating the framework file which can be updated by any of the frameword update and one need to repeat the update (well..until a nifty setting comes into setting panel somewhere :)

== See also ==
* [[GPRS]]
* [[OpenmokoFramework/mdbus]]

[[Category:FSO]]
[[Category:GPRS]]

Manuals/SHR

2010-01-17T19:02:31Z

Ott--: /* Disable the standard Lock Screen, go back to the old LOCKED */

{{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

# Please note [[#opkg_upgrade_issues]]
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:

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 µ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]]

If you have trouble logging yourself in via ssh have a lock here: [[USB_Networking#The_login]]

====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 if your release is >=: 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.

If you are using Qi and installation on a µSD card, you can change the kernel parameterin /boot/append-GTA02 to:

loglevel=1

===Disable the standard Lock Screen===

And go back to the old LOCKED again

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.

In '''Illume Settings''' => '''Input''' => '''Key Bindings''', bind the key '''XF86Phone''' to '''Desktop Simple Lock'''

===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. The unwanted suspending while upgrading can be avoided by using the below alias.
}}

You can request the CPU resource (temporary non-suspend) while executing opkg by inserting this in file /etc/profile :
alias opkg="fsoraw -f -r CPU -- opkg"

To make the alias work at once for the current boot execute:
alias opkg="fsoraw -f -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

==== .ssh/config as an alternative ====

An alternative way is to add your phone to your ~/.ssh/config file.

This does not get lost after a reinstallation of your system.

If the config does not exist yet, create one and paste this into it:

Host neo
HostName 192.168.0.202
Compression no
User root

'''Note''': Compression no does disable ssh compression as your neo is slow enough.

Now you can access your phone like this:

ssh neo

Which is shoter than this ;)

ssh root@neo

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

Manuals/SHR

2010-01-17T19:01:00Z

Ott--: /* System Customizing */ go back to the old screenlock

{{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

# Please note [[#opkg_upgrade_issues]]
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:

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 µ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]]

If you have trouble logging yourself in via ssh have a lock here: [[USB_Networking#The_login]]

====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 if your release is >=: 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.

If you are using Qi and installation on a µSD card, you can change the kernel parameterin /boot/append-GTA02 to:

loglevel=1

===Disable the standard Lock Screen, go back to the old LOCKED===

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.

In '''Illume Settings''' => '''Input''' => '''Key Bindings''', bind the key '''XF86Phone''' to '''Desktop Simple Lock'''

===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. The unwanted suspending while upgrading can be avoided by using the below alias.
}}

You can request the CPU resource (temporary non-suspend) while executing opkg by inserting this in file /etc/profile :
alias opkg="fsoraw -f -r CPU -- opkg"

To make the alias work at once for the current boot execute:
alias opkg="fsoraw -f -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

==== .ssh/config as an alternative ====

An alternative way is to add your phone to your ~/.ssh/config file.

This does not get lost after a reinstallation of your system.

If the config does not exist yet, create one and paste this into it:

Host neo
HostName 192.168.0.202
Compression no
User root

'''Note''': Compression no does disable ssh compression as your neo is slow enough.

Now you can access your phone like this:

ssh neo

Which is shoter than this ;)

ssh root@neo

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

Distributions

2009-10-04T21:31:52Z

Ott--: /* Qalee */ typo work => works

{{Languages|Distributions}}

{|align=left
|__TOC__
|}

== About distributions ==
Openmoko distributions are designed to run on various mobile devices, with the primary aim of supporting Openmoko Inc.'s [[GTA01:Neo 1973|Neo 1973]] and [[Neo FreeRunner]] phones. They are GNU/Linux distributions -- complete operating systems including user applications. You can install any of them on your phone or even have a dualboot system with two distributions installed. For downloads see [[Download]], for installation instructions see [[Flashing the Neo FreeRunner]].

Besides, Openmoko distributions also run on [[Supported devices|other]] mobile devices and some other software distributions also run on the phones of Openmoko Inc.

=== Choosing a distribution ===

According to a survey from August 2009 SHR is by far the most used distribution (60%), followed by Om (15%, [[Om 2007]], [[Om 2008]] and [[Om 2009]] counted as one distribution), [[Debian]] (6%), the Debian-based [[Hackable:1]] (6%), [[Qt Extended Improved]] (5%) and [[Android]] (4%).[http://doodle.com/sd2c8d8snr23eeqq] As the development of Om 2009 basically stopped after this poll even more people might switch to SHR.

{| class="wikitable" style="float:right;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|Distributions
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* Openmoko (official)
** [[Om 2009]]
** [[Om 2008]]
** [[Om 2007.2]]
* Om Community
** [[Android]]
** [[Debian]]
** [[Gentoo]]
** [[Hackable:1]]
** [[Mer]]
** [[Neovento]]
** [[OpenWrt]]
** [[Qt Extended Improved]]
** [[SHR]]
</div>
|-
|}

=== Please note ===

* Stable in the FreeRunner world does not mean the same thing as stable in the Debian world.
* Most distributions use the same bootloader, kernel, drivers and hardware. Therefore, the same low level bugs are commonly found in all distributions. The latest and greatest software usually has most bug fixes, plus a whole set of new fresh bugs.
* Most of these distributions also have package repositories. It is a BAD idea to feed from another distribution's repository. E.g. see [[installing alien package]]s.
* Upgrade path between these distributions are mostly not tested, thus updating by changing the feeds will most likely end in broken packages or even an unbootable system. It is advisable to reflash the whole filesystem with [[dfu-util]] to switch between the different distributions, with the reminder that a dual-boot setup (e.g. via [[Booting from SD|MicroSD]] or [[Booting from NFS|NFS]]) can be used.
* [[Marketing Mistakes]] and pre-installed distributions.

== Official Openmoko Releases ==

'Release targets' offered by Openmoko Inc. are built out of different branches of the [[OpenEmbedded]] metadistribution source tree.

=== Om series ===

* '''[[Om 2009]]''' is intended to be the new distro; it is not a simple follow-on from [[Om 2008]]. It is based on the [http://freesmartphone.org freesmartphone.org] milestone 5.5 framework.

{{Main|Om2009}}

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

{{Main|Om 2008}}

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

{{Main|Om 2007.2}}

== Community Distributions ==

=== Android ===
[http://code.google.com/android/ Android] is a software stack for mobile devices developed by the [http://www.openhandsetalliance.com/ The Open Handset Alliance.] Openmoko is fully supporting Android running on the Freerunner.

Android has now reached a point where it is usable on the FreeRunner as an everyday phone, there are, however, still some caveats. Check out the main Android section of the wiki for more info.

{{Main|Android}}You can also visit the user web page for [http://wiki.openmoko.org/wiki/User:Seanmcneil3 Sean McNeil] for some more info.

=== Debian ===
[[Debian]] is "the universal operating system". It comes with thousands and thousands of packages (most of them designed for desktops or servers so far). So in the words of Joachim "nomeata" Breitner from the [http://wiki.debian.org/Teams/DebianFSO pkg-fso] team, this is not really a distribution in the Openmoko sense of the word, but rather a different underlying system for Openmoko distributions. At the moment, we ship the software from the FSO stack, but hopefully we’ll also have, for example, the SHR software in our archive. So for now, Debian is a different way of installing FSO, which takes more space and provides more programs :-)

{{Main|Debian}}

=== Gentoo ===
[[Gentoo]] is all about choices. When installing Gentoo, this is made clear to you several times -- you can choose how much you want to compile yourself, how to install Gentoo, what system logger you want, etc. Gentoo is a fast, modern metadistribution with a clean and flexible design. Gentoo is built around free software and doesn't hide from its users what is beneath the hood. Portage, the package maintenance system which Gentoo uses, is written in Python, meaning you can easily view and modify the source code. Gentoo's packaging system uses source code (although support for precompiled packages is included too) and configuring Gentoo happens through regular textfiles. In other words, openness everywhere.

{{Main|Gentoo}}

=== Hackable:1 ===
Hackable1 is a community distribution for hackable devices like the Neo Freerunner. It is based on Debian and 2007.2 userland which has been abandoned by Openmoko. It follows the GNOME mobile platform.
{{Main|Hackable:1}}

=== Mer ===
[[Mer]] is a distribution based on [[Maemo]].

=== Mokotouch ===
[[MokoTouch]] wants to be a replacement for the OM Distribution. It will contains apps for system settings and other useful apps like, mail client, Photo and Maps Viewer and maybe other fun things. It's fully written in C++ using Qt 4.5 Embedded. and it runs using Framebuffer, so no X11 Required. http://th30z.netsons.org/mokotouch/index.html

[http://www.youtube.com/watch?v=yr821OgnvYc Video]

=== neovento ===
[[neovento]] (ex FYP) is a [[Debian|Debian on Freerunner]] based [[Distributions|distribution]] which uses [http://lxde.org/ LXDE] and [[Zhone]] on top. It is a [http://freeyourphone.de FreeYourPhone.de] community project.

{{Main|neovento}}

=== OpenWrt ===
[[OpenWrt]] is described as a Linux distribution for embedded devices.

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

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

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

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

{{Main|OpenWrt}}

=== Qalee ===
[[Qalee]] is a phone environment develloped in Qt4 above the fso stack. It works on the freerunner under any distribution that support Qt4. http://www.openmoko.openmatica.es/QALEE/

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

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

{{Main|Qt Extended Improved}}

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

{{Main|QT Moko}}

=== SHR ===

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

{{Main|SHR}}

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

=== Abandoned ===

==== FDOM (FAT and Dirty Openmoko) ====

[[FDOM]] is a distribution based on Openmoko's currently supported image, updated with many ready-to-use applications and with fixes posted in the mailing lists. A combination of applications (everything goes) and fixes to demonstrate the capabilities of the Freerunner and to have a functional phone (sort of). This all while retaining the ability to update through the official feeds.

{{Main|FDOM}}

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

== Features by distribution/release target ==

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

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

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

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

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

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

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

=== Images ===
Latest and stable combinations for Neo FreeRunner gta02
{|class="wikitable" border="1" cellpadding="5" cellspacing="0"
| || '''OM''' || '''[[Qt Extended]]''' || '''[[Android]]'''
|-
| current bootloader || [[U-boot|U-Boot]] from [http://downloads.openmoko.org/distro/releases/Om2008.9/ OM daily] version [http://downloads.openmoko.org/] || [[U-boot|U-Boot]] from [http://downloads.openmoko.org/repository/experimental/ OM daily] version [http://downloads.openmoko.org/daily/gta02v5_and_up-u-boot.bin gta02v5_and_up] ||
|-
| future bootloader || [[Qi]] from [http://people.openmoko.org/andy/ Andy] latest qi-andy.udfu || [[Qi]] from [http://people.openmoko.org/andy/ Andy] latest qi-andy.udfu ||
|-
| splash || [[Configuring_the_boot_splash_screens|U-Boot]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest splash.gz || [[Configuring_the_boot_splash_screens|U-Boot]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest splash.gz ||
|-
| kernel || [[Linux]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest uImage.bin || [[Linux]] see [[Qt_Extended]] page for latest version || [[Linux]] from [http://koolu.org/releases/ koolu]
|-
| modules || ? || [[Linux]] from [http://moko.mwester.net/download/ mwester] latest modules-min-gta02-mwester-stable.tgz or modules-all-gta02-mwester-stable.tgz ||
|-
| rootfs || [[Main_Page|OM]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest rootfs.jffs2 || See [[Qt_Extended]] for latest rootfs || [[Android]] from [http://koolu.org/releases/ koolu]
|}

Footnotes:

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

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

(*) unstable

==Quick download page==

[[Download]]

== See also ==

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

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

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

[[Category:Distributions| ]]

Npkg

2009-07-28T11:46:12Z

Ott--: /* Features */

This package manager was created to replace [[opkg]] in low memory environments. (openmoko/slugos/more?)

It will hopefully be both memory efficient and fast, though the emphasis is on memory efficiency, since we have unlimited time though not unlimited memory.

It is not yet in development, it's in the characterization stage. Please feel free to help, as this is the most important part.

Please read the introduction section
source code: git://github.com/tasn/npkg.git

=Introduction=
npkg (Nano pkg) conforms to the following coding convention:
[http://wiki.shr-project.org/trac/wiki/Coding%20Conventions Coding Conventions]
Please read and follow.

Please help and add ideas to the projects wiki pages. (for instance the features page)

=Features=
This list includes all the actions it should be able to do (even trivial ones)

Should be able to:
# Install
# Remove
# Upgrade
# Update
# Handle configuration files changes
# Run without stopping and asking questions, like overwriting config files (save new config as <pkg.conf>.new resp. <pkg.conf>.old)
# Ignore dependencies
# Restrict certain packages upgrades
# Check if a new version of itself exists before installing other packages.
# List all/installed/upgradeable packages
# search for a package by name/description
# download only
# probe all info about a package
# be able to set different config file
# be able to set different root dir
# be able to force downgrade
# be able to tell whether to cache or not to cache packages
# be able to do a "dry run"
# ignore restrictions (like deps/conflicts and such)
# progress indication!
# multi repos?
# install from repo/url/local
# when upgrading, confirm the list of pkgs to be upgraded before actually doing the upgrade.

=API=
The basic design is a library, this section lists the needed api.

=Design choices=
It seems like using sqlite3 and libcurl are the best solutions for our purposes.
I'm considering using glib as well for data structures, though about that I'm still not sure and would like someone to help me think about pros and cons.

It'll probably be written in C and maybe at first will use shell (bash?) scripts for help when needed. (although target is C only).

In conclusion:

Probable dependencies:
# sqlite3
# libcurl

=Volunteers=
Please add yourself to this list if you think you'd like to give us a hand (specify nick/name, area of expertise and a way to contact)

# tasn - programmer - #openmoko-cdevel@freenode

[[Category:Package management]]

Hackable:1

2008-11-26T16:03:31Z

Ott--: /* SSH */

[http://www.hackable1.org/ Hackable1] is a community [[Distributions|distribution]] for hackable devices like the Neo Freerunner. It is based on Debian and implements the GNOME mobile platform.

'''Status:''' ''Work in Progress''

= Installation =

[http://www.hackable1.org/hackable1/ Download] the tarball and extract then on the 2 partitions from your microSD card

= Usage =

== Buttons ==

* short press on the AUX button brings up the keyboard
* short press on the Power button kill the application in the foreground
* long presses bring up menus after half a second
* the aux menu lets you search for BT keyboard and switch USB modes

== SSH ==

There seams to be a root password by default : even with "PermitEmptyPasswords yes" on ''/etc/ssh/ssh_config'', you can't log in with an empty password. Simply set a new password with the '''passwd''' command it a already available terminal

After installing the rootfs, /root/.ssh/authorized_keys contains an entry for m@one - is this an intended backdoor for a well known m?

== Networking ==

The PC (192.168.0.200) is configured as the DNS server. You can [[Usb_networking#Configure_Default_Neo_DNS|modify]] this.

= Issues =

* The GSM can't be powered off with no SIM card inserted, he will persist on registering.
[[Category:Distributions]]

Talk:Android

2008-11-07T16:49:13Z

Ott--:

awesome

== Scanning for Files That Use the ARMv5TE ISA ==

"exit -1" does not work with every /bin/sh. Anyway, if you want to give a hint, make it look like this:
<pre>
if [ $# -ne 1 ]; then
echo "usage: $0 android-directoy"
exit 255
fi
</pre>

Openmoko Local Groups: Berlin

2008-10-25T15:59:08Z

Ott--: /* Possible Participants */

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

=== Mailing list ===
We have set up a mailinglist a freelists.org. To subscribe either send a mail with the topic 'subscribe' to openmoko-users-berlin-request@freelists.org OR through the web interface: http://www.freelists.org/list/openmoko-users-berlin.

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

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

[[Category:Openmoko Local Groups]]

FreeRunner: Selected Blogs and Articles

2008-09-21T17:05:57Z

Ott--: /* English */

{{Neo FreeRunner Menu}}

{|align=right
|__TOC__
|}

This page contains references to personal blog entries and reflections of the mind about FreeRunner. Please see [[Press_Coverage]] for more official pieces of information.

Newest on top.

== English ==

=== September 2008 ===
* [http://nop0.blogspot.com/2008/09/revive-openmoko-neo-freerunner-with-usb.html Revive the Freerunner with USB power]
* [http://nop0.blogspot.com/2008/09/having-multiple-distributions-on.html Multiple distributions on SD card] (work in progress)

=== August 2008 ===
* Andrénalin heavy metal chainsaw!!! [http://andre.web-yard.de/blog/2008/08/03/neo-freerunner-rocks-hard-rides-free/ http://andre.web-yard.de/blog/2008/08/03/neo-freerunner-rocks-hard-rides-free/]
* Monochrome Mentality [http://monochromementality.com/index.php/blog/show/FSO-Milestone-II-Phot-Safari-and--rant.html FSO Milestone II Photo Safari and rant]

=== July 2008 ===
* technocrat.net (Charles E. Hill) [http://technocrat.net/d/2008/7/27/46753 Openmoko Neo FreeRunner - Part 1]
* Rabble.ca (Wayne MacPhail) [http://www.rabble.ca/news_full_story.shtml?x=73765 Introducing the anti-iPhone]
* Canadia Blog [http://bieberphoto.com/canadia/index.php/2008/07/openmoko-neo-freerunner-review/ Neo FreeRunner Review]
* Holden Karau [http://blog.holdenkarau.com/2008/07/unboxing-openmokofreerunner-including.html Unboxing the Openmoko/FreeRunner including the spares kit, debug board]
* Dave Fayram [http://www.vimeo.com/1366042 Openmoko Train Wreck] (video review)
* Dave Fayram [http://www.vimeo.com/1366923 More Openmoko Train Wrecking (Now with Qt!)] (video review)
* Wired's Gadget Lab Podcast: [http://blog.wired.com/gadgets/2008/07/gadget-lab-po-1.html Summary] and [http://audio.sonibyte.com/audio/7394.mp3 mp3] (discussion starts at 5:50)
* jThinks: [http://jthinks.com/index.php/freerunner-at-last/ FreeRunner, at last]
* Holden's Blog: [http://blog.holdenkarau.com/2008/07/unboxing-openmokofreerunner-including.html Unboxing the Openmoko/FreeRunner including the spares kit, debug board]
* Wolfmans Howlings: [http://blog.wolfman.com/articles/2008/07/11/openmoko-freerunner-first-impressions Openmoko FreeRunner first impressions]
* Free Software Foundation (John Sullivan): [http://www.fsf.org/blogs/community/5-reasons-to-avoid-iphone-3g 5 reasons to avoid iPhone 3G]
* Joseph Reeves: [http://blogs.thehumanjourney.net/finds/entry/20080710 FreeRunner retail unboxing]
* Ars Technica: [http://arstechnica.com/reviews/os/open-moko-software.ars Ars Technica First Look at Openmoko]
* Juan Lucas Domínguez Rubio: [http://gvsigmobileonopenmoko.wordpress.com/2008/07/02/first-experience-with-openmoko/ First experience with Openmoko]
* Philipp Kern: [http://www.philkern.de/weblog/en/neo_freerunner.html Neo FreeRunner: First impressions]

=== June 2008 ===
* Andrzej Zaborowski: [http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket/ Accelerating in my pocket]

=== May 2008 ===
* Kevin Dean: [http://www.monochromementality.com/index.php/blog/show/Day-One-Openmoko-FreeRunner.html Day One: Openmoko FreeRunner]

==== Earlier ====
* Michael Shiloh: [http://gettingstartedopenmoko.wordpress.com/ Getting Started with Openmoko] (many blog entries in this dedicated blog)

== French (français) ==
* blog, wiki and forum in french about Openmoko: http://www.openmoko-fr.org
=== July 2008 ===
* Xavier Cremaschi : [http://wiki.troulite.fr/index.php/NeoFreerunner FreeRunner French Companion Wiki] This page is a (quite big) summary of my understanding and experimentations : what are the different software stacks, how you can install them (flashing or dual boot), how you can configure them. Note that everything comes from this wiki or mailing lists, I don't claim paternity for anything except translation and feedback.

== Italian (italiano) ==

=== August 2008 ===
* Lo schiaffo : [http://www.loschiaffo.org/telefono-open-source/ Opensource telephone]
* TuguLab : [http://blog.tugulab.org/2008/08/13/come-configurare-openmoko-sul-neofreerunner-e-utilizzarlo/ Come configurare Openmoko sul NeoFreeRunner e utilizzarlo!] by jollyr0ger

[[Category:Community]]

Distributions

2008-09-18T23:45:41Z

Ott--: /* FDOM (FAT and Dirty Openmoko) */ typo kernel instead of kenel

{{Languages|Distributions}}

{| class="wikitable" style="float:right;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|Distributions
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* Openmoko (official)
** [[Om 2008.8]]
** [[Om 2007.2]]
** [[OpenmokoFramework|FSO]]
* Community
** [[SHR]]
** [[FDOM]]
* Other
** [[Qtopia]]
** [[Debian]]
** [[Gentoo]]
</div>
|-
|}
Openmoko distributions are designed to run on various mobile devices, with the primary aim of Openmoko Inc.'s [[Neo 1973]] and [[Neo FreeRunner]] phones. They are Linux distributions; complete operating systems with more or less user applications. You can install any of them on your phone or even have a multiboot system with two distributions installed.

While the Openmoko distributions will run on [[Supported devices|other mobile devices]] too, some other software distributions will also run on the Openmoko Inc. phones (see below).

For downloads see [[Download]], for installation instructions see [[Flashing the Neo FreeRunner]].

== About distributions ==

To be technically precise, 2007.2, 2008.8, FSO and SHR of these are not directly independent distributions, but different 'release targets'. They are built out of different branches of the [[OpenEmbedded]] metadistribution source tree, e.g. 2007.2 and 2008.8 are to each other like Ubuntu Gutsy is to Kubuntu Hardy. A [http://docs.openmoko.org/trac/roadmap roadmap] showing the number of remaining active tickets (in other words, bugs) is available on the bug [http://docs.openmoko.org/trac/ trac]king system (also accessible with the DOCS link at the top of every page).

One should only use feeds from packages of the same source-branch, else 'stuff will break', similar to like using .debs from Hardy on a Gutsy base system. Also note that there is NO supported upgrade path between these at the moment, thus updating by changing the feeds will most likely end in broken packages or even a unbootable system. Thus please always use [[dfu-util]] to switch between the different 'distributions' for now or install them in a dual-boot setup (e.g. via sdcard or NFS).

== Openmoko Inc. driven release targets ==

=== Om 2008.8 (ASU, April/August Software Update) ===

Om 2008.8 has been started to integrate the [http://trolltech.com/products/qtopia Qtopia] stack - on X11 - with a new set of graphically pleasing applications based on the Enlightenment Foundation Libraries. ASU is the internal name and is known as Om 2008.8 upon its release on August 8, 2008. Qtopia is a more mature product than the GNOME Mobile stack and you can expect all the standard feature phone applications to work in a solid way. It uses the Qtopia phone server. Since - contrary to standard Qtopia - it does not directly use the framebuffer, non-Qt applications can safely share the screen with Qt applications.

Om 2008.8 is maintained as "'''ASU-stable'''" with continuous updates.

* [[Om2008.8|Om 2008.8]]
* [[Downloads#Om_2008.8_images_.28ASU.29|Download > Om 2008.8 images (ASU)]]

=== Om 2007.2 (GTK) ===

[[Om 2007.2]] is for people who are familiar with the [http://www.gnome.org/mobile/ GNOME Mobile] initiative and who want to write applications that run on multiple devices running (parts of) GNOME Mobile. This includes Maemo, which runs on the Nokia Internet Tablets. The strength of the GTK+ stack is a UI and programming environment similar to what you run on your Linux desktop, if you’re into GNOME. The GTK+ has PIM applications based on the Evolution Data Server and runs the gsmd phone server. Although you can use them, the applications are still pretty rough und unfinished. Some people have problems with the stability of the phone server.

* [[Om 2007.2]]
* Availabilty: [http://downloads.openmoko.org/repository/Om2007.2/ Official Buildhost] and [[MokoMakefile]] support for development builds
* [[Downloads#Openmoko_2007.2_images_.28GTK.29|Download]]
* Several videos of this stack by [http://uk.youtube.com/user/freeyourphone Youtube user freeyourphone] and [http://uk.youtube.com/watch?v=U05kZfURPig&NR=1 video review by BVB Tech]
This is the base-system which is installed on FreeRunner when it leaves the factory.

2007.2 development driven by openmoko inc. has basically stopped and resources are allocated in favor of 2008.8, while the community currently does the effort to 'rescue' the 2007.2 telephony apps and pull them to the future middleware from FSO (see SHR).
thus patches are still welcome, especially if they help development of SHR.

=== FSO - freesmartphone.org ===

FSO has been started to overcome the deficiencies both of the 2007.2 and the 2008.8 stack, namely to come up with an extensible framework that gives developers the infrastructure they need to create solid and exciting software products based on the Openmoko platform. An infrastructure that supports competing UIs while we can collaborate on developing services, making the framework strong . Here, the focus is on stable highlevel services that you can access from whatever language or UI that supports [http://dbus.freesmartphone.org/ dbus]. People report that despite its infancy, e.g. the phone server part in FSO is already more solid than anywhere else.

It is not really intended as future release-target, but used as a 'vessel' or 'container' for the development and testing of the new, future middleware.

The applications installed are intended as test-tools for the new middleware and not as fully featured, end user oriented applications. (even if it looks that way sometimes)

In the words of Mickey, project manager:

<blockquote>FSO is only a distro because "we can" (thanks to OpenEmbedded). Zhone is an independent UI application based on the FSO framework to facilitate testing. If you want to build own UIs or custom applications on the forthcoming Openmoko dbus service framework, then the FSO-image is a good starting point.</blockquote>

* [[FSO]]
* [http://trac.freesmartphone.org:8000/trac-example Development tracker]
* [http://downloads.openmoko.org/framework/milestone3/ Download milestone 3]
* [http://freesmartphone.org freesmartphone.org]
* [http://shr.bearstech.com/ fso-testing and fso-unstable images and feeds] (maintained by Rod Whitby, MokoMakefile author)

== Openmoko Community driven release targets ==

=== SHR - Stable Hybrid Release ===

Stable Hybrid Release is a combination of the middleware from FSO, some of the 2007.2 GTK software (telephony-ui, pim), and Om2008.8 that provides all of the functionality of the 2007.2 software, but with the stability of the FSO.

* [[Stable Hybrid Release]]

=== FDOM (FAT and Dirty Openmoko) ===

[[FDOM]] is a rootfs/kernel image ready to flash of an OM2008.08-updates distribution with some apps already installed and some fixes posted in the lists done. Download from http://compartida.net/openmoko/FDOM . Use wget -c to retrieve the files because of the server seems to cut the connection time to time, and check the files MD5 hashes afterwards.

== Non-Openmoko distributions ==

These are not Openmoko (and OE) based distributions. These are an alternatives you can run on your Openmoko phones.

=== Qtopia ===

The Qtopia distribution from [http://www.trolltech.com Trolltech], it aims to provide a ready-to use image for Openmoko devices.

* [[Qtopia]]
* Download: [http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 Qtopia.net]

=== Debian ===

In the words of Joachim "nomeata" Breitner from the [http://wiki.debian.org/Teams/DebianFSO pkg-fso] team:

:It’s not really a distribution in the Openmoko sense of the word, but rather a different underlying system for Openmoko distributions. At the moment, we ship the software from the FSO stack, but hopefully we’ll also have, for example, the Stable Hybrid Release software in our archive.

:So for now, Debian is a different way of installing FSO, which takes more space and provides more programs :-)

* [[Debian]]

=== Gentoo ===

* [[Gentoo]]
== Features by distribution/release target ==

=== Connectivity ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Telephony || {{Yes}} || {{Yes}} || {{Yes}} || N/A || {{Yes}} || {{Yes}} (1)
|-
| SMS || {{Yes}} || {{Yes}} || {{Yes}} || N/A || {{Yes}} || {{Yes}} (1)
|-
| [[GPRS]] || Not through UI || Not through UI || Not through UI || N/A || {{No}} (3) || {{Yes}} (1)
|-
| WiFi || {{Yes}} || Not through UI || {{Yes}} (*) || N/A || {{Yes}} || {{Yes}}
|-
| VoIP || ?? || ?? || ?? || ?? || ?? || {{Yes}}
|-
| Bluetooth || {{Yes}} || {{No}} || {{Yes}} || N/A || {{Yes}} || {{Yes}}
|-
| GPS || {{Yes}} (1) || {{Yes}} || {{Yes}} (1) || N/A || {{Yes}} (1) || {{Yes}} (1)
|-
|}

=== User Interaction ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Stylus friendly || {{Yes}} || {{Yes}} || {{Yes}} || N/A || {{Yes}} || {{Yes}}
|-
| Finger friendly || Partially || Partially || Partially || N/A || {{Yes}} || {{No}}
|-
| Accelerometer || {{No}}|| {{No}} || {{Yes}} [[Gestures|(1)]] || N/A || {{No}} || {{No}}
|-
|}

=== Applications ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Terminal || Basic (2) || {{Yes}} || {{Yes}} (1) || N/A || {{Yes}} || {{Yes}}
|-
| PIM || {{Yes}} || {{No}} || {{Yes}} || N/A || {{Yes}} || {{Yes}} (1)
|-
| Phonebook || {{Yes}} || {{Yes}} || {{Yes}} || N/A || {{Yes}} || {{Yes}} (1)
|-
| Dialer || {{Yes}} || {{Yes}} || {{Yes}} || N/A || {{Yes}} || {{Yes}} (1)
|-
| Web Browser || {{Yes}} (1) || ? || {{Yes}} (1) || ? || {{No}} || {{Yes}} (midori)
|-
| Mail Client || ? || ? || {{Yes}} || ? || {{Yes}} || {{Yes}} (1)
|-
| XMPP Client || {{Yes}} (1) || ? || {{Yes}} [[Instant Messaging|(1)]] || ? || {{No}} || {{Yes}} (1)
|-
| Media Player || {{Yes}} || ? || {{Yes}} (1) || ? || {{Yes}} || {{Yes}} (1)
|-
|}

=== Toolkits / Runtimes ===
{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| GTK+ || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Yes}}
|-
| QT/Qtopia || No || {{Yes}}? || {{Yes}} || {{Yes}}? || {{Yes}} || {{Yes}}
|-
| Middleware || gsmd/neod || freesmartphone.org || qtopia-x11 || freesmartphone.org || qtopia || freesmartphone.org
|-
| [[Java]] || Jalimo || Jalimo || Jalimo || ? || ? || {{Yes}} (CacaoVM, JamVM)
|-
| [[Python]] || {{Yes}} || {{Yes}} || {{Yes}} || ? || {{Yes}} || {{Yes}}
|-
| [[Mono]] || {{Yes}} (1) || ? || {{Yes}} (1) || ? || ? || {{Yes}} (1)
|}

Footnotes:

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

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

(3) there is a UI but it crashes the device when used.

(*) unstable

== External links ==

Original distribution descriptions are from Mickey Lauer's [http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO, TMTLA!].

[[Category:Distributions| ]]

Supported microSD cards

2008-09-14T15:06:58Z

Ott--: /* Cards by Vendor */

There are a plethora of Transflash / microSD / SDHC (Secure Digital High Capacity) cards out there.

The Neo FreeRunner supports up to 8GB SDHC cards.

Some microSD cards appear to be too slow to work with the current default settings of the glamo driver, so some specific parameters must be set in uboot to use them (see https://docs.openmoko.org/trac/ticket/1743, and corresponding notes in the tables bellow).

There had been a [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677 bug] in the SD device driver (s3cmci) which caused some trouble. Please make sure you use a recent kernel which applies our kernel patchset rev2832 or higher.

Booting from SDHC requires a u-boot from 2008-07-23 or later. '''But pay attention''' : there are problems with SDHC cards at suspend time. More details from [[Booting from SD#Booting_from_SDHC_.2F_suspend_problems|Booting from SD]]

Note that most vendors are using an irritating way of labeling the capacity of their cards (They are using the factor 1000 instead of 1024 for KB and MB). Therefore the real capacity of these cards will be about 5% less than the vendor's specification. For example, cards labelled ''6 GB'' will only have 5.7 GB of storage capacity.

If you use a card not listed here, please add to this table.

== Cards by Vendor ==
{| border=1 |
| Vendor || Model || Capacity || Speed || [[u-boot]] 1.1.6 || linux 2.6.17.14-fic5 || [[u-boot]] 1.2.0-moko8 svn1915 || [[u-boot]] 1.3.2-moko12 || linux 2.6.24+git75969 (2008.8 kernel as of Sept. 4, 2008)
|-
| A-Data || microSDHC-8GB || 8GB (SDHC) || class 4 || ? || {{yes}} || ? || ||
|-
| Corsair || CMFSDMICRO-512 || 512MB || || {{no}} || {{yes}} || || ||
|-
| Dane-Elec || DA-SDMC-2048-R || 2GB || ? || ? || ? || ? || ? || {{yes}}
|-
| extreMemory || AE56-1280R || 128MB || || {{no}} || {{yes}} || {{yes}} || ||
|-
| extreMemory || H256MS05 || 256MB || 60x || {{no}} || {{yes}} || {{yes}} || ||
|-
| hama || 55371 || 256MB || || {{no}} || {{yes}} || {{yes}} || ||
|-
| Intuix || IXMSDM128B60X || 128MB || 60x || {{no}} || {{yes}} || {{yes}} || ||
|-
| Kingston || SD-C512 || 512MB || ? || {{no}} || {{yes}} || || ||
|-
| Kingston || SD-C01G || 1GB || ? || {{yes}} || ? || || ||
|-
| Kingston || SD-C02G || 2GB || ? || ? || {{yes}} || || {{yes}} ||
|-
| Kingston || SDC4 (N0043-012.A00LF) || 4GB || ? || ? || FSO MS2 / Linux 2.6.24: I/O Errors while formatting [http://wiki.openmoko.org/wiki/Special:Emailuser/varacanero Contact me here] || || ||
|-
| Patriot || PSF128MCSD-RC || 128MB || ? || {{no}} || ? || || ||
|-
| Patriot || PSF8GMCSDHC4 || 8GB || Class 4 || ? || ? || ? || {{yes}} || {{yes}}
|-
| PNY || P-MICROSD512-BX || 512MB || || {{yes}} || {{yes}} || {{yes}} || ||
|-
| PNY || P-MICROSD2GB-BX (card marked with MM8GR02GUACY) || 2GB || slow ? || ? || ? (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743] but apparently not enough) || ? || ||
|-
| Pretec || || 128MB || ? || ? || {{yes}} || || ||
|-
| SanDisk || SDSDQ-128 || 128MB || || {{yes}} || {{yes}} || {{yes}} || ||
|-
| SanDisk || unknown || 256MB || || {{yes}} || {{yes}} || {{yes}} || ||
|-
| SanDisk || unknown || 512MB || || {{yes}} || {{yes}} || || ||
|-
| SanDisk || SDSDQ-1024-E10M || 1GB || || {{yes}} || {{yes}} || {{yes}} || ||
|-
| SanDisk || SDSDQU-2048-E10M || 2GB || || {{yes}} || {{yes}} || {{yes}} || ||
|-
| SanDisk || SDSDQ-4096-E11M || 4GB (SDHC) || || ? || {{yes}} || ? || ||
|-
| SanDisk || SDSDQ-6144-E11M || 6GB (SDHC) || || ? || {{yes}} || {{no}} || ||
|-
| SanDisk || SDSDQ-8192-E11M || 7GB (SDHC) || 4 || ? || {{yes}} || ? || ||
|-
| SanDisk || SDSDQY-8192-A11M || 8GB (SDHC) || || ? || {{yes}} || ? || ||
|-
| SanDisk || SDSDQR-8192-E12M || 8GB (SDHC) || 4 || ? || {{yes}} || ? || ||
|-
| SanDisk || SDSDQR-8192-???? || 8GB (SDHC) || 6 || ? || {{yes}} || {{yes}} || ||
|-
| SanDisk || SDSDQ-008G-E11M || 8GB (SDHC) || 4 || ? || {{yes}} || || ||
|-
| Toshiba || SD-512R2W || 512MB || || {{no}} || {{yes}} || || ||
|-
| Transcend || TS128MUSD || 128MB || || {{no}} || {{yes}} || || ||
|-
| Transcend || TS256MUSD80 || 256MB || 80x || {{no}} || {{yes}} || {{yes}} || ||
|-
| Transcend || TS512MUSD || 512MB || || {{no}} || {{yes}} || {{yes}} || ||
|-
| Transcend || MM4GRO1GUACY || 1GB || || ? || {{yes}} || ? || ||
|-
| Transcend || TS1GUSDC || 1GB (SDC) || || ? || I/O errors while trying to install Om2008.8 rootfs.tar.gz, looks like [https://docs.openmoko.org/trac/ticket/1743 #1743] || ? || ? || ?
|-
| Transcend || TS4GUSDHC6 (card marked with MM8GR04GUACY) || 4GB (SDHC) || Class 6 || ? || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ? || ||
|-
| Transcend || TS8GUSDHC4 || 8GB (SDHC) || Class 4 || ? || ? || ? || {{yes}} || linux 2.6.24+git37+d744c88c14 (2007.2 kernel as of Aug 28, 2008)
|-
| Verbatim || 47225 || 1GB || || {{no}} || {{yes}} || {{yes}} || ||
|-
| vox-fon || 1 GB || 1GB || || {{no}} || {{yes}} || || ||
|-
| (Intenso) || ? || 4GB (SDHC) || || {{no}} || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ? || {{yes}} || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743])
|}

Note that cards with a "'''no'''" may still work at times, but that we just have found their behaviour too erratic to consider acceptable.
(Also note that this is a bug in our version of u-boot. The cards are probably fine.)

[[Category:Neo1973 Hardware]]

Supported microSD cards

2008-09-11T12:03:20Z

Ott--: /* Cards by Vendor */

There are a plethora of Transflash / microSD / SDHC (Secure Digital High Capacity) cards out there.

The Neo FreeRunner supports up to 8GB SDHC cards.

Some microSD cards appear to be too slow to work with the current default settings of the glamo driver, so some specific parameters must be set in uboot to use them (see https://docs.openmoko.org/trac/ticket/1743, and corresponding notes in the tables bellow).

There had been a [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677 bug] in the SD device driver (s3cmci) which caused some trouble. Please make sure you use a recent kernel which applies our kernel patchset rev2832 or higher.

Booting from SDHC requires a u-boot from 2008-07-23 or later. '''But pay attention''' : there are problems with SDHC cards at suspend time. More details from [[Booting from SD#Booting_from_SDHC_.2F_suspend_problems|Booting from SD]]

Note that most vendors are using an irritating way of labeling the capacity of their cards (They are using the factor 1000 instead of 1024 for KB and MB). Therefore the real capacity of these cards will be about 5% less than the vendor's specification. For example, cards labelled ''6 GB'' will only have 5.7 GB of storage capacity.

If you use a card not listed here, please add to this table.

== Cards by Vendor ==
{| border=1 |
| Vendor || Model || Capacity || Speed || [[u-boot]] 1.1.6 || linux 2.6.17.14-fic5 || [[u-boot]] 1.2.0-moko8 svn1915 || [[u-boot]] 1.3.2-moko12 || linux 2.6.24+git75969 (2008.8 kernel as of Sept. 4, 2008)
|-
| A-Data || microSDHC-8GB || 8GB (SDHC) || class 4 || ? || {{yes}} || ? || ||
|-
| Corsair || CMFSDMICRO-512 || 512MB || || {{no}} || {{yes}} || || ||
|-
| Dane-Elec || DA-SDMC-2048-R || 2GB || ? || ? || ? || ? || ? || {{yes}}
|-
| extreMemory || AE56-1280R || 128MB || || {{no}} || {{yes}} || {{yes}} || ||
|-
| extreMemory || H256MS05 || 256MB || 60x || {{no}} || {{yes}} || {{yes}} || ||
|-
| hama || 55371 || 256MB || || {{no}} || {{yes}} || {{yes}} || ||
|-
| Intuix || IXMSDM128B60X || 128MB || 60x || {{no}} || {{yes}} || {{yes}} || ||
|-
| Kingston || SD-C512 || 512MB || ? || {{no}} || {{yes}} || || ||
|-
| Kingston || SD-C01G || 1GB || ? || {{yes}} || ? || || ||
|-
| Kingston || SD-C02G || 2GB || ? || ? || {{yes}} || || {{yes}} ||
|-
| Kingston || SDC4 (N0043-012.A00LF) || 4GB || ? || ? || FSO MS2 / Linux 2.6.24: I/O Errors while formatting [http://wiki.openmoko.org/wiki/Special:Emailuser/varacanero Contact me here] || || ||
|-
| Patriot || PSF128MCSD-RC || 128MB || ? || {{no}} || ? || || ||
|-
| Patriot || PSF8GMCSDHC4 || 8GB || Class 4 || ? || ? || ? || {{yes}} || {{yes}}
|-
| PNY || P-MICROSD512-BX || 512MB || || {{yes}} || {{yes}} || {{yes}} || ||
|-
| PNY || P-MICROSD2GB-BX (card marked with MM8GR02GUACY) || 2GB || slow ? || ? || ? (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743] but apparently not enough) || ? || ||
|-
| Pretec || || 128MB || ? || ? || {{yes}} || || ||
|-
| SanDisk || SDSDQ-128 || 128MB || || {{yes}} || {{yes}} || {{yes}} || ||
|-
| SanDisk || unknown || 256MB || || {{yes}} || {{yes}} || {{yes}} || ||
|-
| SanDisk || unknown || 512MB || || {{yes}} || {{yes}} || || ||
|-
| SanDisk || SDSDQ-1024-E10M || 1GB || || {{yes}} || {{yes}} || {{yes}} || ||
|-
| SanDisk || SDSDQU-2048-E10M || 2GB || || {{yes}} || {{yes}} || {{yes}} || ||
|-
| SanDisk || SDSDQ-4096-E11M || 4GB (SDHC) || || ? || {{yes}} || ? || ||
|-
| SanDisk || SDSDQ-6144-E11M || 6GB (SDHC) || || ? || {{yes}} || {{no}} || ||
|-
| SanDisk || SDSDQ-8192-E11M || 7GB (SDHC) || 4 || ? || {{yes}} || ? || ||
|-
| SanDisk || SDSDQY-8192-A11M || 8GB (SDHC) || || ? || {{yes}} || ? || ||
|-
| SanDisk || SDSDQR-8192-E12M || 8GB (SDHC) || 4 || ? || {{yes}} || ? || ||
|-
| SanDisk || SDSDQR-8192-???? || 8GB (SDHC) || 6 || ? || {{yes}} || {{yes}} || ||
|-
| SanDisk || SDSDQ-008G-E11M || 8GB (SDHC) || 4 || ? || {{yes}} || || ||
|-
| Toshiba || SD-512R2W || 512MB || || {{no}} || {{yes}} || || ||
|-
| Transcend || TS128MUSD || 128MB || || {{no}} || {{yes}} || || ||
|-
| Transcend || TS256MUSD80 || 256MB || 80x || {{no}} || {{yes}} || {{yes}} || ||
|-
| Transcend || TS512MUSD || 512MB || || {{no}} || {{yes}} || {{yes}} || ||
|-
| Transcend || MM4GRO1GUACY || 1GB || || ? || {{yes}} || ? || ||
|-
| Transcend || TS4GUSDHC6 (card marked with MM8GR04GUACY) || 4GB (SDHC) || Class 6 || ? || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ? || ||
|-
| Transcend || TS8GUSDHC4 || 8GB (SDHC) || Class 4 || ? || ? || ? || {{yes}} || linux 2.6.24+git37+d744c88c14 (2007.2 kernel as of Aug 28, 2008)
|-
| Verbatim || 47225 || 1GB || || {{no}} || {{yes}} || {{yes}} || ||
|-
| vox-fon || 1 GB || 1GB || || {{no}} || {{yes}} || || ||
|-
| (Intenso) || ? || 4GB (SDHC) || || {{no}} || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ? || {{yes}} || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743])
|}

Note that cards with a "'''no'''" may still work at times, but that we just have found their behaviour too erratic to consider acceptable.
(Also note that this is a bug in our version of u-boot. The cards are probably fine.)

[[Category:Neo1973 Hardware]]
[[Category:Documentation]]

Booting the Neo FreeRunner from SD via U-Boot

2008-09-10T21:29:10Z

Ott--: typo (bellow => below)

{{Languages}}
This page explains how to boot a FreeRunner from the [[Supported_microSD_cards|(micro-)SD card]] rather than from the built-in NAND flash memory. The SD card shares a bus with the GPU, so it may not perform as well, but it is another option.

{{Warning | Booting from SDHC may cause problems at this time (see below).}}

== Booting from SDHC / suspend problems ==

First, a warning. There is a longstanding bug, probably somewhere in the Linux kernel, that tends to eat the partition table of high-capacity SD cards when the system suspends. This is ticket [https://docs.openmoko.org/trac/ticket/1802 #1802]. See [http://thread.gmane.org/gmane.comp.handhelds.openmoko.community/19154/focus=19281| this thread] for explanation of the partition table removal on suspend and maybe other problems related to using high capacity SD cards. A safety net is to keep a written copy of the partition table on paper, just in case one needs to recreate it.

== How it Works ==

On the Neo, [[u-boot]] performs a similar role to the 'grub' bootloader on a PC. U-boot loads a kernel image into memory and then passes a list of parameters to the kernel. These parameters specify, among other things, the device on which the root filesystem is located.

As the kernel boots, it initializes the hardware and then mounts the root filesystem. The kernel then runs "/sbin/init", which handles the rest of the boot-up sequence (such as displaying the splash screen and progress bar).

This sequence is the same whether the device is booting from built-in Flash or from the SD card. The differences are how the kernel is loaded, and which device is mounted as the root filesystem.

The following sections provide additional details.

=== Menu Entries ===

U-boot menu entries are defined by environment variables named "menu_X" (where X is a number). The value of the environment variable is a string "<label>:<commands>", where <label> is the text shown on the screen, and <commands> is a sequence of u-boot commands (delimited by ';' characters) to be executed when the menu item is selected. When entering a string of commands, the ';' and '$' characters must be backslash-escaped ("\;" and "\$").

=== Loading the Kernel ===

A pair of u-boot commands must be used to load the kernel from SD. First is "mmcinit", which will cause u-boot to detect the card. Next is a command to load a file into memory - either "fatload" or "ext2load" depending on whether the kernel is on a FAT filesytem or an ext2/ext3 filesystem.

The command syntax is:

fatload mmc 1: 0x32000000 <filepath>
ext2load mmc 1: 0x32000000 <filepath>

where is the partition number, and <filepath> is the path to the file that is to be loaded.

{{Note| The "ext2load" command is broken on u-boot binary earlier than "20080723", including the one shipped with the first batch of FreeRunners, are affected by bug [http://docs.openmoko.org/trac/ticket/799 #799]. If you update your U-Boot and kernel packages you can use direct ext2 / 3 boot all in one partition.}}

{{Warning | Be careful when updating u-boot on a Neo1973 as there is a risk of bricking the device (unless you have a debug board). This is not an issue for the FreeRunner as it has a protected copy of u-boot in the NOR flash }}

{{Note| U-Boot supports SDHC protocol on the FreeRunner only: on the Neo1973, u-boot is unable to access SDHC cards (4G or larger). The kernel does have SDHC support on Neo1973, so it is possible to have the root filesystem on SDHC and the kernel on NAND flash to work around it. }}

=== Root Filesystem Parameters ===

The contents of the "bootargs" environment variable are passed to the kernel. Bootargs is a space-delimited list of "name=value" definitions. The items relevant to SD-booting are "root", "rootfstype", and "rootdelay".

For example, the following parameters would tell the kernel to mount the third partition of the SD-card as an ext3 filesystem:

root=/dev/mmcblk0p3 rootfstype=ext3 rootdelay=5

The "rootdelay" parameter allows time for the card to be properly initialized before it is accessed.

Note that the kernel must have built-in support (i.e. not a module) for the filesystem specified in "rootfstype". The default Openmoko kernel configs as of [http://git.openmoko.org/?p=kernel.git;a=commit;h=642cbda5f3b7e7a61512426e1d30a41ab4691123| 2008-07-17] have built-in support for both ext2 and ext3. You can check the available filesystems with the Linux command

less /proc/filesystems

It is not possible to use VFAT for the root filesystem.

==== ext2 vs. ext3 ====

Opinion is divided on whether it is better to use ext2 or ext3 for the root filesystem. Ext3 in general is a superior choice, because it is a journalled filesystem and so does not require a long 'fsck' (file system check) after an unclean shutdown. However, if used on a flash device that does not support wear-leveling then ext3 may cause premature wear on the blocks of the card where the journal is stored. SD cards are supposed to support wear leveling, but this can not be guaranteed for all vendors.

== Acquiring a tarfile rootfs ==

There are two ways of acquiring an rootfs image as a tar archive. You can either build it on your own using the OpenEmbedded Distribution. Or download it from the openmoko buildhost.

=== Possibility 1: Downloading the rootfs/kernel tar from the Openmoko buildhost ===

Choose and find the rootfs/kernel combo you would like to install at [[Latest Images]].

=== Possibility 2: Building a tarfile distribution using OpenEmbedded ===

Another possibility to get a tar archive of your rootfs is to build it on your own with the OpenEmbedded environment.

To build OM-2007.2 you need to add "tar" to the image types in your ''local.conf'':

IMAGE_FSTYPES = "jffs2 tar"

After that build a new image by issuing:

bitbake openmoko-devel-image

or if you are using the MokoMakefile:

make openmoko-devel-image

After the process finished there will be a ''Openmoko-....tar'' in the deploy directory, which is your newly created rootfs archive

=== Possibility 3 : Convert a jff2 image to a tarfile ===

See [[Userspace root image]] for more details on how to access contents of a jffs2 image.

== Prepare the SD card ==

=== Partioning the SD card ===

u-boot pre-2008-07-23 can only boot from FAT filesystems; if you update u-boot, you can boot from FAT or ext2.
This example shows how to do an example partition using the fdisk utility. Feel free to use the partitioning utility of your liking for this task.

fdisk /dev/mmcblk0

'''''Note:''''' The device file might differ on your system. If you are not sure about it, you may check your kernel message log by calling ''dmesg'' to find the correct device.

We will now create a 8 mb partition for our kernel and another one for the rootfs which will take up all the remaining space.

Command (m for help): d
Selected partition 1
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-983, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-983, default 983): +8M
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (18-983, default 18):
Using default value 18
Last cylinder or +size or +sizeM or +sizeK (18-983, default 983):
Using default value 983
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.

''Should probably need to change type of first partition to FAT 16 too ?''

if it exits with something like

Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy

do

umount /dev/mmcblk0p1

on another shell and try again.

=== Formatting the SD card ===

Just issue the following command to create at FAT filesystem:

mkfs.vfat /dev/mmcblk0p1
{{Note|if you do not have mkfs.vfat you must find and install the "dosfstools" package. This package does not seem to be in the official feeds, but an unofficial build may be downloaded from http://members.shaw.ca/mmontour/neo/dosfstools_2.11-r0_armv4t.ipk}}

The second partition is about to be formatted with ext3 (for ext2 to work you need to make sure you compiled the kernel with the correct configuration):

mkfs.ext3 /dev/mmcblk0p2

== Populate SD card ==

Your sd card is now ready to be filled up with the rootfs and the needed kernel to boot.

Mount the second partition of your SD card somewhere and put the image on it:

mount /dev/mmcblk0p2 /mnt/moko
tar -C /mnt/moko/ -xzvf openmoko-devel-image-fic-gta01-20070313022035.rootfs.tar.gz

'''''Note:''''' As always in this guide the device name as well as the rootfs name needs to be adjusted to your device and filename structure

'''''Note:''''' There's a nice gotcha to take care about if you use your host OS automount. Some hosts mount these removable devices with "nodev" option by default for security. If the image you are unpacking has a populated /dev directory, the nodes will fail to create as devices then. If automounting the SD on your host, confirm there are no unexpected mount options by using "mount" command alone to list the mounts.

The next step is to mount the first partition of the sd card and install the kernel on it.

mount /dev/mmcblk0p1 /mnt/mokokernel
cp uImage-fic-gta01-latest.bin /mnt/mokokernel/uImage.bin

Make sure your kernel is called ''uImage.bin''. If the u-boot doesn't find the kernel image during boot, [[Bootloader#Using usbtty from Linux|log into the bootloader]] with ''[http://www.airs.com/ian/uucp.html cu]'', mount the partition with mmcinit and check the presence and the name of the kernel image with ''fatls mmc 1:1'' for FAT filesystem or ''ext2ls mmc 1:1'' for ext2 filesystem.

Unmount both the rootfs partition and the kernel partition and make sure all remaining buffers are written to it:

umount /mnt/moko
umount /mnt/mokokernel
sync

== Add uboot boot entry ==
Depending on the revision of the phone and the partition type (ext2/ext3) you are using, it might be necessary to add an entry to the bootmenu to be able to boot the system off your SD card.
If you are using a FreeRunner and have created an FAT kernel/ext2 rootfs partition you should be able to boot from the card right out of the box, because a boot menu entry for this should already exist in the NOR/NAND boot menu.
In any other case you should at least make sure the needed entry exists in your menu before proceeding.
You will need to enter the uboot shell of the NAND boot menu for this. A description on how to connect to the uboot loader shell can be found in this article: [[Uboot#Bootloader_prompt]]. Details on howto get into the NAND boot menu can be found [[Booting#Log_into_U-Boot_in_the_NAND_Flash|here]].

After you read these two references you should be connected to your NAND uboot shell right now. The first thing to do is to set the boot menu timeout to a really high value. Unfortunately if you don't do this, the boot loader will continue booting after the default timeout (60 seconds) even if you are connected to the uboot shell. Just enter the following command to the menu prompt:

setenv boot_menu_timeout 99999

This will set the timeout to 99999 seconds which should definitely enough time for us finish whatever work we want accomplish in the boot loader shell.

Now we will make sure a appropriate menu item for booting from sd exists, or create it otherwise. You can print the defined boot loader environment by issuing the command:

printenv

If it shows a line beginning with ''menu_'' followed by the commands which are just to follow in this guide, you do not need to create a new menu entry. In any other case please proceed with the following.

Please make sure you are using the correct configuration based on the decisions you made earlier. For more information on the uboot prompt, see
help
help <command>
and [[Bootloader]] and [[Bootloader commands]].

{{Note| The backslashes (\) are important for uboot to set the command as new environment variable (menu_9) instead of just executing them as soon as enter is pressed.}}

{{Note| Copy and paste may not work depending on your terminal emulator. Commi just works or you can use [[NeoCon|neocon]] terminal emulator and add a per-character delay. Otherwise, you will have to type in the commandline manually.}}

It is important to distinguish between FAT or ext2 kernel partitions and ext2 or ext3 root partitions at this point.

Please watch partition numbers in the following commands. In particular, you may need to change root=/dev/mmcblk0p'''#''' and fatload mmc '''#''' or ext2load mmc '''#''' depending on which partition number your root and kernel, respectively, are located. Number starts from unity.

'''Boot entry for FAT kernel+ext3 rootfs partitions:'''

setenv menu_9 Boot from microSD (FAT+ext3): setenv bootargs \${bootargs_base} rootfstype=ext3 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\; mmcinit\; fatload mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000

'''Boot entry for FAT kernel+ext2 rootfs partitions:'''

setenv menu_9 Boot from microSD (FAT+ext2): setenv bootargs \${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\; mmcinit\; fatload mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000

or : with additional 'init=/sbin/init' kernel parameter (may be needed for some images) :
setenv menu_9 Boot 200808 from microSD (FAT+ext2): setenv bootargs \${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} init=/sbin/init ro\; mmcinit\; fatload mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000

'''Boot entry for ext2 kernel+ext2 rootfs partitions: (requires newer u-boot)'''

setenv menu_2 Boot from microSD part2 (ext2+ext2): setenv bootargs \${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\; mmcinit\; ext2load mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000

'''Boot entry for kernel and rootfs on same ext2 partition (tested with Qtopia/requires newer u-boot)'''
setenv menu_3 QTopia: setenv bootargs \${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p1 rootdelay=5 \${mtdparts} ro\; mmcinit\; ext2load mmc 1:1 0x32000000 \${sd_image_name}\; bootm 0x32000000
You are nearly done. Just issue a

printenv

and verify that your newly created entry is correctly displayed (This time the backslashes are not displayed anyone).

If everything looks fine enter

saveenv

into the prompt and press enter. The new configuration should now be saved to the NAND.

Shutdown your neo with the following command:

neo1973 power-off

After you restarted the Neo and got back to the NAND boot menu you should be able to select your newly created menu entry and successfully boot into the rootfs from your SD card.

----

See also [[Moving current system from flash to SD]] which shows how to move the running system currently running in flash to an SD card, in order to keep a backup system on SD on which to boot from.

----

== Appendix ==

=== Boot from SDHC ===

{{Note|the following text was written for the Neo1973. SDHC and SD should both work in a FreeRunner if you have u-boot from 2008-07-23 or later.}}

As SDHC is not supported in older u-boot versions you can't use the Booting from SD guide.
But there's a kind of workaround that is a good option to have at least your rootfs on the microSDHC:

First you can follow Step 1 to get an kernel-image with mmc- and ext2-support. But instead of copying the image to the rootfs you will have to flash it to the Neo's internal NAND-Flash (using [[Dfu-util]]).
Now you can continue with Step 2 (like mentioned before you do not have to copy your uImage to the rootfs) and follow the instructions to Step 3.
Instead of the setenv commands in Step 3 you have to enter the following:

GTA01Bv4 # setenv menu_5 Boot from SDHC: setenv bootargs root=/dev/mmcblk0p1 console=tty0 rootdelay=5 neo1973-nand:0x00040000(u-boot),0x00004000(u-boot_env),0x00200000(kernel),0x000a0000(splash)\; nand read.e 0x32000000 kernel\; bootm 0x32000000
GTA01Bv4 # saveenv

And that's it!
Now you can use the newly created menu option "Boot from SDHC" to boot the internal kernel, using the root-filesystem on the microSDHC.

=== Autoboot from SDHC ===

Maybe you want to Boot automatically from SDHC:
Set a new Bootmenu Entry for booting from NAND first

GTA01Bv4 # setenv menu_6 Boot from NAND: setenv bootargs \${bootargs_base} \${mtdparts}\; nand read.e 0x32000000 kernel\; bootm 0x32000000
GTA01Bv4 # saveenv

then Power-off, and enter the Bootmenu to test the new Entry.If you can boot from NAND, shutdown, enter Boot menu, connect to bootloader and set the (auto)bootcmd for boot from SDHC:

GTA01Bv4 # setenv bootcmd setenv bootargs root=/dev/mmcblk0p1 rootdelay=10 console=tty0 neo1973-nand:0x00040000(u-boot),0x00004000(u-boot_env),0x00200000(kernel),0x000a0000(splash)\; nand read.e 0x32000000 kernel\; bootm 0x32000000
GTA01Bv4 # saveenv

Now you boot from SDHC everytime you press the Power-Button or reboot and if you like to boot from NAND -just use the bootmenu.

=== Fixing udev automount ===

Udev automatically mounts the SD Card in /media/mmcblk0p1/ you can disable this with

echo /dev/mmcblk >> /etc/udev/mount.blacklist

=== Remarks on Kernel Parameters ===

==== loglevel ====

Some people suggested adding:

loglevel=8

to the kernel command line. IF you also have "console=tty0" on your kernel commandline this makes the boot process extremely slow because the framebuffer (the neo display in text mode) has to print out tons of lines of debug messages like:

s3c2410-sdi s3c2410-sdi: ......
mmc0: ....

{{Languages|Booting_from_SD}}

[[Category:Guides]]
[[Category:Flashing Openmoko]]
[[Category:Documentation]]
[[Category:System Developers]]

Neo FreeRunner Hardware Issues

2008-09-09T22:41:48Z

Ott--: /* Can't boot with discharged or missing battery */

{{Neo FreeRunner Menu}}

This is a community-written page that discusses '''hardware issues''' with the FreeRunner/[[GTA02]] device. Information here is unofficial (and possibly incorrect) unless otherwise stated. Corrections and clarifications from Openmoko employees would be greatly appreciated.

Please '''DON'T PANIC''' when reading this page. Please give Openmoko employees time to investigate these issues and to develop a solution. Some of the items may turn out to be non-issues, or may have software workarounds. The FreeRunner's software is still under heavily development and can help fix most of this problems.

=== Active Issues ===

==== Poor Audio Quality ====

Issue: The person on the other end of a GSM phone call may experience poor audio quality, to the point where he/she cannot carry on a normal conversation.

There are three related aspects to this issue:
* Call is too quiet (mixer settings for mic and/or earpiece are set too low)
* Caller hears a loud echo of their own voice [http://docs.openmoko.org/trac/ticket/1267 #1267]
* Buzzing noise caused by GSM radio interference [http://docs.openmoko.org/trac/ticket/883 #883] [http://docs.openmoko.org/trac/ticket/1352 #1352]

Affects: all devices but only some users (depending on many factors)

Status: Under investigation. There is a possibility that the quality can be made "good enough" through software (mixer settings).

The source of the GSM buzz has been [http://lists.openmoko.org/pipermail/hardware/2008-August/000415.html identified].

Some [http://lists.openmoko.org/pipermail/hardware/2008-August/000451.html hidden Calypso commands] may help with the echo problem.

Workarounds:

# Using a bluetooth headset is a possibility.

# Better mixer settings: One confirmed good settings are here: http://www.mail-archive.com/support@lists.openmoko.org/msg00564.html. Please change accordingly in /usr/share/openmoko/scenarios/gsmhandset.state. Should eliminate/lessen echo and buzz problems.

==== Can't boot with discharged or missing battery ====

Issue: Neo FreeRunner requires battery power to boot, because Neo FreeRunner consumes too much current while booting to boot with only a charger. Since charging isn't enabled until the Neo FreeRunner has booted, this means that a discharged battery can not be charged. One manifestation of this problem is a kernel panic (red LED flashes constantly) when trying to boot using the power button.

Affects: Unknown.

Status: By properly sequencing module power sequence, a software solution to this problem should exist.

Fixed(?) with [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/003799.html Werner Almesberger patches] - [http://lists.openmoko.org/pipermail/commitlog/2008-July/005403.html more here] [http://lists.openmoko.org/pipermail/community/2008-July/023392.html additional information]

Workarounds:

# Make sure that the battery never discharges completely
# Use external stand-alone charger (compatible with the Nokia BL-5C battery)
# Boot the FreeRunner with an [[Neo_FreeRunner_Battery#Compatible_Replacement_Batteries|alternative battery]], or with a spare GTA01 or GTA02 battery, plug USB power, then switch to the empty battery.
# Boot the FreeRunner with a 4.5VDC external power source (steady hand and great care involved), plug USB power, then insert the empty battery.
# Some users have reported that Neo FreeRunner '''is''' able to boot on USB power alone using the NOR u-boot, thus: press AUX, plug USB power, select boot. Reports of success would be appreciated.

See also:
:[[Neo_FreeRunner_Battery|Neo FreeRunner Battery]]

==== Battery discharges when charging completes ====

Issue: If the Neo FreeRunner has been charging, when charging completes, it seems to drain the battery and not turn on charging again. This seems to be bug of PMU-registers setup, that shows up when PMU has to handle bat autonomously (=suspend). There might be issues our current scheme relies on wake-interrupt at bat-full which doesn't succeed, or something like that.

Affects: Unknown.

Status:

Workarounds:

# When the battery is full, disconnect the charger

See also:

==== Suspend/resume corrupts SD card's partition table ====

Issue: Suspend/resume corrupts the partition table of the SD card

Affects: Unknown.

Status:

[[https://docs.openmoko.org/trac/ticket/1802#comment:6 Patched kernel]] might solve the problem

Workarounds:

# [[https://docs.openmoko.org/trac/ticket/1802#comment:5 Script]] as a temporary workaround

See also:

:[[https://docs.openmoko.org/trac/ticket/1802 trac ticket]]

==== Some SIMs Don't Work ====

Issue: There are reports that some users cannot register with their GSM network when using certain SIM cards. See for example http://lists.openmoko.org/pipermail/community/2008-July/020370.html

It is possible that there is more than one issue involved here. The observed problems ''might'' (i.e. some items are only speculation at this point) be caused by:

* User error, not inserting the SIM in the correct orientation or not sliding the holder to the 'locked' position

* Software issues that result in a locked SIM (not properly prompting the user for a PIN and then passing this to the SIM)

* Mechanical issues with the SIM holder that prevent the pins from making reliable contact with the pads on the SIM. Note that only 6 of the 8 pins are used, and the remaining two are not connected.

* Electrical incompatibility (some tests show problems with 1.8V SIMs while 2.9V ones work OK)

* Firmware bugs in the TI Calypso GSM chipset. Note that one issue in this category was found and fixed on the GTA01 devices (#666 in Trac), and that specific problem should not affect the FreeRunner.

* Defective SIMs, i.e. ones that do not comply with the applicable standards and are acknowledged as being defective by the carrier (even if they happen to work in some phones).

* You may have true 3G operating at 2100 and your sim doesn't fallback to GSM. The Phone works on 850/1800/1900 or 900/1800/1900.

See also:
* http://wiki.openmoko.org/wiki/Carriers/ATT
* http://wiki.openmoko.org/wiki/Carriers/Rogers

Affects: Only a subset of users (details unknown).

Status: Under investigation. Please add your information to [[FreeRunner_unable_to_work_with_3G_SIM_cards]] or [[GSM network registration]]

Workarounds:

# Please document your existing SIM card and provider in the table [[FreeRunner_unable_to_work_with_3G_SIM_cards|here]]
# If the table mentioned above shows any SIM cards known to work with your provider, make note of these numbers
# Contact your network provider and request a new SIM card. You may wish to print out the table mentioned above and bring it with you to the store.
# Add your experience with the new SIM card to the table mentioned above

=== Known/Accepted Issues ===

This section lists items that are acknowledged as being less than ideal, but are considered to be acceptable in the shipping product. They will not be discussed in detail on this page.

* Poor performance + slow bus speed of the Glamo GPU - discussed to death on the mailing lists and IRC.
* [http://lists.openmoko.org/pipermail/hardware/2008-April/000055.html GPS antenna switch] driven out-of-spec - does not appear to have a significant effect on device performance
* Poor low-frequency audio response with low-impedance headphones, e.g. as discussed in this thread: http://lists.openmoko.org/pipermail/openmoko-kernel/2008-March/001999.html (NOTE - this thread refers to pre-mass-production devices)
** Can be fixed to an semi-acceptable level (if not high fidelity most probably) by adjusting "Bass Volume" to full (15) and "Bass Filter" to "100Hz @ 8kHz" (bass will be boosted <= 600Hz when playing back at 48kHz) or "200Hz @ 8kHz" (<= 1200Hz @ 48kHz). The default is 130Hz @ 48kHz and does not help much with the more wider scope of low frequencies.
** Ideally someone would record output and find out which setting produces best output, ie. compensating for the loss of low frequencies without boosting too high frequencies with this "bass" boost.

=== Resolved Issues ===

These are issues that have been discussed in the past, but have been fixed (or turned out not to be a problem) for the mass-produced devices.

* Excessive LED current - Some early units lacked a current-limiting resistor for the LEDs. This has been fixed for the production units.
* Battery life - At this time it appears that the FreeRunner battery life will be acceptable once suspend/resume support has been implemented in software.
* slow GPS TTFF - see [[GPS Problems]]
==== Empty NOR Flash ====

Issue: NOR flash (backup copy of u-boot) is not programmed. [http://docs.openmoko.org/trac/ticket/1568 #1568]

Affects: Unknown - maybe only 1 or 2 devices? Also need to confirm that the bug report was from a mass-production unit rather than an earlier prototype.

Status: Solved. The new devices are tested better if they have the NOR flashed programmed and aren't shipped if the test fail.

Workarounds: Use the NAND copy of u-boot and be careful not to brick the device unless a debug-board is available.

==== Debug board has wrong vendor/product ID ====

Issue: A debug board is not reporting the expected USB Vendor/Product ID.

Affects: Only [http://lists.openmoko.org/pipermail/device-owners/2008-July/001775.html one report] has been seen so far.

Status: Probably a single case scenario.

Workarounds: Edit configuration files (e.g. openocd.conf) to use the IDs that the board is reporting.

== List of "Current issues" Imported from the "Community update page" ==
(to be sorted)

The information below has been collected from various sources, feel free to add questions and comments here.

===GPS Performance of the FreeRunner===
The poor GPS performance on the FreeRunner has been traced to an
interaction between the microSD card and the GPS unit. A software
and a hardware fixes are available, see [[GPS Problems]].

===GTA02 battery status===
While writing a device driver for the new battery which provides an accurate counter of the charge state of the [[GTA02]], the driver developer discovered that the device driver does not get a reading of the charge state due to a very long response time with only one I/O signal when trying to read the charge state. To be able to read the battery status properly, it has been written that it will be necessary to re-design that part of the GTA02 for hardware version GTA02A5 to use two I/O signals to reduce the response time (one for transmitting commands, one for receiving data?). This was fixed two months ago (see [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=957#c1 Bug 957]).

===Delivery of a GSM firmware update for the 3G SIM bug ([http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=666 #666])===

A bug in the GSM firwmare of Neo 1973 caused some 3G SIM cards to not work with Neo 1973. This Neo 1973 GSM firmware update can only be installed by an Openmoko employee due to licensing issues.

This fix is already present in the Neo FreeRunner firwmare, and thus the Neo 1973 GSM firmware update is not required for the Neo FreeRunner. In fact since the firmware differs between the Neo 1973 and the Neo FreeRunner, it would very likely make the GSM module unusable.

There seem to be other GSM issues on the Neo FreeRunner. See [[#Some_SIMs_Don.27t_Work|Some SIMs Don't Work]] above.

=== SMedia 3362 Documentation & OpenGL ES Drivers ===
There is an open source kdrive driver being written for the GTA02 which will use hardware to accelerate the XRender extension. While the chip is capable of 3D graphics, no OpenGL ES driver/library is avaliable and Openmoko developers will not be writing one in the near future (although they have not ruled it out in the long-term).

Documentation for the SMedia 3362 has been promised ([http://lists.openmoko.org/pipermail/community/2007-September/010175.html see this post]). However, this refers to documentation Openmoko developers will be writing themselves, not the technical documentation SMedia have provided Openmoko with. The Openmoko developers had to sign an NDA with SMedia to obtain this documentation and are therefore unable to pass this information on to community developers. (See [http://lists.openmoko.org/pipermail/community/2007-November/011349.html this post] for details)

=== Power Management on the Neo1973/FreeRunner===
The current battery life of the Neo1973 and FreeRunner is not satisfactory. A lot of changes seem to be necessary to the kernel, drivers and related user-space applications. Hopefully the situation will improve over time.

[[Category:Neo FreeRunner Hardware]]

Supported microSD cards

2008-09-09T21:30:16Z

Ott--: /* Cards by Vendor */

There are a plethora of Transflash / microSD / SDHC (Secure Digital High Capacity) cards out there.

The Neo FreeRunner supports up to 8GB SDHC cards.

Some microSD cards appear to be too slow to work with the current default settings of the glamo driver, so some specific parameters must be set in uboot to use them (see https://docs.openmoko.org/trac/ticket/1743, and corresponding notes in the tables bellow).

There had been a [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677 bug] in the SD device driver (s3cmci) which caused some trouble. Please make sure you use a recent kernel which applies our kernel patchset rev2832 or higher.

Booting from SDHC requires a u-boot from 2008-07-23 or later. '''But pay attention''' : there are problems with SDHC cards at suspend time. More details from [[Booting from SD#Booting_from_SDHC_.2F_suspend_problems|Booting from SD]]

Note that most vendors are using an irritating way of labeling the capacity of their cards (They are using the factor 1000 instead of 1024 for KB and MB). Therefore the real capacity of these cards will be about 5% less than the vendor's specification. For example, cards labelled ''6 GB'' will only have 5.7 GB of storage capacity.

If you use a card not listed here, please add to this table.

== Cards by Vendor ==
{| border=1 |
| Vendor || Model || Capacity || Speed || [[u-boot]] 1.1.6 || linux 2.6.17.14-fic5 || [[u-boot]] 1.2.0-moko8 svn1915 || [[u-boot]] 1.3.2-moko12 || linux 2.6.24+git75969 (2008.8 kernel as of Sept. 4, 2008)
|-
| A-Data || microSDHC-8GB || 8GB (SDHC) || class 4 || ? || {{yes}} || ? || ||
|-
| Corsair || CMFSDMICRO-512 || 512MB || || {{no}} || {{yes}} || || ||
|-
| Dane-Elec || DA-SDMC-2048-R || 2GB || ? || ? || ? || ? || ? || {{yes}}
|-
| extreMemory || AE56-1280R || 128MB || || {{no}} || {{yes}} || {{yes}} || ||
|-
| extreMemory || H256MS05 || 256MB || 60x || {{no}} || {{yes}} || {{yes}} || ||
|-
| hama || 55371 || 256MB || || {{no}} || {{yes}} || {{yes}} || ||
|-
| Intuix || IXMSDM128B60X || 128MB || 60x || {{no}} || {{yes}} || {{yes}} || ||
|-
| Kingston || SD-C512 || 512MB || ? || {{no}} || {{yes}} || || ||
|-
| Kingston || SD-C01G || 1GB || ? || {{yes}} || ? || || ||
|-
| Kingston || SD-C02G || 2GB || ? || ? || {{yes}} || || {{yes}} ||
|-
| Kingston || SDC4 (N0043-012.A00LF) || 4GB || ? || ? || FSO MS2 / Linux 2.6.24: I/O Errors while formatting [http://wiki.openmoko.org/wiki/Special:Emailuser/varacanero Contact me here] || || ||
|-
| Patriot || PSF128MCSD-RC || 128MB || ? || {{no}} || ? || || ||
|-
| Patriot || PSF8GMCSDHC4 || 8GB || Class 4 || ? || ? || ? || {{yes}} || {{yes}}
|-
| PNY || P-MICROSD512-BX || 512MB || || {{yes}} || {{yes}} || {{yes}} || ||
|-
| PNY || P-MICROSD2GB-BX (card marked with MM8GR02GUACY) || 2GB || slow ? || ? || ? (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743] but apparently not enough) || ? || ||
|-
| Pretec || || 128MB || ? || ? || {{yes}} || || ||
|-
| SanDisk || SDSDQ-128 || 128MB || || {{yes}} || {{yes}} || {{yes}} || ||
|-
| SanDisk || unknown || 256MB || || {{yes}} || {{yes}} || {{yes}} || ||
|-
| SanDisk || unknown || 512MB || || {{yes}} || {{yes}} || || ||
|-
| SanDisk || SDSDQ-1024-E10M || 1GB || || {{yes}} || {{yes}} || {{yes}} || ||
|-
| SanDisk || SDSDQU-2048-E10M || 2GB || || {{yes}} || {{yes}} || {{yes}} || ||
|-
| SanDisk || SDSDQ-4096-E11M || 4GB (SDHC) || || ? || {{yes}} || ? || ||
|-
| SanDisk || SDSDQ-6144-E11M || 6GB (SDHC) || || ? || {{yes}} || {{no}} || ||
|-
| SanDisk || SDSDQ-8192-E11M || 7GB (SDHC) || 4 || ? || {{yes}} || ? || ||
|-
| SanDisk || SDSDQY-8192-A11M || 8GB (SDHC) || || ? || {{yes}} || ? || ||
|-
| SanDisk || SDSDQR-8192-E12M || 8GB (SDHC) || 4 || ? || {{yes}} || ? || ||
|-
| SanDisk || SDSDQR-8192-???? || 8GB (SDHC) || 6 || ? || {{yes}} || {{yes}} || ||
|-
| SanDisk || SDSDQ-008G-E11M || 8GB (SDHC) || 4 || ? || {{yes}} || || ||
|-
| Toshiba || SD-512R2W || 512MB || || {{no}} || {{yes}} || || ||
|-
| Transcend || TS128MUSD || 128MB || || {{no}} || {{yes}} || || ||
|-
| Transcend || TS256MUSD80 || 256MB || 80x || {{no}} || {{yes}} || {{yes}} || ||
|-
| Transcend || TS512MUSD || 512MB || || {{no}} || {{yes}} || {{yes}} || ||
|-
| Transcend || MM4GRO1GUACY || 1GB || || ? || {{yes}} || ? || ||
|-
| Transcend || TS4GUSDHC6 (card marked with MM8GR04GUACY) || 4GB (SDHC) || Class 6 || ? || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ? || ||
|-
| Transcend || TS8GUSDHC4 || 8GB (SDHC) || Class 4 || ? || ? || ? || {{yes}} || Linux 2.6.24 from Aug 28 2008
|-
| Verbatim || 47225 || 1GB || || {{no}} || {{yes}} || {{yes}} || ||
|-
| vox-fon || 1 GB || 1GB || || {{no}} || {{yes}} || || ||
|-
| (Intenso) || ? || 4GB (SDHC) || || {{no}} || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || u-boot from August, 2nd (1.3.1) boots fine) || ||
|}

Note that cards with a "'''no'''" may still work at times, but that we just have found their behaviour too erratic to consider acceptable.
(Also note that this is a bug in our version of u-boot. The cards are probably fine.)

[[Category:Neo1973 Hardware]]
[[Category:Documentation]]

Manually using GPRS

2008-08-25T00:13:01Z

Ott--: /* Turning your FreeRunner into a Network Address Translation (NAT) gateway */

The GPRS connection is made using the PPP protocol to a server identified by an "APN" at the network operator. Once a GPRS connection is made, it is possible to [[#Sharing_the_GPRS_connection_with_a_computer|share that connection with a connected computer]], allowing that computer to access the internet through the phone!

= Option 1: With GSM multiplexing and with a GUI =

{{note|The following does not appear to work if you have a SIM PIN. The dialog to enter your SIM PIN never pops up and the GSM multiplexing daemon continuous loops and runs into a SIM PIN error.}}

GSM multiplexing allows both a GPRS connection and a phone call to be handled at the same time. By default, [[Om 2008.8]] does not multiplex the GSM device. The [[FSO]] distribution, however, introduces GSM multiplexing with a new service and a DBus API to that service. The instructions to modify the OM2008.8 distribution to make use of GSM multiplexing and allow you to start GPRS from a GUI can be found here: http://freeyourphone.de/portal_v1/viewtopic.php?f=21&t=295

However, using those instructions, you will encounter a few hurdles. Do not use the gsm0710muxd that is found in the OM2008.8 repository. It will not work, instead, use the one found here:

http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/gsm0710muxd_0.9.1+gitr6fecc78198dd821bbe29efd096bd8fecd855179d-r0_armv4t.ipk

In order to install that version of gsm0710muxd, however, you will also have to install a bunch of missing dependencies. Those can be found by clicking on the dependencies found here:

http://www.angstrom-distribution.org/repo/?action=details&pnm=gsm0710muxd

Make sure that you install the armv4t versions of all packages.

The [[#Some APN names for reference|APN Reference]] table may come in handy when you are looking for the required network specific information.

Once you follow through with all the instructions, you will notice that the "Services" GUI will crash. This has to do with this bug: http://docs.openmoko.org/trac/ticket/1718

The fix is to change the "init()" call on line 82 of /usr/lib/python2.5/site-packages/gtk-2.0/gtk/_init_.py to "_init()" (add an underscore).

You may also have to modify your /etc/resolv.conf file and add the nameserver (DNS Server) of your service provider if you have DNS resolution problems.

Then, hopefully, you should be up in running with GPRS and a GUI to turn it on and off.

= Option 2: With GSM multiplexing and without a GUI =

'''1) In /etc/rc5.d start gsm0710muxd before gsmd:'''
* S34gsm0710muxd -> ../init.d/gsm0710muxd
* S35gsmd -> ../init.d/gsmd

'''2) Modify S35gsmd so it can start either with or without gsm0710muxd:'''
<pre>
...
case "$1" in
start)
if [ "$(pidof gsm0710muxd)" ] ; then
id=$(date +%s)
GSM_DEV=$(dbus-send --system --print-reply --type=method_call --dest=org.pyneo.muxer /org/pyneo/Muxer org.freesmartphone.GSM.MUX.AllocChannel string:$id | grep string | cut -d \" -f 2)
else
[ -n "$GSM_POW" ] && ( echo "0" >$GSM_POW; sleep 1 )
[ -n "$GSM_POW" ] && ( echo "1" >$GSM_POW; sleep 1 )
[ -n "$GSM_RES" ] && ( echo "1" >$GSM_RES; sleep 1 )
[ -n "$GSM_RES" ] && ( echo "0" >$GSM_RES; sleep 2 )
fi

if [ ! "$GSM_DEV" ] ; then
echo "GSM_DEV was not set"
exit 1
fi

echo -n "Starting GSM daemon: "
start-stop-daemon -S -x /usr/sbin/gsmd -- gsmd -p $GSM_DEV $GSMD_OPTS -d -l /var/log/gsmd

if [ $? = 0 ]; then
echo "gsmd."
else
echo "(failed.)"
fi
;;
stop)
if [ ! "$(pidof gsm0710muxd)" ] ; then
[ -n "$GSM_POW" ] && echo "0" >$GSM_POW
fi

echo -n "Stopping GSM daemon: "
...
</pre>

'''3) Remove the tty from /etc/ppp/peers/simyo''' (replace simyo with your provider).

'''4) Use a ppp start script like this:'''
<pre>
$ cat /usr/local/bin/ppp-start
#!/bin/sh

id=$(date +%s)
TTY=$(dbus-send --system --print-reply --type=method_call --dest=org.pyneo.muxer /org/pyneo/Muxer org.freesmartphone.GSM.MUX.AllocChannel string:$id | grep string | cut -d \" -f 2)
logger -t ppp-start "using tty $TTY"
pppd $TTY call simyo
</pre>

'''5) Use "killall pppd" to terminate the PPP connection.'''

= Option 3: Without GSM multiplexing and without a GUI =

The program that implements PPP on Linux is [[pppd]], which we need to configure and run to get a connection. When that is working, we can configure pppd to wait until it's needed before it connects, and to disconnect if the connection becomes idle. Further, we can start pppd in the background during the boot process.

== Configuring pppd for manual connections ==

You'll need /etc/ppp/peers/gprs:
<pre>
# Uncomment the following if you want some debug.
#debug
#logfile /var/volatile/log/pppd.log
lock
/dev/ttySAC0 115200
crtscts
connect /etc/ppp/gprs-connect-chat
disconnect /etc/ppp/gprs-disconnect-chat
hide-password
usepeerdns
ipcp-accept-local
noauth
noipdefault
novj
novjccomp
defaultroute
replacedefaultroute
# Reopen the connection if it fails, pausing for a while.
persist
holdoff 15
# Check the line every 20 seconds and presume
# the peer is gone if no replay for 4 times.
lcp-echo-interval 20
lcp-echo-failure 4
</pre>

Depending on the APN, you may need password authentication using CHAP or PAP. In /etc/ppp/pap-secrets you can add the following default line for "password-less" connections:

<pre>
# client server secret IP addresses
* * "" *
</pre>

For CHAP, lines in /etc/ppp/chap-secrets are used. For PAP, the lines are in /etc/ppp/pap-secrets. The client should match the "user" option in pppd the config file (below). You can use * to mean any here, but the option user "" doesn't mean empty!

For example:

<pre>
# Secrets for authentication using CHAP
# client server secret IP addresses
"user" * "password" *
</pre>

For this you need the following options in /etc/ppp/peers/gprs:

<pre>
# username to use for authentication, should match "client" in /etc/ppp/{chap,pap}-secrets
user "user"
</pre>

== gprs-connect-chat, version 1 ==

You'll also need /etc/ppp/gprs-connect-chat (needs "chmod +x"):

<pre>
#!/bin/sh -e
exec chat -v -S -s\
TIMEOUT 15\
"" "\K\K\K\d+++ATH"\
OK-AT-OK ATZ\
OK ATE1\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 60\
OK AT+CFUN=1\
OK AT+COPS\
OK AT+CGDCONT=1,\"IP\",\"internet\"\
OK ATD*99#\
CONNECT /n/d
</pre>

(08/18/08) Note: I needed to add the command "AT+CMOD=2" (formatted as "OK AT+CMOD=2\" without the quotes) in order to get GPRS working with the above script (otherwise it would ERROR on the CFUN, COPS, or the ATD if the other two were removed). I have T-Mobile (US) with the $5.99 "tzones" addon, which works with Minimo as it supports HTTP proxy setups.

== gprs-connect-chat, version 2 ==

Update: On my freerunner the first AT+CFUN=1 always generated ERROR. I managed to get gprs work by using the following script from http://lists.openmoko.org/pipermail/community/2008-July/023246.html:

<pre>
#!/bin/sh -e
exec /usr/sbin/chat -v \
TIMEOUT 10 \
OK-AT-'' ''\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 30 \
'' ATZ\
OK ATE1\
OK AT+CFUN=1\
ERROR AT+CPIN=\"XXXX\"\ << USE YOUR OWN
OK AT+COPS\
OK AT+CGDCONT=1,\"IP\",\"internet\"\
OK 'ATDT*99***1#'\
CONNECT ''
</pre>

The error seems to vary a bit, sometimes it's before AT+COPS, sometimes as above. I have two versions of the gprs-connect-chat, which I vary between depending on which is needed. Or is there a way to specify two acceptable answers like {OK,ERROR}?

You will need to adjust the APN name "internet" in at+cgdcont line and possibly the phone number in the ATD line to match what your network operator provides. See below in the table "Some APN names for reference" for the right settings for your operator.

== gprs-disconnect-chat ==

Also good to have is /etc/ppp/gprs-disconnect-chat (needs "chmod +x"):

<pre>
#!/bin/sh -e
/usr/sbin/chat -v\
ABORT OK\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO CARRIER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 12\
"" "\K\K\K\d+++ATH"\
"NO CARRIER-AT-OK" "\c"
</pre>

== Starting PPP connection ==

The following script can be used to start the ppp connection. First it stops gsmd because gsmd may put the phone in a unknown state. It then turns on the power to the phone, modifies the ownership, and then creates a tty connection. Finally it starts [[pppd]] with the gprs settings.

<pre>
/etc/init.d/gsmd stop
echo "1" > /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
chown uucp.uucp /dev/ttySAC0
stty -F /dev/ttySAC0 crtscts
pppd call gprs
</pre>

If you are having problems connecting ensure you have a good GSM signal and replace the last line with the below line. This will allow you to see the details of the connection on the console.

<pre>
pppd debug nodetach call gprs
</pre>

The config above will establish a persistant link over gprs. The battery will run low in less than an hour. See an example for an on-demand config below.

=== Resolve.conf issues ===

The latest build seems to have solved the following issue, it should be automatically updated by pppd.

If you expeience DNS issues after connecting to DNS you may need a proper /etc/resolv.conf:

<pre>
ln -sf /var/run/resolv.conf /etc
</pre>

If needed put your nameserver for usb-net into /var/run/resolv.conf, not in /etc.

The image does not set a correct resolv.conf. i do so with an

<pre>
echo nameserver 192.168.0.201 > /var/run/resolv.conf
</pre>

in the right place. because a post-up in /etc/network/interfaces is not supported i do that in /etc/network/if-up.d/08setupdns

another problem is pppd's /etc/ppp/ip-down.d/92removedns which does not properly remove the link when shuting down ppp. my fix is this script:

<pre>
#!/bin/sh
ACTUALCONF=/var/run/resolv.conf
PPPCONF=/var/run/ppp/resolv.conf
if [ -f $PPPCONF ] ; then
if [ -f $ACTUALCONF ] ; then
if [ ! -h $ACTUALCONF -o ! "`readlink $ACTUALCONF 2>&1`" = "$PPPCONF" ] ; then
mv $ACTUALCONF $ACTUALCONF.ppporig
fi
fi

ln -sf $PPPCONF $ACTUALCONF
fi
</pre>

=== Some APN names for reference ===

{| border="1"
! Country
! Carrier
! Plan
! APN/Phone
! user/password if required
! Working pppd scripts
|-
| Australia || Vodafone || Any || vfinternet.au || ||
|-
| Canada || Fido || Any, behind NAT || internet.fido.ca || fido/fido || mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device
org.freesmartphone.GSM.PDP.ActivateContext internet.fido.ca fido
fido
|-
| Canada || Rogers || Any, behind NAT || internet.com || wapuser1/wap || nameserver 207.181.101.4
|-
| Denmark || Telmore || || wap || must be empty ||
|-
| Estonia || Elisa || Any, behind NAT || internet || ||
|-
| Estonia || EMT || Any, behind NAT || internet.emt.ee || ||
|-
| Finland || Saunalahti || Any || internet.saunalahti || ||
|-
| Finland || Sonera || Any, behind NAT || internet || ||
|-
| Finland || Sonera || Any, public IP || prointernet || ||
|-
| France || SFR || 10.x.x.x? || websfr || || under tests
|-
| France || SFR || 10.x.x.x? || wapsfr[1]|| || under tests
|-
| France || Orange || ??? || orange.fr || || under tests
|-
| France || Bouyges Telecom || Web & Mail || mmsbouygtel.com || || Work great under FSO. Just follow instructions at http://wiki.openmoko.org/wiki/GPRS_FSO. Proxy: 62.201.129.225:8080. For emails, only ports 25 (smtp) and 110 (pop) are allowed. (They use a transparent proxy ...)
|-
| Germany || E-Plus || BASE (and others?) || internet.eplus.de || eplus gprs || [[Base pppd scripts]]
|-
| Germany || E-Plus || Simyo || internet.eplus.de || simyo simyo || [[simyo pppd scripts]]
|-
| Germany || T-Mobile || || internet.t-mobile || ||
|-
| Germany || Vodafone || Any, behind NAT || web.vodafone.de || ||
|-
| India || AirTel || MobileOffice || airtelgprs.com || ||
|-
| Italy || Wind || Superinternet, public IP || internet.wind / *99# || wind/wind (any string) || [[Wind pppd scripts]]
|-
| Netherlands || Vodafone || Any || live.vodafone.com / *99***1#|| || [[Vodafone pppd scripts]]
|-
| New Zealand || Vodafone || Any || live.vodafone.com / *99***2#|| ||
|-
| Norway || Netcom || Any || internet.netcom.no || ||
|-
| Norway || OneCall || Any || internet || ||
|-
| Norway || Telenor || Any || telenor || ||
|-
| Sweden || Parlino || || internet.parlino.se || || [[GPRS_FSO|Works with FSO]]
|-
| Switzerland || Swisscom || e.g. Natel Basic Liberty, behind NAT || gprs.swisscom.ch || ||
|-
| UK || T-Mobile|| || general.t-mobile.uk || ||
|-
| UK || Virgin || || goto.virginmobile.uk || user ||
|-
| UK || [http://www.filesaveas.com/gprs.html other providers] || || || ||
|-
| USA || AT&T || Unlimited data plan (attached to pay-as-you-go voice plan) || wap.cingular / *99***1# || WAP@CINGULARGPRS.COM/CINGULAR1 ||
|-
| USA || Cincinnati Bell Wireless || || wap.gocbw.com || cbw ||
|-
| USA || Cingular (AT&T) || Less than full internet || wap.cingular / may require *99***1# || ||
|-
| USA || T-mobile || Anything less than full internet || wap.voicestream.com || || Need to set proxy to 216.155.165.50 T-Mobile docs say "216.155.165.050". 050 octal = 40 decimal and will *not* work. I think port is 8080 or 9100. No luck w/ pppd scripts. GPRS_FSO directions work under FSO though.
|-
| USA || T-mobile || Regular internet plan || internet2.voicestream.com || || [[T-Mobile pppd scripts]]
|-
| USA || T-mobile || "VPN" internet plan || internet3.voicestream.com || ||
|-
| Venezuela || Digitel || Pre- y post-pago || gprsweb.digitel.ve || ||
|-
|}

[1] connected through a WAP proxy (slower, but the only way to access Vodafone live! and SFR portal)

[2] Unless stated otherwise the phone number to call is "*99#"

Also see Ross Barkman's page for a detailed list of more [http://www.taniwha.org.uk/gprs.html global GPRS providers APN details]

== Starting pppd automatically ==

Once you have finished debugging your gprs-connect-chat and gprs options files, you may wish to automatically connect whenever needed and hang up when finished. Make sure you understand the impact of this change to your carrier plan billing. This is not recommended unless you have a large-use or unlimited data plan. These scripts do NOT prompt you before connecting.

=== On-demand connection settings ===

Additional settings are needed if you want the actual connection to be up only while there is traffic. In the 'gprs' file above, insert the following, making sure 'nodetach' is commented out. If 'nodetach' is on, the boot process will stop when it starts pppd. Also remove the option 'persist' mentioned above.

<pre>

# Wait until needed before connecting
demand

# Disconnect if idle for given amount of seconds
idle 20

</pre>

=== Start on boot (method 1) ===

Add the following definition to /etc/network/interfaces:
<pre>
auto ppp0
iface ppp0 inet ppp
provider gprs
</pre>

That should be it. Now you can use 'ifup ppp0' and 'ifdown ppp0' manually too.

=== Start on boot (method 2) ===

Create the following file as /etc/ppp/ppp_on_boot (needs chmod +x). The /etc/init.d/ppp script will call it to set up the daemon.
<pre>
#!/bin/sh
#
# Rename this file to ppp_on_boot and pppd will be fired up as
# soon as the system comes up, connecting to `provider'.
#
# If you also make this file executable, and replace the first line
# with just "#!/bin/sh", the commands below will be executed instead.
#

# The location of the ppp daemon itself (shouldn't need to be changed)
PPPD=/usr/sbin/pppd

# The default provider to connect to
$PPPD call gprs

# Additional connections, which would just use settings from
# /etc/ppp/options.<tty>
#$PPPD ttyS0
#$PPPD ttyS1
#$PPPD ttyS2
#$PPPD ttyS3
</pre>

Finally, you need to add the /etc/init.d/ppp script to the init process by creating symbolic links from the appropriate directories. I chose the following:

<pre>
/etc/rc0.d/K25ppp
/etc/rc1.d/K45ppp
/etc/rc2.d/S45ppp
/etc/rc3.d/S45ppp
/etc/rc4.d/S45ppp
/etc/rc5.d/S45ppp
/etc/rc6.d/K25ppp
</pre>

= Sharing the GPRS connection with a computer =

Once you successfully connect to your network operator, you can start sharing your data plan with your computer through USB or Bluetooth networking. The following describes how you can do so through USB networking.

== Setting up your computer's network settings ==

I find it useful to have my computer automatically acquire it's network address, mask, gateway, and DNS servers from the FreeRunner instead of manually setting these up. In order to this, I installed busybox-udhcpd from the Angstrom repositories (see [[Repositories]])

opkg install busybox-udhcpd

Once it is installed, it needs to be configured. Edit the /etc/udhcpd.conf file. Mine looks like this:

<pre>
# Sample udhcpd configuration file (/etc/udhcpd.conf)

# The start and end of the IP lease block

start 192.168.0.200 #default: 192.168.0.20
end 192.168.0.200 #default: 192.168.0.254

# The interface that udhcpd will use

interface usb0 #default: eth0

# The maximim number of leases (includes addressesd reserved
# by OFFER's, DECLINE's, and ARP conficts

#max_leases 254 #default: 254

# If remaining is true (default), udhcpd will store the time
# remaining for each lease in the udhcpd leases file. This is
# for embedded systems that cannot keep time between reboots.
# If you set remaining to no, the absolute time that the lease
# expires at will be stored in the dhcpd.leases file.

#remaining yes #default: yes

# The time period at which udhcpd will write out a dhcpd.leases
# file. If this is 0, udhcpd will never automatically write a
# lease file. (specified in seconds)

#auto_time 7200 #default: 7200 (2 hours)

# The amount of time that an IP will be reserved (leased) for if a
# DHCP decline message is received (seconds).

#decline_time 3600 #default: 3600 (1 hour)

# The amount of time that an IP will be reserved (leased) for if an
# ARP conflct occurs. (seconds

#conflict_time 3600 #default: 3600 (1 hour)

# How long an offered address is reserved (leased) in seconds

#offer_time 60 #default: 60 (1 minute)

# If a lease to be given is below this value, the full lease time is
# instead used (seconds).

#min_lease 60 #defult: 60

# The location of the leases file

#lease_file /var/lib/misc/udhcpd.leases #defualt: /var/lib/misc/udhcpd.
leases

# The location of the pid file
#pidfile /var/run/udhcpd.pid #default: /var/run/udhcpd.pid

# Everytime udhcpd writes a leases file, the below script will be called.
# Useful for writing the lease file to flash every few hours.

#notify_file #default: (no script)

#notify_file dumpleases # <--- usefull for debugging

# The following are bootp specific options, setable by udhcpd.

#siaddr 192.168.0.22 #default: 0.0.0.0

#sname zorak #default: (none)

#boot_file /var/nfs_root #default: (none)

# The remainer of options are DHCP options and can be specifed with the
# keyword 'opt' or 'option'. If an option can take multiple items, such
# as the dns option, they can be listed on the same line, or multiple
# lines. The only option with a default is 'lease'.

#Examles
opt dns 192.168.0.202 <your APN's DNS server>
option subnet 255.255.255.0
opt router 192.168.0.202
opt wins 192.168.0.202
#option dns 129.219.13.81 # appened to above DNS servers for a total of 3
option domain local
option lease 864000 # 10 days of seconds

# Currently supported options, for more info, see options.c
#subnet
#timezone
#router
#timesvr
#namesvr
#dns
#logsvr
#cookiesvr
#lprsvr
#bootsize
#domain
#swapsvr
#rootpath
#ipttl
#mtu
#broadcast
#wins
#lease
#ntpsrv
#tftp
#bootfile
</pre>

Notice that I set the start and end of the IP lease block to 192.168.0.200. If you follow the instructions at [[USB Networking]], this is the address that it assumes the host to be and the /etc/resolv.conf file points to this address to allow name resolution from your phone.

The interface in this case is usb0. This will have to be set differently if you are using Bluetooth.

The dns is set to the FreeRunner's address, as well as my network operator's DNS server address. You don't have to use your network operator's DNS address if you can find a caching nameserver for the FreeRunner.

The router is set to the FreeRunner.

== Turning your FreeRunner into a Network Address Translation (NAT) gateway ==

I set up my FreeRunner so that it acts as a NAT gateway so that all traffic that goes to my network operator appears to originate from the phone. I installed iptables to accomplish this:

opkg install iptables iptables-utils kernel-module-ipt-masquerade kernel-module-iptable-nat

Once that is installed, I have the following script named firewall.sh that I use to set up the NAT once connected to the GPRS network:

<pre>
#!/bin/sh
IPTABLES='/usr/sbin/iptables'

# Set interface values
EXTIF='ppp0'
INTIF='usb0'

# enable ip forwarding in the kernel
/bin/echo 1 > /proc/sys/net/ipv4/ip_forward

# flush rules and delete chains
$IPTABLES -F
$IPTABLES -X

#Enable masquerading to allow LAN internet access
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE

#Forward LAN traffic from LAN $INTIF to Internet $EXTIF
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -m state --state NEW,ESTABLISHED -j ACCEPT

#Allowing access to the SSH server"
#$IPTABLES -A INPUT --protocol tcp --dport 22 -j ACCEPT

#Allowing access to the HTTP server"
#$IPTABLES -A INPUT --protocol tcp --dport 80 -j ACCEPT

# block out all other Internet access on $EXTIF
$IPTABLES -A INPUT -i $EXTIF -m state --state NEW,INVALID -j DROP
$IPTABLES -A FORWARD -i $EXTIF -m state --state NEW,INVALID -j DROP
</pre>

so once connected through GPRS, I run:

./firewall.sh

and then you should be able to connect to the internet from your computer!

Of course this also works when sharing your WLAN connection. Just set EXTIF to eth0.

== See also ==
* [[pppd]]
* [[Manually using GSM]]
* [[Manually using Bluetooth]]
* [[GPRS FSO]]
{{Languages|Manually_using_GPRS}}

[[Category:Documentation]]
[[Category:Application Developer]]
[[Category:Guides]]
[[Category:Networking]]

Manually using GPRS

2008-08-24T23:59:18Z

Ott--:

The GPRS connection is made using the PPP protocol to a server identified by an "APN" at the network operator. Once a GPRS connection is made, it is possible to [[#Sharing_the_GPRS_connection_with_a_computer|share that connection with a connected computer]], allowing that computer to access the internet through the phone!

= Option 1: With GSM multiplexing and with a GUI =

{{note|The following does not appear to work if you have a SIM PIN. The dialog to enter your SIM PIN never pops up and the GSM multiplexing daemon continuous loops and runs into a SIM PIN error.}}

GSM multiplexing allows both a GPRS connection and a phone call to be handled at the same time. By default, [[Om 2008.8]] does not multiplex the GSM device. The [[FSO]] distribution, however, introduces GSM multiplexing with a new service and a DBus API to that service. The instructions to modify the OM2008.8 distribution to make use of GSM multiplexing and allow you to start GPRS from a GUI can be found here: http://freeyourphone.de/portal_v1/viewtopic.php?f=21&t=295

However, using those instructions, you will encounter a few hurdles. Do not use the gsm0710muxd that is found in the OM2008.8 repository. It will not work, instead, use the one found here:

http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/gsm0710muxd_0.9.1+gitr6fecc78198dd821bbe29efd096bd8fecd855179d-r0_armv4t.ipk

In order to install that version of gsm0710muxd, however, you will also have to install a bunch of missing dependencies. Those can be found by clicking on the dependencies found here:

http://www.angstrom-distribution.org/repo/?action=details&pnm=gsm0710muxd

Make sure that you install the armv4t versions of all packages.

The [[#Some APN names for reference|APN Reference]] table may come in handy when you are looking for the required network specific information.

Once you follow through with all the instructions, you will notice that the "Services" GUI will crash. This has to do with this bug: http://docs.openmoko.org/trac/ticket/1718

The fix is to change the "init()" call on line 82 of /usr/lib/python2.5/site-packages/gtk-2.0/gtk/_init_.py to "_init()" (add an underscore).

You may also have to modify your /etc/resolv.conf file and add the nameserver (DNS Server) of your service provider if you have DNS resolution problems.

Then, hopefully, you should be up in running with GPRS and a GUI to turn it on and off.

= Option 2: With GSM multiplexing and without a GUI =

'''1) In /etc/rc5.d start gsm0710muxd before gsmd:'''
* S34gsm0710muxd -> ../init.d/gsm0710muxd
* S35gsmd -> ../init.d/gsmd

'''2) Modify S35gsmd so it can start either with or without gsm0710muxd:'''
<pre>
...
case "$1" in
start)
if [ "$(pidof gsm0710muxd)" ] ; then
id=$(date +%s)
GSM_DEV=$(dbus-send --system --print-reply --type=method_call --dest=org.pyneo.muxer /org/pyneo/Muxer org.freesmartphone.GSM.MUX.AllocChannel string:$id | grep string | cut -d \" -f 2)
else
[ -n "$GSM_POW" ] && ( echo "0" >$GSM_POW; sleep 1 )
[ -n "$GSM_POW" ] && ( echo "1" >$GSM_POW; sleep 1 )
[ -n "$GSM_RES" ] && ( echo "1" >$GSM_RES; sleep 1 )
[ -n "$GSM_RES" ] && ( echo "0" >$GSM_RES; sleep 2 )
fi

if [ ! "$GSM_DEV" ] ; then
echo "GSM_DEV was not set"
exit 1
fi

echo -n "Starting GSM daemon: "
start-stop-daemon -S -x /usr/sbin/gsmd -- gsmd -p $GSM_DEV $GSMD_OPTS -d -l /var/log/gsmd

if [ $? = 0 ]; then
echo "gsmd."
else
echo "(failed.)"
fi
;;
stop)
if [ ! "$(pidof gsm0710muxd)" ] ; then
[ -n "$GSM_POW" ] && echo "0" >$GSM_POW
fi

echo -n "Stopping GSM daemon: "
...
</pre>

'''3) Remove the tty from /etc/ppp/peers/simyo''' (replace simyo with your provider).

'''4) Use a ppp start script like this:'''
<pre>
$ cat /usr/local/bin/ppp-start
#!/bin/sh

id=$(date +%s)
TTY=$(dbus-send --system --print-reply --type=method_call --dest=org.pyneo.muxer /org/pyneo/Muxer org.freesmartphone.GSM.MUX.AllocChannel string:$id | grep string | cut -d \" -f 2)
logger -t ppp-start "using tty $TTY"
pppd $TTY call simyo
</pre>

'''5) Use "killall pppd" to terminate the PPP connection.'''

= Option 3: Without GSM multiplexing and without a GUI =

The program that implements PPP on Linux is [[pppd]], which we need to configure and run to get a connection. When that is working, we can configure pppd to wait until it's needed before it connects, and to disconnect if the connection becomes idle. Further, we can start pppd in the background during the boot process.

== Configuring pppd for manual connections ==

You'll need /etc/ppp/peers/gprs:
<pre>
# Uncomment the following if you want some debug.
#debug
#logfile /var/volatile/log/pppd.log
lock
/dev/ttySAC0 115200
crtscts
connect /etc/ppp/gprs-connect-chat
disconnect /etc/ppp/gprs-disconnect-chat
hide-password
usepeerdns
ipcp-accept-local
noauth
noipdefault
novj
novjccomp
defaultroute
replacedefaultroute
# Reopen the connection if it fails, pausing for a while.
persist
holdoff 15
# Check the line every 20 seconds and presume
# the peer is gone if no replay for 4 times.
lcp-echo-interval 20
lcp-echo-failure 4
</pre>

Depending on the APN, you may need password authentication using CHAP or PAP. In /etc/ppp/pap-secrets you can add the following default line for "password-less" connections:

<pre>
# client server secret IP addresses
* * "" *
</pre>

For CHAP, lines in /etc/ppp/chap-secrets are used. For PAP, the lines are in /etc/ppp/pap-secrets. The client should match the "user" option in pppd the config file (below). You can use * to mean any here, but the option user "" doesn't mean empty!

For example:

<pre>
# Secrets for authentication using CHAP
# client server secret IP addresses
"user" * "password" *
</pre>

For this you need the following options in /etc/ppp/peers/gprs:

<pre>
# username to use for authentication, should match "client" in /etc/ppp/{chap,pap}-secrets
user "user"
</pre>

== gprs-connect-chat, version 1 ==

You'll also need /etc/ppp/gprs-connect-chat (needs "chmod +x"):

<pre>
#!/bin/sh -e
exec chat -v -S -s\
TIMEOUT 15\
"" "\K\K\K\d+++ATH"\
OK-AT-OK ATZ\
OK ATE1\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 60\
OK AT+CFUN=1\
OK AT+COPS\
OK AT+CGDCONT=1,\"IP\",\"internet\"\
OK ATD*99#\
CONNECT /n/d
</pre>

(08/18/08) Note: I needed to add the command "AT+CMOD=2" (formatted as "OK AT+CMOD=2\" without the quotes) in order to get GPRS working with the above script (otherwise it would ERROR on the CFUN, COPS, or the ATD if the other two were removed). I have T-Mobile (US) with the $5.99 "tzones" addon, which works with Minimo as it supports HTTP proxy setups.

== gprs-connect-chat, version 2 ==

Update: On my freerunner the first AT+CFUN=1 always generated ERROR. I managed to get gprs work by using the following script from http://lists.openmoko.org/pipermail/community/2008-July/023246.html:

<pre>
#!/bin/sh -e
exec /usr/sbin/chat -v \
TIMEOUT 10 \
OK-AT-'' ''\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 30 \
'' ATZ\
OK ATE1\
OK AT+CFUN=1\
ERROR AT+CPIN=\"XXXX\"\ << USE YOUR OWN
OK AT+COPS\
OK AT+CGDCONT=1,\"IP\",\"internet\"\
OK 'ATDT*99***1#'\
CONNECT ''
</pre>

The error seems to vary a bit, sometimes it's before AT+COPS, sometimes as above. I have two versions of the gprs-connect-chat, which I vary between depending on which is needed. Or is there a way to specify two acceptable answers like {OK,ERROR}?

You will need to adjust the APN name "internet" in at+cgdcont line and possibly the phone number in the ATD line to match what your network operator provides. See below in the table "Some APN names for reference" for the right settings for your operator.

== gprs-disconnect-chat ==

Also good to have is /etc/ppp/gprs-disconnect-chat (needs "chmod +x"):

<pre>
#!/bin/sh -e
/usr/sbin/chat -v\
ABORT OK\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO CARRIER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 12\
"" "\K\K\K\d+++ATH"\
"NO CARRIER-AT-OK" "\c"
</pre>

== Starting PPP connection ==

The following script can be used to start the ppp connection. First it stops gsmd because gsmd may put the phone in a unknown state. It then turns on the power to the phone, modifies the ownership, and then creates a tty connection. Finally it starts [[pppd]] with the gprs settings.

<pre>
/etc/init.d/gsmd stop
echo "1" > /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
chown uucp.uucp /dev/ttySAC0
stty -F /dev/ttySAC0 crtscts
pppd call gprs
</pre>

If you are having problems connecting ensure you have a good GSM signal and replace the last line with the below line. This will allow you to see the details of the connection on the console.

<pre>
pppd debug nodetach call gprs
</pre>

The config above will establish a persistant link over gprs. The battery will run low in less than an hour. See an example for an on-demand config below.

=== Resolve.conf issues ===

The latest build seems to have solved the following issue, it should be automatically updated by pppd.

If you expeience DNS issues after connecting to DNS you may need a proper /etc/resolv.conf:

<pre>
ln -sf /var/run/resolv.conf /etc
</pre>

If needed put your nameserver for usb-net into /var/run/resolv.conf, not in /etc.

The image does not set a correct resolv.conf. i do so with an

<pre>
echo nameserver 192.168.0.201 > /var/run/resolv.conf
</pre>

in the right place. because a post-up in /etc/network/interfaces is not supported i do that in /etc/network/if-up.d/08setupdns

another problem is pppd's /etc/ppp/ip-down.d/92removedns which does not properly remove the link when shuting down ppp. my fix is this script:

<pre>
#!/bin/sh
ACTUALCONF=/var/run/resolv.conf
PPPCONF=/var/run/ppp/resolv.conf
if [ -f $PPPCONF ] ; then
if [ -f $ACTUALCONF ] ; then
if [ ! -h $ACTUALCONF -o ! "`readlink $ACTUALCONF 2>&1`" = "$PPPCONF" ] ; then
mv $ACTUALCONF $ACTUALCONF.ppporig
fi
fi

ln -sf $PPPCONF $ACTUALCONF
fi
</pre>

=== Some APN names for reference ===

{| border="1"
! Country
! Carrier
! Plan
! APN/Phone
! user/password if required
! Working pppd scripts
|-
| Australia || Vodafone || Any || vfinternet.au || ||
|-
| Canada || Fido || Any, behind NAT || internet.fido.ca || fido/fido || mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device
org.freesmartphone.GSM.PDP.ActivateContext internet.fido.ca fido
fido
|-
| Canada || Rogers || Any, behind NAT || internet.com || wapuser1/wap || nameserver 207.181.101.4
|-
| Denmark || Telmore || || wap || must be empty ||
|-
| Estonia || Elisa || Any, behind NAT || internet || ||
|-
| Estonia || EMT || Any, behind NAT || internet.emt.ee || ||
|-
| Finland || Saunalahti || Any || internet.saunalahti || ||
|-
| Finland || Sonera || Any, behind NAT || internet || ||
|-
| Finland || Sonera || Any, public IP || prointernet || ||
|-
| France || SFR || 10.x.x.x? || websfr || || under tests
|-
| France || SFR || 10.x.x.x? || wapsfr[1]|| || under tests
|-
| France || Orange || ??? || orange.fr || || under tests
|-
| France || Bouyges Telecom || Web & Mail || mmsbouygtel.com || || Work great under FSO. Just follow instructions at http://wiki.openmoko.org/wiki/GPRS_FSO. Proxy: 62.201.129.225:8080. For emails, only ports 25 (smtp) and 110 (pop) are allowed. (They use a transparent proxy ...)
|-
| Germany || E-Plus || BASE (and others?) || internet.eplus.de || eplus gprs || [[Base pppd scripts]]
|-
| Germany || E-Plus || Simyo || internet.eplus.de || simyo simyo || [[simyo pppd scripts]]
|-
| Germany || T-Mobile || || internet.t-mobile || ||
|-
| Germany || Vodafone || Any, behind NAT || web.vodafone.de || ||
|-
| India || AirTel || MobileOffice || airtelgprs.com || ||
|-
| Italy || Wind || Superinternet, public IP || internet.wind / *99# || wind/wind (any string) || [[Wind pppd scripts]]
|-
| Netherlands || Vodafone || Any || live.vodafone.com / *99***1#|| || [[Vodafone pppd scripts]]
|-
| New Zealand || Vodafone || Any || live.vodafone.com / *99***2#|| ||
|-
| Norway || Netcom || Any || internet.netcom.no || ||
|-
| Norway || OneCall || Any || internet || ||
|-
| Norway || Telenor || Any || telenor || ||
|-
| Sweden || Parlino || || internet.parlino.se || || [[GPRS_FSO|Works with FSO]]
|-
| Switzerland || Swisscom || e.g. Natel Basic Liberty, behind NAT || gprs.swisscom.ch || ||
|-
| UK || T-Mobile|| || general.t-mobile.uk || ||
|-
| UK || Virgin || || goto.virginmobile.uk || user ||
|-
| UK || [http://www.filesaveas.com/gprs.html other providers] || || || ||
|-
| USA || AT&T || Unlimited data plan (attached to pay-as-you-go voice plan) || wap.cingular / *99***1# || WAP@CINGULARGPRS.COM/CINGULAR1 ||
|-
| USA || Cincinnati Bell Wireless || || wap.gocbw.com || cbw ||
|-
| USA || Cingular (AT&T) || Less than full internet || wap.cingular / may require *99***1# || ||
|-
| USA || T-mobile || Anything less than full internet || wap.voicestream.com || || Need to set proxy to 216.155.165.50 T-Mobile docs say "216.155.165.050". 050 octal = 40 decimal and will *not* work. I think port is 8080 or 9100. No luck w/ pppd scripts. GPRS_FSO directions work under FSO though.
|-
| USA || T-mobile || Regular internet plan || internet2.voicestream.com || || [[T-Mobile pppd scripts]]
|-
| USA || T-mobile || "VPN" internet plan || internet3.voicestream.com || ||
|-
| Venezuela || Digitel || Pre- y post-pago || gprsweb.digitel.ve || ||
|-
|}

[1] connected through a WAP proxy (slower, but the only way to access Vodafone live! and SFR portal)

[2] Unless stated otherwise the phone number to call is "*99#"

Also see Ross Barkman's page for a detailed list of more [http://www.taniwha.org.uk/gprs.html global GPRS providers APN details]

== Starting pppd automatically ==

Once you have finished debugging your gprs-connect-chat and gprs options files, you may wish to automatically connect whenever needed and hang up when finished. Make sure you understand the impact of this change to your carrier plan billing. This is not recommended unless you have a large-use or unlimited data plan. These scripts do NOT prompt you before connecting.

=== On-demand connection settings ===

Additional settings are needed if you want the actual connection to be up only while there is traffic. In the 'gprs' file above, insert the following, making sure 'nodetach' is commented out. If 'nodetach' is on, the boot process will stop when it starts pppd. Also remove the option 'persist' mentioned above.

<pre>

# Wait until needed before connecting
demand

# Disconnect if idle for given amount of seconds
idle 20

</pre>

=== Start on boot (method 1) ===

Add the following definition to /etc/network/interfaces:
<pre>
auto ppp0
iface ppp0 inet ppp
provider gprs
</pre>

That should be it. Now you can use 'ifup ppp0' and 'ifdown ppp0' manually too.

=== Start on boot (method 2) ===

Create the following file as /etc/ppp/ppp_on_boot (needs chmod +x). The /etc/init.d/ppp script will call it to set up the daemon.
<pre>
#!/bin/sh
#
# Rename this file to ppp_on_boot and pppd will be fired up as
# soon as the system comes up, connecting to `provider'.
#
# If you also make this file executable, and replace the first line
# with just "#!/bin/sh", the commands below will be executed instead.
#

# The location of the ppp daemon itself (shouldn't need to be changed)
PPPD=/usr/sbin/pppd

# The default provider to connect to
$PPPD call gprs

# Additional connections, which would just use settings from
# /etc/ppp/options.<tty>
#$PPPD ttyS0
#$PPPD ttyS1
#$PPPD ttyS2
#$PPPD ttyS3
</pre>

Finally, you need to add the /etc/init.d/ppp script to the init process by creating symbolic links from the appropriate directories. I chose the following:

<pre>
/etc/rc0.d/K25ppp
/etc/rc1.d/K45ppp
/etc/rc2.d/S45ppp
/etc/rc3.d/S45ppp
/etc/rc4.d/S45ppp
/etc/rc5.d/S45ppp
/etc/rc6.d/K25ppp
</pre>

= Sharing the GPRS connection with a computer =

Once you successfully connect to your network operator, you can start sharing your data plan with your computer through USB or Bluetooth networking. The following describes how you can do so through USB networking.

== Setting up your computer's network settings ==

I find it useful to have my computer automatically acquire it's network address, mask, gateway, and DNS servers from the FreeRunner instead of manually setting these up. In order to this, I installed busybox-udhcpd from the Angstrom repositories (see [[Repositories]])

opkg install busybox-udhcpd

Once it is installed, it needs to be configured. Edit the /etc/udhcpd.conf file. Mine looks like this:

<pre>
# Sample udhcpd configuration file (/etc/udhcpd.conf)

# The start and end of the IP lease block

start 192.168.0.200 #default: 192.168.0.20
end 192.168.0.200 #default: 192.168.0.254

# The interface that udhcpd will use

interface usb0 #default: eth0

# The maximim number of leases (includes addressesd reserved
# by OFFER's, DECLINE's, and ARP conficts

#max_leases 254 #default: 254

# If remaining is true (default), udhcpd will store the time
# remaining for each lease in the udhcpd leases file. This is
# for embedded systems that cannot keep time between reboots.
# If you set remaining to no, the absolute time that the lease
# expires at will be stored in the dhcpd.leases file.

#remaining yes #default: yes

# The time period at which udhcpd will write out a dhcpd.leases
# file. If this is 0, udhcpd will never automatically write a
# lease file. (specified in seconds)

#auto_time 7200 #default: 7200 (2 hours)

# The amount of time that an IP will be reserved (leased) for if a
# DHCP decline message is received (seconds).

#decline_time 3600 #default: 3600 (1 hour)

# The amount of time that an IP will be reserved (leased) for if an
# ARP conflct occurs. (seconds

#conflict_time 3600 #default: 3600 (1 hour)

# How long an offered address is reserved (leased) in seconds

#offer_time 60 #default: 60 (1 minute)

# If a lease to be given is below this value, the full lease time is
# instead used (seconds).

#min_lease 60 #defult: 60

# The location of the leases file

#lease_file /var/lib/misc/udhcpd.leases #defualt: /var/lib/misc/udhcpd.
leases

# The location of the pid file
#pidfile /var/run/udhcpd.pid #default: /var/run/udhcpd.pid

# Everytime udhcpd writes a leases file, the below script will be called.
# Useful for writing the lease file to flash every few hours.

#notify_file #default: (no script)

#notify_file dumpleases # <--- usefull for debugging

# The following are bootp specific options, setable by udhcpd.

#siaddr 192.168.0.22 #default: 0.0.0.0

#sname zorak #default: (none)

#boot_file /var/nfs_root #default: (none)

# The remainer of options are DHCP options and can be specifed with the
# keyword 'opt' or 'option'. If an option can take multiple items, such
# as the dns option, they can be listed on the same line, or multiple
# lines. The only option with a default is 'lease'.

#Examles
opt dns 192.168.0.202 <your APN's DNS server>
option subnet 255.255.255.0
opt router 192.168.0.202
opt wins 192.168.0.202
#option dns 129.219.13.81 # appened to above DNS servers for a total of 3
option domain local
option lease 864000 # 10 days of seconds

# Currently supported options, for more info, see options.c
#subnet
#timezone
#router
#timesvr
#namesvr
#dns
#logsvr
#cookiesvr
#lprsvr
#bootsize
#domain
#swapsvr
#rootpath
#ipttl
#mtu
#broadcast
#wins
#lease
#ntpsrv
#tftp
#bootfile
</pre>

Notice that I set the start and end of the IP lease block to 192.168.0.200. If you follow the instructions at [[USB Networking]], this is the address that it assumes the host to be and the /etc/resolv.conf file points to this address to allow name resolution from your phone.

The interface in this case is usb0. This will have to be set differently if you are using Bluetooth.

The dns is set to the FreeRunner's address, as well as my network operator's DNS server address. You don't have to use your network operator's DNS address if you can find a caching nameserver for the FreeRunner.

The router is set to the FreeRunner.

== Turning your FreeRunner into a Network Address Translation (NAT) gateway ==

I set up my FreeRunner so that it acts as a NAT gateway so that all traffic that goes to my network operator appears to originate from the phone. I installed iptables to accomplish this:

opkg install iptables iptables-utils kernel-module-ipt-masquerade kernel-module-iptable-nat

Once that is installed, I have the following script named firewall.sh that I use to set up the NAT once connected to the GPRS network:

<pre>
#!/bin/sh
IPTABLES='/usr/sbin/iptables'

# Set interface values
EXTIF='ppp0'
INTIF='usb0'

# enable ip forwarding in the kernel
/bin/echo 1 > /proc/sys/net/ipv4/ip_forward

# flush rules and delete chains
$IPTABLES -F
$IPTABLES -X

#Enable masquerading to allow LAN internet access
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE

#Forward LAN traffic from LAN $INTIF to Internet $EXTIF
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -m state --state NEW,ESTABLISHED -j ACCEPT

#Allowing access to the SSH server"
#$IPTABLES -A INPUT --protocol tcp --dport 22 -j ACCEPT

#Allowing access to the HTTP server"
#$IPTABLES -A INPUT --protocol tcp --dport 80 -j ACCEPT

# block out all other Internet access on $EXTIF
$IPTABLES -A INPUT -i $EXTIF -m state --state NEW,INVALID -j DROP
$IPTABLES -A FORWARD -i $EXTIF -m state --state NEW,INVALID -j DROP
</pre>

so once connected through GPRS, I run:

./firewall.sh

and then you should be able to connect to the internet from your computer!

== See also ==
* [[pppd]]
* [[Manually using GSM]]
* [[Manually using Bluetooth]]
* [[GPRS FSO]]
{{Languages|Manually_using_GPRS}}

[[Category:Documentation]]
[[Category:Application Developer]]
[[Category:Guides]]
[[Category:Networking]]

Manually using GPRS

2008-08-24T23:24:34Z

Ott--: /* Some APN names for reference */

The GPRS connection is made using the PPP protocol to a server identified by an "APN" at the network operator. Once a GPRS connection is made, it is possible to [[#Sharing_the_GPRS_connection_with_a_computer|share that connection with a connected computer]], allowing that computer to access the internet through the phone!

= Option 1: With GSM multiplexing and with a GUI =

{{note|The following does not appear to work if you have a SIM PIN. The dialog to enter your SIM PIN never pops up and the GSM multiplexing daemon continuous loops and runs into a SIM PIN error.}}

GSM multiplexing allows both a GPRS connection and a phone call to be handled at the same time. By default, [[Om 2008.8]] does not multiplex the GSM device. The [[FSO]] distribution, however, introduces GSM multiplexing with a new service and a DBus API to that service. The instructions to modify the OM2008.8 distribution to make use of GSM multiplexing and allow you to start GPRS from a GUI can be found here: http://freeyourphone.de/portal_v1/viewtopic.php?f=21&t=295

However, using those instructions, you will encounter a few hurdles. Do not use the gsm0710muxd that is found in the OM2008.8 repository. It will not work, instead, use the one found here:

http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/gsm0710muxd_0.9.1+gitr6fecc78198dd821bbe29efd096bd8fecd855179d-r0_armv4t.ipk

In order to install that version of gsm0710muxd, however, you will also have to install a bunch of missing dependencies. Those can be found by clicking on the dependencies found here:

http://www.angstrom-distribution.org/repo/?action=details&pnm=gsm0710muxd

Make sure that you install the armv4t versions of all packages.

The [[#Some APN names for reference|APN Reference]] table may come in handy when you are looking for the required network specific information.

Once you follow through with all the instructions, you will notice that the "Services" GUI will crash. This has to do with this bug: http://docs.openmoko.org/trac/ticket/1718

The fix is to change the "init()" call on line 82 of /usr/lib/python2.5/site-packages/gtk-2.0/gtk/_init_.py to "_init()" (add an underscore).

You may also have to modify your /etc/resolv.conf file and add the nameserver (DNS Server) of your service provider if you have DNS resolution problems.

Then, hopefully, you should be up in running with GPRS and a GUI to turn it on and off.

= Option 2: Without GSM multiplexing and without a GUI =

The program that implements PPP on Linux is [[pppd]], which we need to configure and run to get a connection. When that is working, we can configure pppd to wait until it's needed before it connects, and to disconnect if the connection becomes idle. Further, we can start pppd in the background during the boot process.

== Configuring pppd for manual connections ==

You'll need /etc/ppp/peers/gprs:
<pre>
# Uncomment the following if you want some debug.
#debug
#logfile /var/volatile/log/pppd.log
lock
/dev/ttySAC0 115200
crtscts
connect /etc/ppp/gprs-connect-chat
disconnect /etc/ppp/gprs-disconnect-chat
hide-password
usepeerdns
ipcp-accept-local
noauth
noipdefault
novj
novjccomp
defaultroute
replacedefaultroute
# Reopen the connection if it fails, pausing for a while.
persist
holdoff 15
# Check the line every 20 seconds and presume
# the peer is gone if no replay for 4 times.
lcp-echo-interval 20
lcp-echo-failure 4
</pre>

Depending on the APN, you may need password authentication using CHAP or PAP. In /etc/ppp/pap-secrets you can add the following default line for "password-less" connections:

<pre>
# client server secret IP addresses
* * "" *
</pre>

For CHAP, lines in /etc/ppp/chap-secrets are used. For PAP, the lines are in /etc/ppp/pap-secrets. The client should match the "user" option in pppd the config file (below). You can use * to mean any here, but the option user "" doesn't mean empty!

For example:

<pre>
# Secrets for authentication using CHAP
# client server secret IP addresses
"user" * "password" *
</pre>

For this you need the following options in /etc/ppp/peers/gprs:

<pre>
# username to use for authentication, should match "client" in /etc/ppp/{chap,pap}-secrets
user "user"
</pre>

== gprs-connect-chat, version 1 ==

You'll also need /etc/ppp/gprs-connect-chat (needs "chmod +x"):

<pre>
#!/bin/sh -e
exec chat -v -S -s\
TIMEOUT 15\
"" "\K\K\K\d+++ATH"\
OK-AT-OK ATZ\
OK ATE1\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 60\
OK AT+CFUN=1\
OK AT+COPS\
OK AT+CGDCONT=1,\"IP\",\"internet\"\
OK ATD*99#\
CONNECT /n/d
</pre>

(08/18/08) Note: I needed to add the command "AT+CMOD=2" (formatted as "OK AT+CMOD=2\" without the quotes) in order to get GPRS working with the above script (otherwise it would ERROR on the CFUN, COPS, or the ATD if the other two were removed). I have T-Mobile (US) with the $5.99 "tzones" addon, which works with Minimo as it supports HTTP proxy setups.

== gprs-connect-chat, version 2 ==

Update: On my freerunner the first AT+CFUN=1 always generated ERROR. I managed to get gprs work by using the following script from http://lists.openmoko.org/pipermail/community/2008-July/023246.html:

<pre>
#!/bin/sh -e
exec /usr/sbin/chat -v \
TIMEOUT 10 \
OK-AT-'' ''\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 30 \
'' ATZ\
OK ATE1\
OK AT+CFUN=1\
ERROR AT+CPIN=\"XXXX\"\ << USE YOUR OWN
OK AT+COPS\
OK AT+CGDCONT=1,\"IP\",\"internet\"\
OK 'ATDT*99***1#'\
CONNECT ''
</pre>

The error seems to vary a bit, sometimes it's before AT+COPS, sometimes as above. I have two versions of the gprs-connect-chat, which I vary between depending on which is needed. Or is there a way to specify two acceptable answers like {OK,ERROR}?

You will need to adjust the APN name "internet" in at+cgdcont line and possibly the phone number in the ATD line to match what your network operator provides. See below in the table "Some APN names for reference" for the right settings for your operator.

== gprs-disconnect-chat ==

Also good to have is /etc/ppp/gprs-disconnect-chat (needs "chmod +x"):

<pre>
#!/bin/sh -e
/usr/sbin/chat -v\
ABORT OK\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO CARRIER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 12\
"" "\K\K\K\d+++ATH"\
"NO CARRIER-AT-OK" "\c"
</pre>

== Starting PPP connection ==

The following script can be used to start the ppp connection. First it stops gsmd because gsmd may put the phone in a unknown state. It then turns on the power to the phone, modifies the ownership, and then creates a tty connection. Finally it starts [[pppd]] with the gprs settings.

<pre>
/etc/init.d/gsmd stop
echo "1" > /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
chown uucp.uucp /dev/ttySAC0
stty -F /dev/ttySAC0 crtscts
pppd call gprs
</pre>

If you are having problems connecting ensure you have a good GSM signal and replace the last line with the below line. This will allow you to see the details of the connection on the console.

<pre>
pppd debug nodetach call gprs
</pre>

The config above will establish a persistant link over gprs. The battery will run low in less than an hour. See an example for an on-demand config below.

=== Resolve.conf issues ===

The latest build seems to have solved the following issue, it should be automatically updated by pppd.

If you expeience DNS issues after connecting to DNS you may need a proper /etc/resolv.conf:

<pre>
ln -sf /var/run/resolv.conf /etc
</pre>

If needed put your nameserver for usb-net into /var/run/resolv.conf, not in /etc.

The image does not set a correct resolv.conf. i do so with an

<pre>
echo nameserver 192.168.0.201 > /var/run/resolv.conf
</pre>

in the right place. because a post-up in /etc/network/interfaces is not supported i do that in /etc/network/if-up.d/08setupdns

another problem is pppd's /etc/ppp/ip-down.d/92removedns which does not properly remove the link when shuting down ppp. my fix is this script:

<pre>
#!/bin/sh
ACTUALCONF=/var/run/resolv.conf
PPPCONF=/var/run/ppp/resolv.conf
if [ -f $PPPCONF ] ; then
if [ -f $ACTUALCONF ] ; then
if [ ! -h $ACTUALCONF -o ! "`readlink $ACTUALCONF 2>&1`" = "$PPPCONF" ] ; then
mv $ACTUALCONF $ACTUALCONF.ppporig
fi
fi

ln -sf $PPPCONF $ACTUALCONF
fi
</pre>

=== Some APN names for reference ===

{| border="1"
! Country
! Carrier
! Plan
! APN/Phone
! user/password if required
! Working pppd scripts
|-
| Australia || Vodafone || Any || vfinternet.au || ||
|-
| Canada || Fido || Any, behind NAT || internet.fido.ca || fido/fido || mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device
org.freesmartphone.GSM.PDP.ActivateContext internet.fido.ca fido
fido
|-
| Canada || Rogers || Any, behind NAT || internet.com || wapuser1/wap || nameserver 207.181.101.4
|-
| Denmark || Telmore || || wap || must be empty ||
|-
| Estonia || Elisa || Any, behind NAT || internet || ||
|-
| Estonia || EMT || Any, behind NAT || internet.emt.ee || ||
|-
| Finland || Saunalahti || Any || internet.saunalahti || ||
|-
| Finland || Sonera || Any, behind NAT || internet || ||
|-
| Finland || Sonera || Any, public IP || prointernet || ||
|-
| France || SFR || 10.x.x.x? || websfr || || under tests
|-
| France || SFR || 10.x.x.x? || wapsfr[1]|| || under tests
|-
| France || Orange || ??? || orange.fr || || under tests
|-
| France || Bouyges Telecom || Web & Mail || mmsbouygtel.com || || Work great under FSO. Just follow instructions at http://wiki.openmoko.org/wiki/GPRS_FSO. Proxy: 62.201.129.225:8080. For emails, only ports 25 (smtp) and 110 (pop) are allowed. (They use a transparent proxy ...)
|-
| Germany || E-Plus || BASE (and others?) || internet.eplus.de || eplus gprs || [[Base pppd scripts]]
|-
| Germany || E-Plus || Simyo || internet.eplus.de || simyo simyo || [[simyo pppd scripts]]
|-
| Germany || T-Mobile || || internet.t-mobile || ||
|-
| Germany || Vodafone || Any, behind NAT || web.vodafone.de || ||
|-
| India || AirTel || MobileOffice || airtelgprs.com || ||
|-
| Italy || Wind || Superinternet, public IP || internet.wind / *99# || wind/wind (any string) || [[Wind pppd scripts]]
|-
| Netherlands || Vodafone || Any || live.vodafone.com / *99***1#|| || [[Vodafone pppd scripts]]
|-
| New Zealand || Vodafone || Any || live.vodafone.com / *99***2#|| ||
|-
| Norway || Netcom || Any || internet.netcom.no || ||
|-
| Norway || OneCall || Any || internet || ||
|-
| Norway || Telenor || Any || telenor || ||
|-
| Sweden || Parlino || || internet.parlino.se || || [[GPRS_FSO|Works with FSO]]
|-
| Switzerland || Swisscom || e.g. Natel Basic Liberty, behind NAT || gprs.swisscom.ch || ||
|-
| UK || T-Mobile|| || general.t-mobile.uk || ||
|-
| UK || Virgin || || goto.virginmobile.uk || user ||
|-
| UK || [http://www.filesaveas.com/gprs.html other providers] || || || ||
|-
| USA || AT&T || Unlimited data plan (attached to pay-as-you-go voice plan) || wap.cingular / *99***1# || WAP@CINGULARGPRS.COM/CINGULAR1 ||
|-
| USA || Cincinnati Bell Wireless || || wap.gocbw.com || cbw ||
|-
| USA || Cingular (AT&T) || Less than full internet || wap.cingular / may require *99***1# || ||
|-
| USA || T-mobile || Anything less than full internet || wap.voicestream.com || || Need to set proxy to 216.155.165.50 T-Mobile docs say "216.155.165.050". 050 octal = 40 decimal and will *not* work. I think port is 8080 or 9100. No luck w/ pppd scripts. GPRS_FSO directions work under FSO though.
|-
| USA || T-mobile || Regular internet plan || internet2.voicestream.com || || [[T-Mobile pppd scripts]]
|-
| USA || T-mobile || "VPN" internet plan || internet3.voicestream.com || ||
|-
| Venezuela || Digitel || Pre- y post-pago || gprsweb.digitel.ve || ||
|-
|}

[1] connected through a WAP proxy (slower, but the only way to access Vodafone live! and SFR portal)

[2] Unless stated otherwise the phone number to call is "*99#"

Also see Ross Barkman's page for a detailed list of more [http://www.taniwha.org.uk/gprs.html global GPRS providers APN details]

== Starting pppd automatically ==

Once you have finished debugging your gprs-connect-chat and gprs options files, you may wish to automatically connect whenever needed and hang up when finished. Make sure you understand the impact of this change to your carrier plan billing. This is not recommended unless you have a large-use or unlimited data plan. These scripts do NOT prompt you before connecting.

=== On-demand connection settings ===

Additional settings are needed if you want the actual connection to be up only while there is traffic. In the 'gprs' file above, insert the following, making sure 'nodetach' is commented out. If 'nodetach' is on, the boot process will stop when it starts pppd. Also remove the option 'persist' mentioned above.

<pre>

# Wait until needed before connecting
demand

# Disconnect if idle for given amount of seconds
idle 20

</pre>

=== Start on boot (method 1) ===

Add the following definition to /etc/network/interfaces:
<pre>
auto ppp0
iface ppp0 inet ppp
provider gprs
</pre>

That should be it. Now you can use 'ifup ppp0' and 'ifdown ppp0' manually too.

=== Start on boot (method 2) ===

Create the following file as /etc/ppp/ppp_on_boot (needs chmod +x). The /etc/init.d/ppp script will call it to set up the daemon.
<pre>
#!/bin/sh
#
# Rename this file to ppp_on_boot and pppd will be fired up as
# soon as the system comes up, connecting to `provider'.
#
# If you also make this file executable, and replace the first line
# with just "#!/bin/sh", the commands below will be executed instead.
#

# The location of the ppp daemon itself (shouldn't need to be changed)
PPPD=/usr/sbin/pppd

# The default provider to connect to
$PPPD call gprs

# Additional connections, which would just use settings from
# /etc/ppp/options.<tty>
#$PPPD ttyS0
#$PPPD ttyS1
#$PPPD ttyS2
#$PPPD ttyS3
</pre>

Finally, you need to add the /etc/init.d/ppp script to the init process by creating symbolic links from the appropriate directories. I chose the following:

<pre>
/etc/rc0.d/K25ppp
/etc/rc1.d/K45ppp
/etc/rc2.d/S45ppp
/etc/rc3.d/S45ppp
/etc/rc4.d/S45ppp
/etc/rc5.d/S45ppp
/etc/rc6.d/K25ppp
</pre>

= Sharing the GPRS connection with a computer =

Once you successfully connect to your network operator, you can start sharing your data plan with your computer through USB or Bluetooth networking. The following describes how you can do so through USB networking.

== Setting up your computer's network settings ==

I find it useful to have my computer automatically acquire it's network address, mask, gateway, and DNS servers from the FreeRunner instead of manually setting these up. In order to this, I installed busybox-udhcpd from the Angstrom repositories (see [[Repositories]])

opkg install busybox-udhcpd

Once it is installed, it needs to be configured. Edit the /etc/udhcpd.conf file. Mine looks like this:

<pre>
# Sample udhcpd configuration file (/etc/udhcpd.conf)

# The start and end of the IP lease block

start 192.168.0.200 #default: 192.168.0.20
end 192.168.0.200 #default: 192.168.0.254

# The interface that udhcpd will use

interface usb0 #default: eth0

# The maximim number of leases (includes addressesd reserved
# by OFFER's, DECLINE's, and ARP conficts

#max_leases 254 #default: 254

# If remaining is true (default), udhcpd will store the time
# remaining for each lease in the udhcpd leases file. This is
# for embedded systems that cannot keep time between reboots.
# If you set remaining to no, the absolute time that the lease
# expires at will be stored in the dhcpd.leases file.

#remaining yes #default: yes

# The time period at which udhcpd will write out a dhcpd.leases
# file. If this is 0, udhcpd will never automatically write a
# lease file. (specified in seconds)

#auto_time 7200 #default: 7200 (2 hours)

# The amount of time that an IP will be reserved (leased) for if a
# DHCP decline message is received (seconds).

#decline_time 3600 #default: 3600 (1 hour)

# The amount of time that an IP will be reserved (leased) for if an
# ARP conflct occurs. (seconds

#conflict_time 3600 #default: 3600 (1 hour)

# How long an offered address is reserved (leased) in seconds

#offer_time 60 #default: 60 (1 minute)

# If a lease to be given is below this value, the full lease time is
# instead used (seconds).

#min_lease 60 #defult: 60

# The location of the leases file

#lease_file /var/lib/misc/udhcpd.leases #defualt: /var/lib/misc/udhcpd.
leases

# The location of the pid file
#pidfile /var/run/udhcpd.pid #default: /var/run/udhcpd.pid

# Everytime udhcpd writes a leases file, the below script will be called.
# Useful for writing the lease file to flash every few hours.

#notify_file #default: (no script)

#notify_file dumpleases # <--- usefull for debugging

# The following are bootp specific options, setable by udhcpd.

#siaddr 192.168.0.22 #default: 0.0.0.0

#sname zorak #default: (none)

#boot_file /var/nfs_root #default: (none)

# The remainer of options are DHCP options and can be specifed with the
# keyword 'opt' or 'option'. If an option can take multiple items, such
# as the dns option, they can be listed on the same line, or multiple
# lines. The only option with a default is 'lease'.

#Examles
opt dns 192.168.0.202 <your APN's DNS server>
option subnet 255.255.255.0
opt router 192.168.0.202
opt wins 192.168.0.202
#option dns 129.219.13.81 # appened to above DNS servers for a total of 3
option domain local
option lease 864000 # 10 days of seconds

# Currently supported options, for more info, see options.c
#subnet
#timezone
#router
#timesvr
#namesvr
#dns
#logsvr
#cookiesvr
#lprsvr
#bootsize
#domain
#swapsvr
#rootpath
#ipttl
#mtu
#broadcast
#wins
#lease
#ntpsrv
#tftp
#bootfile
</pre>

Notice that I set the start and end of the IP lease block to 192.168.0.200. If you follow the instructions at [[USB Networking]], this is the address that it assumes the host to be and the /etc/resolv.conf file points to this address to allow name resolution from your phone.

The interface in this case is usb0. This will have to be set differently if you are using Bluetooth.

The dns is set to the FreeRunner's address, as well as my network operator's DNS server address. You don't have to use your network operator's DNS address if you can find a caching nameserver for the FreeRunner.

The router is set to the FreeRunner.

== Turning your FreeRunner into a Network Address Translation (NAT) gateway ==

I set up my FreeRunner so that it acts as a NAT gateway so that all traffic that goes to my network operator appears to originate from the phone. I installed iptables to accomplish this:

opkg install iptables iptables-utils kernel-module-ipt-masquerade kernel-module-iptable-nat

Once that is installed, I have the following script named firewall.sh that I use to set up the NAT once connected to the GPRS network:

<pre>
#!/bin/sh
IPTABLES='/usr/sbin/iptables'

# Set interface values
EXTIF='ppp0'
INTIF='usb0'

# enable ip forwarding in the kernel
/bin/echo 1 > /proc/sys/net/ipv4/ip_forward

# flush rules and delete chains
$IPTABLES -F
$IPTABLES -X

#Enable masquerading to allow LAN internet access
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE

#Forward LAN traffic from LAN $INTIF to Internet $EXTIF
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -m state --state NEW,ESTABLISHED -j ACCEPT

#Allowing access to the SSH server"
#$IPTABLES -A INPUT --protocol tcp --dport 22 -j ACCEPT

#Allowing access to the HTTP server"
#$IPTABLES -A INPUT --protocol tcp --dport 80 -j ACCEPT

# block out all other Internet access on $EXTIF
$IPTABLES -A INPUT -i $EXTIF -m state --state NEW,INVALID -j DROP
$IPTABLES -A FORWARD -i $EXTIF -m state --state NEW,INVALID -j DROP
</pre>

so once connected through GPRS, I run:

./firewall.sh

and then you should be able to connect to the internet from your computer!

== See also ==
* [[pppd]]
* [[Manually using GSM]]
* [[Manually using Bluetooth]]
* [[GPRS FSO]]
{{Languages|Manually_using_GPRS}}

[[Category:Documentation]]
[[Category:Application Developer]]
[[Category:Guides]]
[[Category:Networking]]

Neo FreeRunner Battery

2008-08-24T21:54:00Z

Ott--: /* Notes about expected battery life */

{{Neo FreeRunner Menu}}
=== GTA02 1200 mAh Smart Battery ===

*Using SANYO 1200mAh cell
*Battery Technical information: [http://people.openmoko.org/tony_tu/GTA02/hardware/GTA02/CT-GTA02.pdf Detailed Battery Information]

* 1200mAh Smart Battery with Coulomb-counter and protection circuit
* The Smart Battery keeps track of maximum and current capacity for precise prediction of remaining battery power and time until shutdown, based on actual power dissipation.

For more information, see the GTA01 battery info at [[Neo1973 Battery]]

=== Notes about expected battery life ===
Battery life is a work in progress. The power saving software is in a very rudimentary state. At the moment 12h is about the most (note though a [http://lists.openmoko.org/pipermail/community/2008-July/020339.html recent result of at least 21h], mostly in suspend, with multiple short wakeups, on the predecessor device GTA01). A week standby and 6 hours talk, 20 hours mp3 might be attainable when power saving software is complete.

Make sure that the battery never discharges completely. This is an issue because
the internal charging circuitry can not be turned on until the FreeRunner has
booted, and booting through USB power alone does not work.
(If you have the newest kernel images, you should be safe due to a software fix.)
Should the battery become completely discharged, your options are:
* Use external stand-alone charger (compatible with the Nokia BL-5C battery)
* Boot the FreeRunner with an alternative battery, or with a spare GTA01 or GTA02 battery, plug USB power, then switch to the empty battery.
* Boot the FreeRunner with a 4.5VDC external power source (steady hand and great care involved), plug USB power, then insert the empty battery.
* Charge the battery directly, [http://wiki.openmoko.org/wiki/Charging_battery_directly see here], how I did that.

=== Compatible Replacement Batteries ===

Other known FreeRunner-compatible batteries include the BL-series (BL-4X, BL-5X) from Nokia, and their third-party equivalents.
These may not work to revive a device and may not report charge information.
It is probably a good idea to check that your battery is not greater than the stock battery's voltage of 3.7V (the above suggests that 4.5VDC should be fine) unless you know what you are doing.

{| border="1" cellpadding="4" cellspacing="0"
!Battery Model
!Capacity (mAh)
!Charge info reported
!Notes
|-
|NOKIA BL-4
|
|no
|
|-
|NOKIA BL-4C
|750
|
|
|-
|NOKIA BL-5B
|760/890
|
|
|-
|NOKIA BL-5C
|950
|no
|
|-
|NOKIA BL-6C
|1200
|no
|
|}

== USB charger ==
{{main|USB charger}}

[[Category:Neo FreeRunner Hardware]]

File:Charging-directly-3.jpg

2008-08-24T21:47:14Z

Ott--:

File:Charging-directly-2.jpg

2008-08-24T21:46:29Z

Ott--:

2008-07-01T14:01:14Z

Ott--: New page: Name: '''Joachim Ott''' E-Mail: '''jo at berlin dot de'''

Name: '''Joachim Ott''' 
E-Mail: '''jo at berlin dot de'''

Openmoko Local Groups: Berlin

2008-07-01T13:49:23Z

Ott--:

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

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

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

=== Meetings, Events ===
Meeting language is German ;-)
{|border=1
!Date
!Location
!Topic
!Who
|-
|8.-12. August 2007
|Flugplatz Finowfurt
|[https://events.ccc.de/camp/2007/Intro/ Chaos Communication Camp 2007] und [http://events.ccc.de/camp/2007/GSM_Village GSM Village]
|?
|-
|23.08.2007 / 18:00
|[https://berlin.ccc.de/wiki/CCC_Berlin CCCB] / [https://berlin.ccc.de/wiki/Club_Discordia Club Diskordia]
|First meeting. bring your hardware
|Roh, pH5, [[User:Minime|tim]](+ 2?), ? (please add yourself)
|-
|no definite date yet - please use [[Talk:OpenMoko_Local_Groups:_Berlin|discussion]]
|no location yet - please use [[Talk:OpenMoko_Local_Groups:_Berlin|discussion]]
|First GTA01Bv4 impressions for P1 owners and those who have no Neo yet. Giving each other a helping hand getting started.
|[[User:Minime|tim]], ...
|}

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