Openmoko - User contributions [en]

Navit

2009-05-08T15:20:34Z

Relet: /* News */ some correct settings for SHR

{{Application|Navit}}

As described on the [http://navit.sourceforge.net/ Navit home page],

"Navit is a car navigation system with routing engine.

Its modular design is capable of using vector maps of various formats for routing and rendering of the displayed map. It's even possible to use multiple maps at a time.

The GTK+ or SDL user interfaces are designed to work well with touch screen displays. Points of Interest of various formats are displayed on the map.

The current vehicle position is either read from gpsd or directly from NMEA GPS sensors."

Some people say Navit is also a good choice for pedestrian and bicycle navigation.

[[Image:Navit-2241.png|thumb|Navit-r2241]]

== Acknowledgment ==

Thanks to [[User:Alessandro | Alessandro]], stefan_schmidt, cp15 and all Navit developers I have done a small ("not really working") preview of Navit on Neo1973 at [http://www.telemobilityforum.com/eng/ Telemobility Forum 2007]. Thanks to [http://gfoss.it GFoss] guys to invite me.
''[[User:Tyrael | Tyrael]]''

==Setting up Navit==

===Install Navit===
====OM2008.x====
You can now simply add a feed from there : http://download.navit-project.org/navit/openmoko/svn/

Essentially, to enable this directory as [[Om_2008.8_Installer#How to add a Repository ?|feed]] and install or update navit do:
* Only for the first time:
echo src navit http://download.navit-project.org/navit/openmoko/svn >/etc/opkg/navit-feed.conf
opkg update

* Always:
opkg install navit

Navit will be auto-updated when you run opkg upgrade later
====Debian====
Navit is now in [http://packages.debian.org/source/experimental/navit Debian experimental].

More recent releases of the very same packaging can be found in the Pini's repository:
deb http://pini.free.fr/debian unstable main
deb-src http://pini.free.fr/debian unstable main

The up-to-date source package is available through git at '''git://git.debian.org/git/collab-maint/navit.git''' ([http://git.debian.org/?p=collab-maint/navit.git;a=summary browse]).

====FSO====
I found that navit did not start fso-gpsd. I found the solution on the [http://lists.openmoko.org/nabble.html#nabble-td2473189 mailing list]. Starting navit from the command line produced the following output:

navit:plugin_load:can't load '/usr/lib/navit/vehicle/
libvehicle_gpsd.so', Error 'libgps.so.16: cannot open shared object
file: No such file or directory'
navit:vehicle_new:invalid type 'gpsd'

So I used the following workaround:

opkg install libgps17
ln -s /usr/lib/libgps.so.17 /usr/lib/libgps.so.16

===Set up the maps you want===

====The Easy Way====
Use [http://maps.navit-project.org/download/ Navit pre-processed OSM maps]. Navigate to the region you want, and click select to select it, select the region you want, then click download

If you just want the entire planet (as of this writing, ~1.8 GB), it's [http://maps.navit-project.org/planet.bin here].

[http://downloads.cloudmade.com/ CloudMade] also has up-to-date maps from OpenStreetMap by country (by state in the US).

====From the command line====
'''OpenStreetMap''' - follow directions at http://wiki.navit-project.org/index.php/OpenStreetMaps
* There are some pre-processed, up-to-date maps that can be grabbed with wget:

<pre>wget -O germany.bin http://maps.navit-project.org/api/map/?bbox=5.185546875,46.845703125,15.46875,55.634765625</pre>

* Here's an example to get the maps for the area around Seattle, WA:
** Find the map coordinates using http://informationfreeway.org/?lat=47.520270037501454&lon=-122.20130713167327&zoom=9&layers=B000F000
** Download 4 regions from OpenStreetMaps ([[Navit#Script_to_download_OSM_maps|see below]] for a script to do this for you automatically for largish areas):

<pre>wget -O map1.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.2,47.5,-122,47.7
wget -O map2.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.4,47.5,-122.2,47.7
wget -O map3.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.4,47.3,-122.2,47.5
wget -O map4.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.2,47.3,-122,47.5</pre>

* A binary Navit map file needs to be created. The following uses osm2navit, and it's recommended that this command be used on something more powerful than the Neo:

<pre>cat *.osm | osm2navit --dedupe-ways mymap.bin</pre>

===Copy the map to the NEO===
To copy the map using scp (replace ''/directory'' as is appropriate in the following):
<pre>scp mymap.bin root@neo:/directory</pre>
Once it's somewhere on the NEO, Navit needs to know that it's there.
<pre>mkdir ~/.navit
cp /usr/share/navit/navit.xml ~/.navit/navit.xml
vi ~/.navit/navit.xml</pre>
In the navit.xml file, put the following into a new <mapset> section:
<pre><map type="binfile" enabled="yes" data="/directory" /></pre>

* Run navit
** Start gllin (for GTA01)
** Start gpsd ( gpsd /tmp/nmeaNP )
** Start navit

* The version of osm2navit with which you build the maps should match the version of navit you have. If in doubt, build the maps on the Openmoko.

===Tips and Tricks===
====Center on Vehicle====
Navit supports a "always center on vehicle" option.

To activate this add
follow="3"
to the vehicle tag in navit.xml. The "3" causes to give the gui time to do something between the repaints (drag the map or browse the menu). When its set to "1" navit does nothing more than repainting the map continuously.

== News ==

=== Getting the display right ===

If using SHR the keyboard in country/town/street search mode does not fit on the street, make sure your gui configuration is set to the following line:

<gui type="internal" font_size="350"/>

The example line provided for freerunners hides some important icons. Namely, instead of typing your city name first, you will first have to click the button on the top left, to go into country search mode. Enter your country name, then the city name, in order to enable the search function. This requires your map data to be searchable.

=== Street names ===
They are now displayed on Openmoko using the CVS version of Navit (20071217).

=== Point selection by pen ===
Easier using the CVS version (20071217).

=== Route > Destination ===
The Route > Destination menu item crashes the software (20071217 and 0.04, but fixed in 0.1.0+svnrev1255).

A workaround is to set the LANG variable before calling navit. For example:

LANG=fr_FR.UTF-8 navit

Note that a short syntax (e.g. LANG=fr) would not work.

If you put an "export LANG=fr_FR.UTF-8" into your /etc/profile file, it will automatically set this environment variable every time you boot up. This way, you can launch Navit from the Icon in Illume.

http://trac.navit-project.org/ticket/51

=== Speech ===
Navit can speak if you install eSpeak + speech-dispatcher and updates your navit.xml file.

For adventurous people, one way to do this:

* mokoTTS aims to integrate these packages in OM:
http://projects.openmoko.org/projects/mokotts/

install espeak, dotconf, and then speech-dispatcher.
note: running 2008.8 updating from zecke's "testing" repo does not require "dotconf"

* change the speech tag in navit.xml:
<speech type="cmdline" data="spd-say '%s'" />

or "spd-say -l fr '%s'" for using the French voice for example.

'''Note: Package speech-dispatcher broke my audio after suspend with current SHR (2009-04-13, though the problem's not shr, but speech-dispatcher itself).''' A solution is to disable starting of speech-dispatcher with:
update-rc.d -f speech-dispatcher remove
And then edit /usr/bin/navit, so that it starts speech-dispatcher before navit, and stops it afterwards. See http://lists.openmoko.org/nabble.html#nabble-td1088795

=== Maps ===
==== Downloadable Maps ====
Downloadable OSM maps for most areas of the world are available free in Navit format from Cloudmade at [http://downloads.cloudmade.com/ http://downloads.cloudmade.com/]. Simply navigate to the country or region you want and download the <code>.navit.bin.zip</code> version of the map. You'll have to exatract the <code>.bin</code> file from the ZIP archive before using it with Navit.
==== Planet extract ====
You can download pre-compiled (ready-to-use) maps using the OpenStreetMap-data from the [http://maps.navit-project.org/download/ the navit planet extractor] ;-)]™ which allows you to select a region of OpenStreetMap to extract. This will give you a binary file that can be used directly by Navit without further processing. The planet extractor's map data is updated daily.

==== Script to download OSM maps ====
[[User:Wurp|Wurp]] wrote a little python script to download all OSM maps within a lat/long rectangle. Just copy the script to a file called dlOSM.sh, chmod +x it, and run it like
dlOSM.sh <minimum latitude> <maximum latitude> <minimum longitude> <maximum longitude>

It takes a long time for large maps. I could optimize it some by having it try to get a big section at once, then if it fails, break it into smaller pieces and recurse. I'm not sure when/if I'll get around to that...

dlOSM.sh:
<pre>
#!/usr/bin/python

import os
import sys
#import math

def doIt(cmd):
os.system(cmd)

def getOsms(basename, minLat, maxLat, minLon, maxLon):
'''basename - base name of map, maps are named {basename}{count}.osm
minLat - latitude of the west side of the map
maxLat - latitude of the east side of the map
minLon - longitude of the north side of the map
maxLon - longitude of the south side of the map'''

wgetCmdTemplate = 'wget -O %s%s.osm http://api.openstreetmap.org/api/0.5/map?bbox=%s,%s,%s,%s'

currLat = minLat
mapCount = 0
while currLat < maxLat:
nextLat = min(currLat + 0.1, maxLat)

currLon = minLon
while currLon < maxLon:
nextLon = min(currLon + 0.1, maxLon)

doIt(wgetCmdTemplate % (basename, mapCount, currLon, currLat, nextLon, nextLat))

currLon = nextLon
mapCount = mapCount + 1

currLat = nextLat

(minLat, maxLat, minLon, maxLon) = map(float, sys.argv[1:])
getOsms('map', minLat, maxLat, minLon, maxLon)
</pre>

<onlyinclude>
{{ApplicationBox|
Name=[[Navit]]|
Description=Navit is a car navigation system with routing engine.|
Screenshot=Screenshot-3.png|
Homepage=http://navit.sourceforge.net|
TestedOn=|
PackageName=
}}
</onlyinclude>

[[Category:GPS Applications]]

TangoGPS

2008-11-02T22:14:04Z

Relet: /* Using Google Maps with tangoGPS */ -comment

{{Languages|tangoGPS}}
{{Application|tangoGPS}}

__TOC__

tangoGPS is a map application which can utilize Neo's built-in GPS to show your current location.

[[Image:TangoGPS1.jpg]]

Website: http://www.tangogps.org

== Running tangoGPS on [[Om 2008.8]] ==

From the freerunner connected to the internet:

opkg install gpsd
{{note|I experienced hangups if gpsd was not installed.}}
opkg install http://www.tangogps.org/downloads/tangogps_0.9.3-r1_armv4t.ipk

If opkg complains about not being able to acquire a lock, try:

pkill packagekit

To get gpsd working on the FreeRunner you have to change the configuration according to [[Gpsd#GPS_on_GTA02]].
Then start gpsd by:

/etc/init.d/gpsd start

If you get an error about no GPS device in /etc/default/gpsd execute:

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

Now you must power up the GPS-chip by opening the "Settings" application and setting the GPS entry to "on". Now you can run tangoGPS and wait until it get's a GPS fix. This can take up to a few minutes.

== Running tangoGPS on [[debian]] ==

tangogps is a very nice GPS mapping application. The latest version is available in [[Debian]].

It depends on gpsd which conflicts with frameworkd in fso-frameworkd, but there is a package available that provides
the gpsd interface to clients while using the services of the FSO frameworkd daemon, fso-gpsd. To install tangogps run

# apt-get install fso-gpsd tangogps

To turn the gps on, you have two options.
You can start the gps application in [[Zhone]], this will turn on the gps device for you or you can manually turn
on the gps device using
# echo 1 >/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron

Now you should be able to start tangoGPS from the X-mouse start menu (must have XFCE installed) :
Start > other > GPS & Map

'''Issues:'''
* Both gpsd and the framework publish GPS data through dbus, though with different interfaces. This suggests a number of possible solutions.
** gpsd or the framework could implement the other's interface (along with their own).
** a translator could read one interface and emulate the other. This is what fso-gpsd does.
** the framework could have an option to read data from gpsd.
** ogpsd/gypsy could be extended to be backwards compatible with the majority of gps applications.

== Running tangoGPS on FSO Milestone 3 ([[OpenmokoFramework]]) ==

There are two various GPS interfaces -- (1) one provided with default gpsd and (2) the other provided by ogpsd (part of the frameworkd). tangoGPS requires the ad 1 and it obtains information from gps from the dbus interface provided by gpsd.

On FSO milestone 3, there is tangoGPS pre-installed as well as both gpsd and ogpsd (see <code>/etc/frameworkd.conf</code>, section <code>ogpsd</code>). As mentioned above, there also exists a fso-gpsd package, that converts from ad 2 to ad 1 (unfortunately fso-gpsd is not in default image and must be installed with <code>opkg install fso-gpsd</code>).

You cannot have both "providers" (ad 1 & ad 2) running, but you can have ad 2 (recommended for FSO) and "convertor" (fso-gpsd) providing the ad 1. To get usable tangoGPS on FreeRunner, one has to:

# check that <code>/etc/frameworkd.conf</code>, section <code>ogpsd</code> reads GPS data from the right device (<code>/dev/ttySAC1</code>)
# if changes were made to configuration, one should restart the frameworkd -- <code>/etc/init.d/frameworkd stop && /etc/init.d/frameworkd start</code>
# check that gpsd is not running -- <code>/etc/init.d/gpsd stop</code>
# check that fso-gpsd is installed and running -- <code>opkg install fso-gpsd; fso-gpsd</code>
# check that gps chip is online (<code>echo 1 > /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron</code>)
# finally start up the tangoGPS and locate the gps signal; it should be up in a few minutes.

Note 1: handy application for testing the gps (and gps signal strength) is <code>openmoko-agpsui</code>, see general gps info at [[Gps]]

Note 2: You can automate the process -- (1) remove the startup script for gpsd (<code>update-rc.d -f gpsd remove</code>) and (2) create a simple startup scipt for fso-gpsd (you can use current script for gpsd as a skeleton)

== Downloading Maps for offline use ==

tangoGPS can bunch-download the map images so you don't need an internet connection while walking around. By default tangoGPS stores downloaded maps to /tmp/. This folder is lost every time you reboo the device. But you can use the "Config" tab within tangoGPS to change the "Cache Dir" location to , for example, /osm/ . So downloaded maps will be kept in the Neos flash, also after reboot. Note that the map files can take up large amounts of space, so you may want to store them on your sd card, in /media/card/osm.

If you find that TangoGPS does not remember configuration changes that you make to it, be sure to run it from the touchscreen, and not an SSH session. TangoGPS uses gconf to store its settings, and cannot access gconf when run via SSH.

Once you have set the location to a non-volatile path, you can connect your Neo to the internet by USB or WiFi at home and start downloading the maps of your area. Tap the map screen and select "map download". Now on-the-road tangoGPS will be able to show you maps in different zoom levels even though you are not connected to the internet.

== Downloading Maps via GPRS ==
I think tangoGPS may have started working after I followed the instructions to get GPRS working with GSM multiplexing here: [[Manually_using_GPRS#Option_1:_With_GSM_multiplexing_and_with_a_GUI]]

There are steps included in those instructions to improve GPS performance. The great thing is that once you get GPRS working, you can roam with TangoGPS running and have it download maps as needed over the GPRS connection!

== Using tangoGPS to create tracks for OpenStreetMap.org ==

tangoGPS works fine to create track for Openstreetmap. However, it records and stores a track in its native format, use [http://www.tangogps.org/downloads/convert2gpx.pl convert2gpx.pl] (see also: [http://psung.blogspot.com/2008/07/sharing-gps-tracks-from-tangogps-on.html tools]) to convert the track to GPX (i.e to import into JOSM):

perl convert2gpx.pl 20080903_111508.log > 20080903_111508.gpx

=== tangoGPS logging format ===

<lat>,<lon>,<elevation>,<speed>,<course>,<hdop>,<datetime>

== Importing Tracks into tangoGPS ==

tangoGPS does not support the import of tracks. You may help yourself by using [http://relet.net/frog/archives/68 this tool] to import GPX trackpoints as a series of POIs directly into the sqlite database which tangoGPS uses to store POIs.

== Using Google Maps with tangoGPS ==

Go to Config and create a new repository.
Set the url to
'''
<nowiki>http://mt.google.com/mt?&x=%d&y=%d&zoom=%d</nowiki> '''
for street-maps or
'''
<nowiki>http://khm.google.com/kh?&x=%d&y=%d&zoom=%d</nowiki> '''
for satellit-maps.
'''
<nowiki>http://mt.google.com/mt?v=app.81&x=%d&y=%d&zoom=%d</nowiki> '''
for topographic-maps.

Check the "Inverted Zoom" box. Press save Repository Configuration and you're ready to go.

<onlyinclude>
{{ApplicationBox|
Name=[[TangoGPS]]|
Description= TangoGPS is a map application which can utilize Neo's built-in GPS to show your current location. It automatically downloads maps from http://openstreetmap.com and you can download map tiles for offline use too.|
Screenshot=TangoGPS1.jpg|
Homepage=http://www.tangogps.org|
TestedOn=Om 2008.8|
PackageName=tangogps
}}
</onlyinclude>

[[Category:GPS Applications]]

Zagg Protection Discount Number

2008-11-02T20:08:38Z

Relet: +2

'''Here a simple page to list all [http://www.zagg.com/invisibleshield/openmoko-neo-freerunner-cases-screen-protectors-covers-skins-shields.php zagg protection] discount codes (20%).'''
'''You can use these numbers when buying [[InvisibleShield]] protectors'''.

'''Take a discount code from the top when buying your protector.'''
Please edit this page, remove the number you used and add "I used this code" in the "Summary:" field of the edit page. You can mention in the summary if you need to edit the page because you find a code invalid & need to take another.

'''When adding your discount code to the list please do so sorted by chronological date expiration''' (normally at the bottom).

(This list should grow quicker than it's used, please add your entries after using)

Here's the list (20%)
* <s>z5h67x (purchased on 8 September)</s>
* <s>25ckt7</s>
* <s>tg2nfr</s>
* <s>n1p2kb (purchased on 9 September)</s>
* <s>137d6h (purchased on 9 September)</s>
* <s>v9zhpr (purchased on 10 September)</s>
* <s>fbwvpx (purchased on 10 September)</s>
* <s>gcnqy2 (purchased on 25 September)</s>
* <s>5qy20k (purchased on 25 September)</s>
* <s>cd291x (purchased on 26 September)</s>
* <s>19fchx (purchased on 26 September)</s>
* <s>yj0kcp (purchased on 27 September)</s>
* <s>0nghfm (purchased on 30 September)</s>
* <s>3jsyxv (purchased on 30 September)</s>
* <s>dh73vs (purchased on 4 October)</s>
* <s>89znsh (purchased on 4 October)</s>
* <s>ksr6f8 (14 October)</s>
* <s>s9y368 (14 October)</s>
* nmwgpq (17 October)
* hj21x8 (17 October)
* 4mrh0d (18 October)
* tq9z4n (18 October)
* m03n6d (21 October)
* 12bjcr (21 October)
* nkgj92 (29 October)
* q1jrs0 (29 October)

This one can be reused, and appears to be a 15% discount.

*techound1 (end date: unknown, good as of 25 September, worked at 14 October and Oct 18th)

If your discount does not appear in the invoice, ask for it using Zagg's contact web form, and it should be given as a partial refund.

[[Category:Purchase]]

Talk:List of Audio Applications

2008-10-20T22:02:37Z

Relet: New page: Are there any audio recorders yet? Or any standard software you could use to take voice notes? -- ~~~~

Are there any audio recorders yet? Or any standard software you could use to take voice notes? -- [[User:Relet|Relet]] 22:02, 20 October 2008 (UTC)

Talk:Distributions

2008-09-15T12:41:20Z

Relet: /* Power Management */ new section

This page is very useful. Thank you for creating it.

In addition to the categories/features you have listed already, I suggest something about its status/usefulness -- like "Who would use this?" For example, FSO milestone 1 is probably "Developers only".

Also, it might be useful to have something that succinctly describes the expected target state for each distribution. For example, FSO is the "Strategic framework for Openmoko".

I know this is a Wiki and I wouldn't mind doing this myself, but I thought I'd bounce the idea out there first.

-Randy

In addition to the distros already covered, should we add a description of the Qtopia images here? From playing around w/ the images linked on [[Latest_Images]] it seems to be pretty functional.

-Sitwon

I thought the FSO stack dialer application was written in Python. If so the FSO stack does indeed have it :)
-Tig

I found here (http://wiki.openmoko.org/wiki/Qtopia) that there's external app to control gps under qtopia (qtgps). I tested it and seems to work. There aren't maps but just infos about lat/long/speed/etc.
Should we update the table?
[[User:Dareus|Dareus]]

== What about Mamona? ==

Should it be added here?

What is it?

Mamona is an alternative Linux distribution for Maemo (read Nokia Internet Tablets). Unless someone already have ported it to run on Neo's, I don't think it should be added here. [[User:Tingo|Tingo]] 22:35, 15 July 2008 (UTC)

== Towards a timeline ==

At some point a timeline will probably be useful. Here are some tools:
http://www.mediawiki.org/wiki/Extension:EasyTimeline
http://infodisiac.com/Wikipedia/EasyTimeline/Introduction.htm
[[User:MinhHaDuong|MinhHaDuong]] 13:45, 31 August 2008 (UTC)

== Power Management ==

I suggest that Power management features (support for standby, suspend, management software) should appear in the table. I'm not adding them, as I only know 2007.2, but maybe you could. -- [[User:Relet|Relet]] 12:41, 15 September 2008 (UTC)

Om 2007.2

2008-09-12T15:19:06Z

Relet: /* Updating your image */

{{Languages|Om 2007.2}}
{{OM2007.2}}
{{Distributions|Om 2007.2}}

'''Om 2007.2''' is the second version of the Openmoko distribution. Development began on 2007-07-26. [[Om 2008.8]] is the successor of this software stack.

Goals of this version are an improved set of PIM applications, improved theming that fixes a lot of the usability problems of the first generation design, more formalized UI guidelines and a number of changes in the build system. The latter should introduce more recent software by staying closer in sync with upstream org.openembedded.dev.

An official announcement was made by Sean Moss-Pultz on August 20:
* http://lists.openmoko.org/pipermail/announce/2007-August/000018.html

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

= Known Issues =

For the very latest status, see [http://docs.openmoko.org/trac/search?q=2007.2 all tickets with 2007.2] in the bug tracker.

==Missing Esc key==

With the default image you can't escape edit mode in vi due to the missing Esc key. You need to [[Switching_Keyboards|install a new on-screen keyboard]], and in order to do this you'll need to [[Getting_Started_with_your_Neo_FreeRunner#Set_up_USB-based_networking_and_update|set up USB networking]] first. You can then SSH into the FreeRunner from your computer and use the keyboard on that computer to edit files in vi.

Alternative on-screen keyboards feature an escape key.

If you are stuck in vi you can type <tt>:q</tt> or <tt>:q!</tt> to exit without saving, or <tt>ZZ</tt> to save and exit.

==Missing /, | and > keys==

These keys are missing from the 0 button. This can be fixed by editing <tt>/etc/multitap-pad/im-multipress.conf</tt>, see [[Switching_Keyboards#Fix_Default| this page]], but unfortunately you need vi, or some other editor to do so. Therefore you need to SSH in and [[Getting_Started_with_your_Neo_FreeRunner#Set_up_USB-based_networking_and_update|set up USB networking]] first.

Alternative on-screen keyboards should have these characters.

=="Signature Check Failed" errors when running `opkg update`==

The signatures are missing from the repository.

Workaround: If the Packages.gz files are downloading ok you can ignore this error.
After your first <tt>opkg upgrade</tt> you should get these signatures.

==The SSH / Dropbear connections over the USB link frequently freezes==

This happens when the phone goes to sleep after a few minutes. To unfreeze, unplug and replug the USB cable. To stop this from happening, press the Power button to get the Power menu, then choose Power Management: Disabled.

==My device is unresponsive. How do I perform a hard reset?==

For different boot methods, see [[Booting the Neo FreeRunner]].

==No GUI for controlling sound volume==

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

Workaround:
Run the terminal application or [[USB_Networking|log in via usb]], and run the [[Neo alsamixer]] application. To see all the options, including Mic2, run
:alsamixer -V all
The mixer is simpler than it looks. Use the left and right arrow keys to select "headphone" or "PCM" and use the up and down arrow keys to adjust the volume. You can also adjust your microphone volume with the "mic2" adjustment. Press ESC when finished. Then exit the terminal application or log out of the USB login.

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

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

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

To manually restore one of the state files,
:alsactl -f ''path-to-statefile'' restore

One way to increase the volume of the microphone is to do the following:
# ssh into your FreeRunner
# vi /usr/share/openmoko/scenarios/gsmhandset.state
# search for "Mic2"
# change to "value 3"
If people report not being able to hear you when you call, then setting the Mic2 value to 2 or 3 should fix that.

'''Question: I am using headphones but only the right speaker work the left don't work how can I fix this ?'''

This should be set correctly by restoring gsmheadset.state.
Pull and replug the headset jack to make sure the correct state-file is restored.
To manually control the switch between Speaker and headset:
Start alsamixer, scroll along to the right until you find "Amp Spk" and mute it (m), the sound will then come out from both channels of the
headphones and not out of the speaker.

= Installing =

If you want install this software distribution to your device, you have to follow these steps:
* Download the recent image of Om2007.2 on the [[Downloads#Openmoko_2007.2_images_.28GTK.29|Downloads]] page
* [[Flashing the Neo FreeRunner|Flash]] to your Neo FreeRunner

[[Image:Openmoko2007.2 home screen.png|thumb|right|home screen of Om 2007.2]]

==Building 2007.2==

=== Why to build ===

Before getting your feet wet, step back a moment and ask yourself why you want to build the Openmoko distribution image. Chances are you are a kernel and application developer and just want to develop on your package -- in that case building Openmoko is completely unnecessary and a waste of time. You may rather want to use the Openmoko [[Toolchain]] and build only the stuff that is interesting to you.

=== How to build ===

The MokoMakefile is now able to build Om 2007.2 images. If you use this new version of the MokoMakefile, you can ignore everything below and just continue building Om 2007.2 in the same way that you previously built images (i.e. according to [[MokoMakefile]]). Make sure you set the generation correctly at the top of the file.

Follow the [http://wiki.openembedded.net/index.php/Getting_Started getting started] steps of OpenEmbedded. It is suggested to use Bitbake 1.8.8 at least.

{{note|Instead of using '''git.openmoko.org''' (as indicated in OE GettingStarted), please make sure to use '''git.openmoko.org''' as [[MonotoneServer|monotone server]]. This ensures you have a working revision of the metadata and will render a successful build}}

Put the following in your local.conf

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "om-gta01"
DISTRO = "openmoko"

ENABLE_BINARY_LOCALE_GENERATION = "1"
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"

For multi-core machines, the following additions can be used for a speed-up (numbers should be tweaked based on the actual number of cores):

PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"

To free disk space after builds, add:

INHERIT += "rm_work"

Replace "${HOME}/oe" with the path to where your "org.openembedded.dev" folder lives. For the other entries have a look at ''conf/local.conf.sample'' about their meaning.

Run ''bitbake <package name>'' (e.g. openmoko-devel-image).

=== How to enable autorev ===

First apply the following patch to bitbake.

http://lists.linuxtogo.org/pipermail/openembedded-devel/2007-September/003035.html

Add the following line to your local.conf

require conf/distro/include/moko-autorev.inc

Then run bitbake as normal. Openmoko will now build with latest SVN checkouts.

=== Build issues ===

==== Wrong certificate ====
You may get something like this while the bitbake recipes are parsed:

Error validating server certificate for 'https://libw100.svn.sf.net:443':
- The certificate hostname does not match.
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

That is an issue in a bitbake file. One should not use the short-name for sourceforge (sf.net) when certificates are only for exact host names. Accept the certificate and everything is fine for now.

==== openmoko-libs FTBFS ====
Some applications have not been fully modified to build with the new libraries of Openmoko and still need the old-style ''openmoko-libs'' package. ''libmokogsm'' which is needed for ''openmoko-libs'' then fails to build. As a workaround you can remove the not yet ported applications that need ''openmoko-libs'' making it unneccessary itself. To do this edit ''packages/tasks/openmoko-taks.bb'' and find the following lines:

.
.
.
openmoko-terminal \
matchbox-panel-2 \
matchbox-panel-2-applets \
matchbox-applet-inputmanager \
# openmoko-appmanager \
matchbox-keyboard \
matchbox-stroke \
openmoko-keyboard \
.
.
.

Now put a hash (''#'') before ''openmoko-terminal'' and ''openmoko-keyboard''. You can verify that ''openmoko-libs'' is not needed any more by issuing ''bitbake -g openmoko-devel-image'' (= creates a dependency graph). There should be no mentioning of ''openmoko-libs'' in the file ''task-depends.dot''. '''Please note that the graphicall terminal and the virtual keyboard will be missing now.''' You can still have terminal access by following the [[USB Networking]] guide. For keyboard input in Qemu add the ''-usbdevice keyboard'' switch.

==== gtk+ fails building w/ gtkcombobox.c ====

If you get these errors:

gtkcombobox.c: In function 'gtk_combo_box_size_request':
gtkcombobox.c:1859: warning: unused variable 'font_desc'
gtkcombobox.c:1858: warning: unused variable 'metrics'
gtkcombobox.c:1857: warning: unused variable 'context'
gtkcombobox.c:1855: warning: unused variable 'arrow_size'
gtkcombobox.c:1854: warning: unused variable 'font_size'
gtkcombobox.c: In function 'gtk_combo_box_size_allocate':
gtkcombobox.c:1962: error: 'arrow_size' undeclared (first use in this function)
gtkcombobox.c:1962: error: (Each undeclared identifier is reported only once
gtkcombobox.c:1962: error: for each function it appears in.)
gtkcombobox.c:1965: error: 'font_desc' undeclared (first use in this function)
gtkcombobox.c:1966: error: 'context' undeclared (first use in this function)
gtkcombobox.c:1967: error: 'metrics' undeclared (first use in this function)
gtkcombobox.c:1969: error: 'font_size' undeclared (first use in this function)

Go to your /build/tmp/work/fic-gta01-angstrom-linux-gnueabi/gtk+-2.10.14-r3/gtk+-2.10.14/gtk directory, and patch gtkcombobox.c with the following:

Thanks to rmoravcik in #openmoko (patch was taken from http://pastebin.ca/654717 )

--- gtkcombobox.c 2007-08-12 20:30:07.000000000 +0200
+++ gtkcombobox.c 2007-08-12 20:29:58.000000000 +0200
@@ -1948,6 +1948,12 @@
gtk_combo_box_size_allocate (GtkWidget *widget,
GtkAllocation *allocation)
{
+ gint font_size;
+ gint arrow_size;
+ PangoContext *context;
+ PangoFontMetrics *metrics;
+ PangoFontDescription *font_desc;
+
GtkComboBox *combo_box = GTK_COMBO_BOX (widget);
gint focus_width, focus_pad;
GtkAllocation child;

==== Building glibc fails with a segfault in QEMU ====

If your build aborts and you see something like this:

NOTE: package glibc-2.5: started
NOTE: package glibc-2.5-r6: task do_package: started
NOTE: preparing tree for binary locale generation
NOTE: generating locale en_US (UTF-8)
qemu: uncaught target signal 11 (Segmentation fault) - exiting

...

NOTE: Tasks Summary: Attempted 271 tasks of which 0 didn't need to be rerun and 1 failed.
ERROR: '/home/moko/oe/org.openembedded.dev/packages/glibc/glibc_2.5.bb' failed

Try editing your local.conf file. Change:

ENABLE_BINARY_LOCALE_GENERATION = "1"

to

ENABLE_BINARY_LOCALE_GENERATION = "0"

and restart the build. This may have some effect on internationalization (you will see a warning indicating that), but at least the build will continue. Thanks to rwhitby for the tip.

Alternatively, as suggested by XorA in #openmoko, if you are running a 64-bit host distribution, try forcing a different QEMU rev, also in local.conf:

PREFERRED_VERSION_qemu-native = "0.9.0+cvs20070701"
SRCDATE_qemu-native = 20070701

==== libxml2-native fails with xmlCatalogPtr errors ====

Go to your build/tmp/work/i686-linux/libxml2-native-2.6.29-r1/libxml2-2.6.29/include/libxml/ directory and patch xmlversion.h with the following:

--- xmlversion.h 2007-08-17 10:45:42.000000000 +0100
+++ xmlversion.h 2007-08-17 10:51:36.000000000 +0100
@@ -219,7 +219,7 @@
*
* Whether the Catalog support is configured in
*/
-#if 0
+#if 1
#define LIBXML_CATALOG_ENABLED
#endif

On my system the libxml2-native-2.6.29-r1 directory is in a directory named i686-linux, yours may be different. I believe this patch to be a workaround to make libxml2-native build. I am not yet sure what the consequences of enabling XML catalogue support are.

== Pre-built images ==
* http://buildhost.openmoko.org/snapshots/2007.08/ (Official snapshots and ipkg repository)

=== Buildhost directory structure ===

The content of the Openmoko build server directory is available at
* http://buildhost.openmoko.org/OM2007.2/tmp/

It contains
* cache
** Internal caching data, not for human interpretation
* cross
** The cross-compilation toolchain used. You can download this and use it on your local machine.
* deploy
** deploy/images
*** The filesystem, kernel and bootloader images to be flashed into NAND
** deploy/ipk
*** the .ipk packages
* rootfs
** the extracted root filesystem. Please use the images from deploy/images instead
* staging
** no user servicable parts inside
* stamp
** internal state data
* work
** the actual build trees (including patches source code and binaries) of the individual packages

== Updating your image ==

'''REVIEW this section - buildhost is down, replaced. '''

Now that you have a functional 2007.2 image on your Neo, you will want to keep it updated. Fortunately, ipkg is already set up to pull updated packages from the openmoko buildhost.

On the phone, in the terminal (or via ssh), if you have a live internet connection and DNS resolution set up in /etc/resolv.conf:

ipkg update && ipkg upgrade

will bring your installed packages up to the most recent versions. Also have a look at alternative/additional ipkg sources at [[downloads]].

If you are also building your own images and packages, you can also run a simple httpd on your build host and serve your own ipkg files to the Neo.

On the build host, for example:

thttpd -d <path_to_moko/tmp/deploy/glibc/ipk> -p 8080

will serve your packages on port 8080.

Then, on the neo, make a new file at /etc/ipkg/local-feed.conf with these contents:

src/gz local-all http://192.168.0.200:8080/all
src/gz local-armv4t http://192.168.0.200:8080/armv4t
src/gz local-om-gta01 http://192.168.0.200:8080/om-gta01

and ipkg on the Neo (update-upgrade) will pick up files from your local build host's repository (assuming its IP address is 192.168.0.200, as is default in the [[USB Networking]] setup) in addition to the openmoko buildhost.

Or better yet, change the 192.168.0.200:8080 addresses above to the eth0 IP address of your build machine (instead of the usb0 IP address), and then you can access your local repository with your Neo plugged into any machine on your local net, or even via bluetooth.

Also if you are building your own packages or packages from the OE database that aren't part of Openmoko by default, you can install those packages as follows.

On the build host:

bitbake <name_of_package>
bitbake -crebuild package-index

Then on the Neo:

ipkg update
ipkg install <name_of_package>

The new package might not show up in the program menu until you reboot or restart X.

==FAQ==
=== Q: What are differences between 2007.1 and 2007.2? ===

* UI redesigned for small and recessed screen
* Simplified visuals for performance
* Simplified UI
* More interactions including finger scrolling
* [[Today|openmoko-today]] rewritten; works as application launcher and task manager as well
* neod takes care of basic powermanagement, supports AUX and POWER buttons for navigation / additional functionality
* Updated upstream packages

=== Q: Where to get snapshot images? ===

* [[Openmoko2007.2#Pre-built_snapshot_images|Unofficial images]] listed at the bottom of this article

* Official snapshots and ipkg repository:
** http://buildhost.openmoko.org/snapshots/2007.08/

=== Q: My mrxvt (terminal) fonts are huge. ===

Edit src/feature.h to set MIN_XFT_FONT_SIZE to lower value:
#define MIN_XFT_FONT_SIZE (2)
and rebuild mrxvt & openmoko-devel-image.

End edit /etc/mrxvt/mrxvt.conf
Mrxvt.xftSize: 4
Mrxvt.xftHint: 1

{{Languages|Om 2007.2}}

[[Category:Om 2007.2| ]]

Om 2007.2

2008-09-12T15:18:56Z

Relet: /* Updating your image */

{{Languages|Om 2007.2}}
{{OM2007.2}}
{{Distributions|Om 2007.2}}

'''Om 2007.2''' is the second version of the Openmoko distribution. Development began on 2007-07-26. [[Om 2008.8]] is the successor of this software stack.

Goals of this version are an improved set of PIM applications, improved theming that fixes a lot of the usability problems of the first generation design, more formalized UI guidelines and a number of changes in the build system. The latter should introduce more recent software by staying closer in sync with upstream org.openembedded.dev.

An official announcement was made by Sean Moss-Pultz on August 20:
* http://lists.openmoko.org/pipermail/announce/2007-August/000018.html

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

= Known Issues =

For the very latest status, see [http://docs.openmoko.org/trac/search?q=2007.2 all tickets with 2007.2] in the bug tracker.

==Missing Esc key==

With the default image you can't escape edit mode in vi due to the missing Esc key. You need to [[Switching_Keyboards|install a new on-screen keyboard]], and in order to do this you'll need to [[Getting_Started_with_your_Neo_FreeRunner#Set_up_USB-based_networking_and_update|set up USB networking]] first. You can then SSH into the FreeRunner from your computer and use the keyboard on that computer to edit files in vi.

Alternative on-screen keyboards feature an escape key.

If you are stuck in vi you can type <tt>:q</tt> or <tt>:q!</tt> to exit without saving, or <tt>ZZ</tt> to save and exit.

==Missing /, | and > keys==

These keys are missing from the 0 button. This can be fixed by editing <tt>/etc/multitap-pad/im-multipress.conf</tt>, see [[Switching_Keyboards#Fix_Default| this page]], but unfortunately you need vi, or some other editor to do so. Therefore you need to SSH in and [[Getting_Started_with_your_Neo_FreeRunner#Set_up_USB-based_networking_and_update|set up USB networking]] first.

Alternative on-screen keyboards should have these characters.

=="Signature Check Failed" errors when running `opkg update`==

The signatures are missing from the repository.

Workaround: If the Packages.gz files are downloading ok you can ignore this error.
After your first <tt>opkg upgrade</tt> you should get these signatures.

==The SSH / Dropbear connections over the USB link frequently freezes==

This happens when the phone goes to sleep after a few minutes. To unfreeze, unplug and replug the USB cable. To stop this from happening, press the Power button to get the Power menu, then choose Power Management: Disabled.

==My device is unresponsive. How do I perform a hard reset?==

For different boot methods, see [[Booting the Neo FreeRunner]].

==No GUI for controlling sound volume==

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

Workaround:
Run the terminal application or [[USB_Networking|log in via usb]], and run the [[Neo alsamixer]] application. To see all the options, including Mic2, run
:alsamixer -V all
The mixer is simpler than it looks. Use the left and right arrow keys to select "headphone" or "PCM" and use the up and down arrow keys to adjust the volume. You can also adjust your microphone volume with the "mic2" adjustment. Press ESC when finished. Then exit the terminal application or log out of the USB login.

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

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

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

To manually restore one of the state files,
:alsactl -f ''path-to-statefile'' restore

One way to increase the volume of the microphone is to do the following:
# ssh into your FreeRunner
# vi /usr/share/openmoko/scenarios/gsmhandset.state
# search for "Mic2"
# change to "value 3"
If people report not being able to hear you when you call, then setting the Mic2 value to 2 or 3 should fix that.

'''Question: I am using headphones but only the right speaker work the left don't work how can I fix this ?'''

This should be set correctly by restoring gsmheadset.state.
Pull and replug the headset jack to make sure the correct state-file is restored.
To manually control the switch between Speaker and headset:
Start alsamixer, scroll along to the right until you find "Amp Spk" and mute it (m), the sound will then come out from both channels of the
headphones and not out of the speaker.

= Installing =

If you want install this software distribution to your device, you have to follow these steps:
* Download the recent image of Om2007.2 on the [[Downloads#Openmoko_2007.2_images_.28GTK.29|Downloads]] page
* [[Flashing the Neo FreeRunner|Flash]] to your Neo FreeRunner

[[Image:Openmoko2007.2 home screen.png|thumb|right|home screen of Om 2007.2]]

==Building 2007.2==

=== Why to build ===

Before getting your feet wet, step back a moment and ask yourself why you want to build the Openmoko distribution image. Chances are you are a kernel and application developer and just want to develop on your package -- in that case building Openmoko is completely unnecessary and a waste of time. You may rather want to use the Openmoko [[Toolchain]] and build only the stuff that is interesting to you.

=== How to build ===

The MokoMakefile is now able to build Om 2007.2 images. If you use this new version of the MokoMakefile, you can ignore everything below and just continue building Om 2007.2 in the same way that you previously built images (i.e. according to [[MokoMakefile]]). Make sure you set the generation correctly at the top of the file.

Follow the [http://wiki.openembedded.net/index.php/Getting_Started getting started] steps of OpenEmbedded. It is suggested to use Bitbake 1.8.8 at least.

{{note|Instead of using '''git.openmoko.org''' (as indicated in OE GettingStarted), please make sure to use '''git.openmoko.org''' as [[MonotoneServer|monotone server]]. This ensures you have a working revision of the metadata and will render a successful build}}

Put the following in your local.conf

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "om-gta01"
DISTRO = "openmoko"

ENABLE_BINARY_LOCALE_GENERATION = "1"
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"

For multi-core machines, the following additions can be used for a speed-up (numbers should be tweaked based on the actual number of cores):

PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"

To free disk space after builds, add:

INHERIT += "rm_work"

Replace "${HOME}/oe" with the path to where your "org.openembedded.dev" folder lives. For the other entries have a look at ''conf/local.conf.sample'' about their meaning.

Run ''bitbake <package name>'' (e.g. openmoko-devel-image).

=== How to enable autorev ===

First apply the following patch to bitbake.

http://lists.linuxtogo.org/pipermail/openembedded-devel/2007-September/003035.html

Add the following line to your local.conf

require conf/distro/include/moko-autorev.inc

Then run bitbake as normal. Openmoko will now build with latest SVN checkouts.

=== Build issues ===

==== Wrong certificate ====
You may get something like this while the bitbake recipes are parsed:

Error validating server certificate for 'https://libw100.svn.sf.net:443':
- The certificate hostname does not match.
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

That is an issue in a bitbake file. One should not use the short-name for sourceforge (sf.net) when certificates are only for exact host names. Accept the certificate and everything is fine for now.

==== openmoko-libs FTBFS ====
Some applications have not been fully modified to build with the new libraries of Openmoko and still need the old-style ''openmoko-libs'' package. ''libmokogsm'' which is needed for ''openmoko-libs'' then fails to build. As a workaround you can remove the not yet ported applications that need ''openmoko-libs'' making it unneccessary itself. To do this edit ''packages/tasks/openmoko-taks.bb'' and find the following lines:

.
.
.
openmoko-terminal \
matchbox-panel-2 \
matchbox-panel-2-applets \
matchbox-applet-inputmanager \
# openmoko-appmanager \
matchbox-keyboard \
matchbox-stroke \
openmoko-keyboard \
.
.
.

Now put a hash (''#'') before ''openmoko-terminal'' and ''openmoko-keyboard''. You can verify that ''openmoko-libs'' is not needed any more by issuing ''bitbake -g openmoko-devel-image'' (= creates a dependency graph). There should be no mentioning of ''openmoko-libs'' in the file ''task-depends.dot''. '''Please note that the graphicall terminal and the virtual keyboard will be missing now.''' You can still have terminal access by following the [[USB Networking]] guide. For keyboard input in Qemu add the ''-usbdevice keyboard'' switch.

==== gtk+ fails building w/ gtkcombobox.c ====

If you get these errors:

gtkcombobox.c: In function 'gtk_combo_box_size_request':
gtkcombobox.c:1859: warning: unused variable 'font_desc'
gtkcombobox.c:1858: warning: unused variable 'metrics'
gtkcombobox.c:1857: warning: unused variable 'context'
gtkcombobox.c:1855: warning: unused variable 'arrow_size'
gtkcombobox.c:1854: warning: unused variable 'font_size'
gtkcombobox.c: In function 'gtk_combo_box_size_allocate':
gtkcombobox.c:1962: error: 'arrow_size' undeclared (first use in this function)
gtkcombobox.c:1962: error: (Each undeclared identifier is reported only once
gtkcombobox.c:1962: error: for each function it appears in.)
gtkcombobox.c:1965: error: 'font_desc' undeclared (first use in this function)
gtkcombobox.c:1966: error: 'context' undeclared (first use in this function)
gtkcombobox.c:1967: error: 'metrics' undeclared (first use in this function)
gtkcombobox.c:1969: error: 'font_size' undeclared (first use in this function)

Go to your /build/tmp/work/fic-gta01-angstrom-linux-gnueabi/gtk+-2.10.14-r3/gtk+-2.10.14/gtk directory, and patch gtkcombobox.c with the following:

Thanks to rmoravcik in #openmoko (patch was taken from http://pastebin.ca/654717 )

--- gtkcombobox.c 2007-08-12 20:30:07.000000000 +0200
+++ gtkcombobox.c 2007-08-12 20:29:58.000000000 +0200
@@ -1948,6 +1948,12 @@
gtk_combo_box_size_allocate (GtkWidget *widget,
GtkAllocation *allocation)
{
+ gint font_size;
+ gint arrow_size;
+ PangoContext *context;
+ PangoFontMetrics *metrics;
+ PangoFontDescription *font_desc;
+
GtkComboBox *combo_box = GTK_COMBO_BOX (widget);
gint focus_width, focus_pad;
GtkAllocation child;

==== Building glibc fails with a segfault in QEMU ====

If your build aborts and you see something like this:

NOTE: package glibc-2.5: started
NOTE: package glibc-2.5-r6: task do_package: started
NOTE: preparing tree for binary locale generation
NOTE: generating locale en_US (UTF-8)
qemu: uncaught target signal 11 (Segmentation fault) - exiting

...

NOTE: Tasks Summary: Attempted 271 tasks of which 0 didn't need to be rerun and 1 failed.
ERROR: '/home/moko/oe/org.openembedded.dev/packages/glibc/glibc_2.5.bb' failed

Try editing your local.conf file. Change:

ENABLE_BINARY_LOCALE_GENERATION = "1"

to

ENABLE_BINARY_LOCALE_GENERATION = "0"

and restart the build. This may have some effect on internationalization (you will see a warning indicating that), but at least the build will continue. Thanks to rwhitby for the tip.

Alternatively, as suggested by XorA in #openmoko, if you are running a 64-bit host distribution, try forcing a different QEMU rev, also in local.conf:

PREFERRED_VERSION_qemu-native = "0.9.0+cvs20070701"
SRCDATE_qemu-native = 20070701

==== libxml2-native fails with xmlCatalogPtr errors ====

Go to your build/tmp/work/i686-linux/libxml2-native-2.6.29-r1/libxml2-2.6.29/include/libxml/ directory and patch xmlversion.h with the following:

--- xmlversion.h 2007-08-17 10:45:42.000000000 +0100
+++ xmlversion.h 2007-08-17 10:51:36.000000000 +0100
@@ -219,7 +219,7 @@
*
* Whether the Catalog support is configured in
*/
-#if 0
+#if 1
#define LIBXML_CATALOG_ENABLED
#endif

On my system the libxml2-native-2.6.29-r1 directory is in a directory named i686-linux, yours may be different. I believe this patch to be a workaround to make libxml2-native build. I am not yet sure what the consequences of enabling XML catalogue support are.

== Pre-built images ==
* http://buildhost.openmoko.org/snapshots/2007.08/ (Official snapshots and ipkg repository)

=== Buildhost directory structure ===

The content of the Openmoko build server directory is available at
* http://buildhost.openmoko.org/OM2007.2/tmp/

It contains
* cache
** Internal caching data, not for human interpretation
* cross
** The cross-compilation toolchain used. You can download this and use it on your local machine.
* deploy
** deploy/images
*** The filesystem, kernel and bootloader images to be flashed into NAND
** deploy/ipk
*** the .ipk packages
* rootfs
** the extracted root filesystem. Please use the images from deploy/images instead
* staging
** no user servicable parts inside
* stamp
** internal state data
* work
** the actual build trees (including patches source code and binaries) of the individual packages

== Updating your image ==

'''REVISE this section - buildhost is down, replaced. '''

Now that you have a functional 2007.2 image on your Neo, you will want to keep it updated. Fortunately, ipkg is already set up to pull updated packages from the openmoko buildhost.

On the phone, in the terminal (or via ssh), if you have a live internet connection and DNS resolution set up in /etc/resolv.conf:

ipkg update && ipkg upgrade

will bring your installed packages up to the most recent versions. Also have a look at alternative/additional ipkg sources at [[downloads]].

If you are also building your own images and packages, you can also run a simple httpd on your build host and serve your own ipkg files to the Neo.

On the build host, for example:

thttpd -d <path_to_moko/tmp/deploy/glibc/ipk> -p 8080

will serve your packages on port 8080.

Then, on the neo, make a new file at /etc/ipkg/local-feed.conf with these contents:

src/gz local-all http://192.168.0.200:8080/all
src/gz local-armv4t http://192.168.0.200:8080/armv4t
src/gz local-om-gta01 http://192.168.0.200:8080/om-gta01

and ipkg on the Neo (update-upgrade) will pick up files from your local build host's repository (assuming its IP address is 192.168.0.200, as is default in the [[USB Networking]] setup) in addition to the openmoko buildhost.

Or better yet, change the 192.168.0.200:8080 addresses above to the eth0 IP address of your build machine (instead of the usb0 IP address), and then you can access your local repository with your Neo plugged into any machine on your local net, or even via bluetooth.

Also if you are building your own packages or packages from the OE database that aren't part of Openmoko by default, you can install those packages as follows.

On the build host:

bitbake <name_of_package>
bitbake -crebuild package-index

Then on the Neo:

ipkg update
ipkg install <name_of_package>

The new package might not show up in the program menu until you reboot or restart X.

==FAQ==
=== Q: What are differences between 2007.1 and 2007.2? ===

* UI redesigned for small and recessed screen
* Simplified visuals for performance
* Simplified UI
* More interactions including finger scrolling
* [[Today|openmoko-today]] rewritten; works as application launcher and task manager as well
* neod takes care of basic powermanagement, supports AUX and POWER buttons for navigation / additional functionality
* Updated upstream packages

=== Q: Where to get snapshot images? ===

* [[Openmoko2007.2#Pre-built_snapshot_images|Unofficial images]] listed at the bottom of this article

* Official snapshots and ipkg repository:
** http://buildhost.openmoko.org/snapshots/2007.08/

=== Q: My mrxvt (terminal) fonts are huge. ===

Edit src/feature.h to set MIN_XFT_FONT_SIZE to lower value:
#define MIN_XFT_FONT_SIZE (2)
and rebuild mrxvt & openmoko-devel-image.

End edit /etc/mrxvt/mrxvt.conf
Mrxvt.xftSize: 4
Mrxvt.xftHint: 1

{{Languages|Om 2007.2}}

[[Category:Om 2007.2| ]]

Openmoko Local Groups: Berlin

2008-09-07T21:48:58Z

Relet: /* 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 [[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
|
|
|-
|[[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
|unfortunately not yet
|
|-
|...
|
|
|
|
|
|
|}

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

TangoGPS

2008-08-27T11:01:16Z

Relet: /* Using Google Maps with TangoGPS */

{{Languages|TangoGPS}}
{{Application|TangoGPS}}

__TOC__

TangoGPS is a map application which can utilize Neo's built-in GPS to show your current location.

[[Image:TangoGPS1.jpg]]

Website: http://www.tangogps.org

== Running tangoGPS on [[Om 2008.8]] ==

{{note|There may be other steps because I remember it took a while before my TangoGPS started working, but these are the only things I remember installing}}

From the freerunner connected to the internet:

opkg install gpsd
opkg install http://www.tangogps.org/downloads/tangogps_0.9.3-r1_armv4t.ipk

If opkg complains about not being able to acquire a lock, try:

pkill packagekit

To get gpsd working on the Freerunner you have to change the configuration according to [[Gpsd#GPS_on_GTA02]].
Then start gpsd by:

/etc/init.d/gpsd start

Now you must power up the GPS-chip by opening the "Settings" application and setting the GPS entry to "on". Now you can run tangoGPS and wait until it get's a GPS fix. This can take up to a few minutes.

== Running TangoGPS on [[debian]] ==

Tangogps is a very nice GPS mapping application. The latest version is available in [[Debian]].

Unfortunately it depends on gpsd which conflicts with frameworkd in fso-frameworkd.

# apt-get install gpsd tangogps

Edit <code>/etc/frameworkd.conf</code>. In the section <code>[ogpsd]</code>, edit to read:
<pre>
# path = /dev/ttySAC1
path = /dev/null
</pre>

/etc/init.d/fso-frameworkd restart
/etc/init.d/zhone-session stop && sleep 2 && /etc/init.d/zhone-session start

# dpkg-reconfigure gpsd

* Start gpsd automatically on boot? Yes.
* Device the GPS receiver is attached to: /dev/ttySAC1
* Should gpsd handle attached USB GPS receivers automatically? Yes
** not certain what this answer should be
* Options to gpsd: none

Start tangogps like this:

# echo 1 >/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron
Turns the GPS on.

# DISPLAY=:0 tangogps

'''Issues:'''
* The different daemons for reading GPS data mean that both tangogps and the framework demo GPS application can't be configured to work at the same time. Reboots are probably necessary when switching between them.
** Both gpsd and the framework publish GPS data through dbus, though with different interfaces. This suggests a number of possible solutions.
*** gpsd or the framework could implement the other's interface (along with their own).
*** a translator could read one interface and emulate the other
*** the framework could have an option to read data from gpsd.
*** opgsd/gypsy could be extended to be backwards compatible with the majority of gps applications.

== Downloading Maps for offline use ==
tangoGPS can bunch-download the map images so you don't need an internet connection while walking around. By default tangoGPS stores downloaded maps to /tmp/. This folder is lost every time you reboo the device. But you can use the "Config" tab within tangoGPS to change the "Cache Dir" location to , for example, /osm/ . So downloaded maps will be kept in the Neos flash, also after reboot. This works fine on OM2007.2 and Debian. If this config gets lost during reboot file a bug against your distro.

Once you have set the location to a non-volatile path, you can connect your Neo to the internet by USB or WiFi at home and start downloading the maps of your area. Tap the map screen and select "map download". Now on-the-road tangoGPS will be able to show you maps in different zoom levels even though you are not connected to the inet.

== Downloading Maps via GPRS ==
I think TangoGPS may have started working after I followed the instructions to get GPRS working with GSM multiplexing here: [[Manually_using_GPRS#Option_1:_With_GSM_multiplexing_and_with_a_GUI]]

There are steps included in those instructions to improve GPS performance. The great thing is that once you get GPRS working, you can roam with TangoGPS running and have it download maps as needed over the GPRS connection!

== Importing Tracks into TangoGPS ==

TangoGPS is able to record and store a track in its native format, and [http://psung.blogspot.com/2008/07/sharing-gps-tracks-from-tangogps-on.html tools] exist to convert this to GPX.
However, TangoGPS does not support the import of tracks. You may help yourself by using [http://relet.net/frog/archives/68 this tool] to import GPX trackpoints as a series of POIs directly into the sqlite database which tangoGPS uses to store POIs.

== Using Google Maps with TangoGPS ==

Go to Config and change the url to http://mt1.google.com/mt?&x=%d&y=%d&zoom=%d and check the "Inverted Zoom" box. Press save Repository Configuration and you're ready to go.
:Automated map download will most certainly fail after a certain period of time, as Google is very keen on keeping leechers out.
:It did work for me...

[[Category:GPS Applications]]

TangoGPS

2008-08-23T23:46:14Z

Relet: +toc

{{Languages|TangoGPS}}
{{Application|TangoGPS}}

__TOC__

TangoGPS is a map application which can utilize Neo's built-in GPS to show your current location.

[[Image:TangoGPS1.jpg]]

Website: http://www.tangogps.org

== Running tangoGPS on [[Om 2008.8]] ==

{{note|There may be other steps because I remember it took a while before my TangoGPS started working, but these are the only things I remember installing}}

From the freerunner connected to the internet:

opkg install gpsd tangogps

If opkg complains about not being able to acquire a lock, try:

pkill packagekit

To get gpsd working on the Freerunner you have to change the configuration according to [[Gpsd#GPS_on_GTA02]].
Then start gpsd by:

/etc/init.d/gpsd start

Now you must power up the GPS-chip by opening the "Settings" application and setting the GPS entry to "on". Now you can run tangoGPS and wait until it get's a GPS fix. This can take up to a few minutes.

== Running TangoGPS on [[debian]] ==

Tangogps is a very nice GPS mapping application. The latest version is available in [[Debian]].

Unfortunately it depends on gpsd which conflicts with frameworkd in fso-frameworkd.

# apt-get install gpsd tangogps

Edit <code>/etc/frameworkd.conf</code>. In the section <code>[ogpsd]</code>, edit to read:
<pre>
# path = /dev/ttySAC1
path = /dev/null
</pre>

/etc/init.d/fso-frameworkd restart
/etc/init.d/zhone-session stop && sleep 2 && /etc/init.d/zhone-session start

# dpkg-reconfigure gpsd

* Start gpsd automatically on boot? Yes.
* Device the GPS receiver is attached to: /dev/ttySAC1
* Should gpsd handle attached USB GPS receivers automatically? Yes
** not certain what this answer should be
* Options to gpsd: none

Start tangogps like this:

# echo 1 >/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron
Turns the GPS on.

# DISPLAY=:0 tangogps

'''Issues:'''
* The different daemons for reading GPS data mean that both tangogps and the framework demo GPS application can't be configured to work at the same time. Reboots are probably necessary when switching between them.
** Both gpsd and the framework publish GPS data through dbus, though with different interfaces. This suggests a number of possible solutions.
*** gpsd or the framework could implement the other's interface (along with their own).
*** a translator could read one interface and emulate the other
*** the framework could have an option to read data from gpsd.
*** tangogps could be extended to read data from the framework.

== Downloading Maps for offline use ==
tangoGPS can bunch-download the map images so you don't need an internet connection while walking around. By default tangoGPS stores downloaded maps to /tmp/. This folder is lost every time you reboo the device. But you can use the "Config" tab within tangoGPS to change the "Cache Dir" location to , for example, /osm/ . So downloaded maps will be kept in the Neos flash, also after reboot. This works fine on OM2007.2 and Debian. If this config gets lost during reboot file a bug against your distro.

Once you have set the location to a non-volatile path, you can connect your Neo to the internet by USB or WiFi at home and start downloading the maps of your area. Tap the map screen and select "map download". Now on-the-road tangoGPS will be able to show you maps in different zoom levels even though you are not connected to the inet.

== Downloading Maps via GPRS ==
I think TangoGPS may have started working after I followed the instructions to get GPRS working with GSM multiplexing here: [[Manually_using_GPRS#Option_1:_With_GSM_multiplexing_and_with_a_GUI]]

There are steps included in those instructions to improve GPS performance. The great thing is that once you get GPRS working, you can roam with TangoGPS running and have it download maps as needed over the GPRS connection!

[[Category:GPS]]

== Importing Tracks into TangoGPS ==

TangoGPS is able to record and store a track in its native format, and tools exist to convert this to GPX.
However, TangoGPS does not support the import of tracks. You may help yourself by using [http://relet.net/frog/archives/68 this tool] to import GPX trackpoints as a series of POIs directly into the sqlite database which tangoGPS uses to store POIs.

== Using Google Maps with TangoGPS ==

Go to Config and change the url to http://mt1.google.com/mt?&x=%d&y=%d&zoom=%d and check the "Inverted Zoom" box. Press save Repository Configuration and you're ready to go.
:Automated map download will most certainly fail, as Google is very keen on keeping leechers out.

TangoGPS

2008-08-23T23:45:35Z

Relet: /* Using Google Maps with TangoGPS */

{{Languages|TangoGPS}}
{{Application|TangoGPS}}

TangoGPS is a map application which can utilize Neo's built-in GPS to show your current location.

[[Image:TangoGPS1.jpg]]

Website: http://www.tangogps.org

== Running tangoGPS on [[Om 2008.8]] ==

{{note|There may be other steps because I remember it took a while before my TangoGPS started working, but these are the only things I remember installing}}

From the freerunner connected to the internet:

opkg install gpsd tangogps

If opkg complains about not being able to acquire a lock, try:

pkill packagekit

To get gpsd working on the Freerunner you have to change the configuration according to [[Gpsd#GPS_on_GTA02]].
Then start gpsd by:

/etc/init.d/gpsd start

Now you must power up the GPS-chip by opening the "Settings" application and setting the GPS entry to "on". Now you can run tangoGPS and wait until it get's a GPS fix. This can take up to a few minutes.

== Running TangoGPS on [[debian]] ==

Tangogps is a very nice GPS mapping application. The latest version is available in [[Debian]].

Unfortunately it depends on gpsd which conflicts with frameworkd in fso-frameworkd.

# apt-get install gpsd tangogps

Edit <code>/etc/frameworkd.conf</code>. In the section <code>[ogpsd]</code>, edit to read:
<pre>
# path = /dev/ttySAC1
path = /dev/null
</pre>

/etc/init.d/fso-frameworkd restart
/etc/init.d/zhone-session stop && sleep 2 && /etc/init.d/zhone-session start

# dpkg-reconfigure gpsd

* Start gpsd automatically on boot? Yes.
* Device the GPS receiver is attached to: /dev/ttySAC1
* Should gpsd handle attached USB GPS receivers automatically? Yes
** not certain what this answer should be
* Options to gpsd: none

Start tangogps like this:

# echo 1 >/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron
Turns the GPS on.

# DISPLAY=:0 tangogps

'''Issues:'''
* The different daemons for reading GPS data mean that both tangogps and the framework demo GPS application can't be configured to work at the same time. Reboots are probably necessary when switching between them.
** Both gpsd and the framework publish GPS data through dbus, though with different interfaces. This suggests a number of possible solutions.
*** gpsd or the framework could implement the other's interface (along with their own).
*** a translator could read one interface and emulate the other
*** the framework could have an option to read data from gpsd.
*** tangogps could be extended to read data from the framework.

== Downloading Maps for offline use ==
tangoGPS can bunch-download the map images so you don't need an internet connection while walking around. By default tangoGPS stores downloaded maps to /tmp/. This folder is lost every time you reboo the device. But you can use the "Config" tab within tangoGPS to change the "Cache Dir" location to , for example, /osm/ . So downloaded maps will be kept in the Neos flash, also after reboot. This works fine on OM2007.2 and Debian. If this config gets lost during reboot file a bug against your distro.

Once you have set the location to a non-volatile path, you can connect your Neo to the internet by USB or WiFi at home and start downloading the maps of your area. Tap the map screen and select "map download". Now on-the-road tangoGPS will be able to show you maps in different zoom levels even though you are not connected to the inet.

== Downloading Maps via GPRS ==
I think TangoGPS may have started working after I followed the instructions to get GPRS working with GSM multiplexing here: [[Manually_using_GPRS#Option_1:_With_GSM_multiplexing_and_with_a_GUI]]

There are steps included in those instructions to improve GPS performance. The great thing is that once you get GPRS working, you can roam with TangoGPS running and have it download maps as needed over the GPRS connection!

[[Category:GPS]]

== Importing Tracks into TangoGPS ==

TangoGPS is able to record and store a track in its native format, and tools exist to convert this to GPX.
However, TangoGPS does not support the import of tracks. You may help yourself by using [http://relet.net/frog/archives/68 this tool] to import GPX trackpoints as a series of POIs directly into the sqlite database which tangoGPS uses to store POIs.

== Using Google Maps with TangoGPS ==

Go to Config and change the url to http://mt1.google.com/mt?&x=%d&y=%d&zoom=%d and check the "Inverted Zoom" box. Press save Repository Configuration and you're ready to go.
:Automated map download will most certainly fail, as Google is very keen on keeping leechers out.

Gpe-scap

2008-08-22T21:48:28Z

Relet: order

{| align="right"
| __TOC__
|}
gpe-scap is an gui-application for taking screenshots of your mobile phone. It offers the possibility of saving the taken screenshots or uploading them to http://scap.linuxtogo.org .

= Installation =
gpe-scap is in the offical [[Om2008.8|2008.8]] repository and can be installed with the [[Om2008.8_Installer|gui-installer]] via: ''"INSTALLER -> install -> Miscellaneous -> gpe-scap''".

Alternativly one can install it via the command line with:
opkg install gpe-scap
= Usage =
== Gui ==
After installation there's an icon with the name ''"Take screenshot"'' on the mainscreen. With pressing the icon gpe-scap is started and takes a screenshot. The big disadvantage with this method is, that gpe-scap can just do a screenshot of the place where it was started and it always takes a screenshot with it's own loading-symbol which renders this method of taking a screenshot totally useless.

;Workaround: Create a simple shell script, which calls gpe-scap after five seconds.
<pre>
sleep 5
gpe-scap
</pre>
Place it in /usr/bin. chmod +x. Replace gpe-scap in the line "Execute = gpe-scap" in the file /usr/share/applications/gpe-scap.desktop with the name of the script file. Now, when you start the screenshot application via the GUI, not much will happen. You have five seconds to switch to the application you wish to capture. The gpe-scap window will automatically pop up with the current screenshot, if it was successful.

== ssh ==
The other and way better method of taking a screenshot with gpe-scap is doing it via ssh. For this method one has to open the window, menu or whatever he wants to take a screenshot of on his device. Then you connect via ssh to the device and execute:
DISPLAY=:0 gpe-scap
Now you get a perfect screenshot of whatever you want.

= Bugs =

Some versions of gpe-scap are unable to save or upload PNG files, due to a wrongly linked library. Try
<pre>
ln -s /lib/libc.so.6 /lib/libc.so
</pre>

Gpe-scap

2008-08-22T21:48:05Z

Relet: /* Gui */

{| align="right"
| __TOC__
|}
gpe-scap is an gui-application for taking screenshots of your mobile phone. It offers the possibility of saving the taken screenshots or uploading them to http://scap.linuxtogo.org .

= Installation =
gpe-scap is in the offical [[Om2008.8|2008.8]] repository and can be installed with the [[Om2008.8_Installer|gui-installer]] via: ''"INSTALLER -> install -> Miscellaneous -> gpe-scap''".

Alternativly one can install it via the command line with:
opkg install gpe-scap
= Usage =
== Gui ==
After installation there's an icon with the name ''"Take screenshot"'' on the mainscreen. With pressing the icon gpe-scap is started and takes a screenshot. The big disadvantage with this method is, that gpe-scap can just do a screenshot of the place where it was started and it always takes a screenshot with it's own loading-symbol which renders this method of taking a screenshot totally useless.

;Workaround: Create a simple shell script, which calls gpe-scap after five seconds.
<pre>
sleep 5
gpe-scap
</pre>
Place it in /usr/bin. chmod +x. Replace gpe-scap in the line "Execute = gpe-scap" in the file /usr/share/applications/gpe-scap.desktop with the name of the script file. Now, when you start the screenshot application via the GUI, not much will happen. You have five seconds to switch to the application you wish to capture. The gpe-scap window will automatically pop up with the current screenshot, if it was successful.

== Bugs ==

Some versions of gpe-scap are unable to save or upload PNG files, due to a wrongly linked library. Try
<pre>
ln -s /lib/libc.so.6 /lib/libc.so
</pre>

== ssh ==
The other and way better method of taking a screenshot with gpe-scap is doing it via ssh. For this method one has to open the window, menu or whatever he wants to take a screenshot of on his device. Then you connect via ssh to the device and execute:
DISPLAY=:0 gpe-scap
Now you get a perfect screenshot of whatever you want.

TangoGPS

2008-08-22T21:31:48Z

Relet: /* Importing Tracks into TangoGPS */

Distributions

2008-08-20T01:44:01Z

Relet: /* Toolkits / Runtimes */

{{Languages|Distributions}}

{| class="wikitable" style="float:right;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|<font color=white>Distributions</font>
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* <font color='#BBBBBB'>Openmoko (official)</font>
** [[Om 2008.8]]
** [[Om 2007.2]]
** [[Om 2007.1]]
** [[OpenmokoFramework|FSO]]
* <font color='#BBBBBB'>Community</font>
** [[SHR]]
* <font color='#BBBBBB'>Other</font>
** [[Qtopia]]
** [[Debian]]
</div>
|-
|}<noinclude>[[Category:Templates]]</noinclude>

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 similar to Linux distributions; complete operating systems with 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 [[Latest Images]], 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.

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 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://buildhost.openmoko.org/daily/ 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.

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

* [[Om2008.8|Om 2008.8]]
* [[Downloads#Openmoko_2008.8_images_.28ASU.29|Download]]

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

* [[FSO]]
* [http://trac.freesmartphone.org:8000/trac-example Development tracker]
* [http://downloads.openmoko.org/framework/milestone2/ Download milestone 2]
* [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]]

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

Debian Linux, the whole distribution, on a mobile phone.

* [[Debian]]

== 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 || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| SMS || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| [[GPRS]] || Not through UI || Not through UI || Not through UI || N/A || No (3) || style="background:lightgreen;" | Yes
|-
| WiFi || style="background:lightgreen;" | Yes || Not through UI || style="background:lightgreen;" | Yes (*) || N/A || style="background:lightgreen;" | Yes ||style="background:lightgreen;" | Yes
|-
| VoIP || ?? || ?? || ?? || ?? || ?? || style="background:lightgreen;" | Yes
|-
| Bluetooth || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| GPS || style="background:lightgreen;" | Yes (1) || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes (1) || N/A || No || style="background:lightgreen;" | Yes
|-
|}

=== 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 || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Finger friendly || Partially || Partially || Partially || N/A || style="background:lightgreen;" | Yes || No
|-
| Accelerometer || No || No || style="background:lightgreen;" | 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) || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes (1) || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| PIM || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Phonebook || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Dialer || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Web Browser || style="background:lightgreen;" | Yes (1) || ? || style="background:lightgreen;" | Yes (1) || ? || No || style="background:lightgreen;" | Yes
|-
| Mail Client || ? || ? || style="background:lightgreen;" | Yes || ? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| XMPP Client || style="background:lightgreen;" | Yes (1) || ? || style="background:lightgreen;" | Yes [[IM#Implementation_Recommendations|(1)]] || ? || No || style="background:lightgreen;" | Yes
|-
| Media Player || ? || ? || ? || ? || ? || ?
|-
|}

=== 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+ || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes
|-
| QT/Qtopia || No || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Middleware || gsmd/neod || freesmartphone.org || qtopia-x11 || freesmartphone.org || qtopia || freesmartphone.org
|-
| [[Java]] || Jalimo || Jalimo || Jalimo || ? || ? || No
|-
| [[Python]] || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || ? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| [[Mono]] || style="background:lightgreen;" | Yes(1) || ? || style="background:lightgreen;" | 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| ]]
[[Category:Documentation]]

Switching Keyboards on Om 2007.2

2008-08-20T00:16:27Z

Relet: /* Fix Default */ tab completion

==Fix Default==

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

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

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

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

==Matchbox keyboard==

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

===What does the keyboard look like?===

[[Image:Complete_QWERTY_Keyboard_On_The_Freerunner_screenshot.png|none|thumb|260px|Screenshot of the keyboard applet]]

===Considerations===

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

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

===How to install it?===

If you use a ScaredyCat release (http://buildhost.automated.it/OM2007.2/), use the following:

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

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

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

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

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

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

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

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

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

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

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

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

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

==Switch back to the original Openmoko keypad==

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

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

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

[[Category:Openmoko]]
[[Category:Technical]]

Neo FreeRunner FAQ

2008-08-19T20:01:46Z

Relet: why not just answer them, instead? ;)

{{Gta02menu}}

== FreeRunner known hardware related issues ==

There is collection of FreeRunner hardware issue wiki page [[Freerunner_Hardware_Issues]] , could help you quickly know if you bump into same problem and the possible way to solve some of issues.

==Booting==
'''Q: I can't boot Neo with charger?'''

'''A:'''
1. You can't boot GTA02 without a spare battery. You should boot Neo with spare battery and attach your charger, then you can boot into neo.

2. Once your phone is booted, remove the spare battery. Freerunner will remain running,

3. Insert dead battery and let it charge.

'''Q: Unable to flash FreeRunner after booting either into NAND or NOR.'''
'''A:''' {{note|Please check [[Getting_Started_with_your_Neo_FreeRunner]] for more information about the flashing image.}}

'''Q: I can ssh into the phone via USB per the wiki instructions, but dfu-util does not find the phone. '''

'''A:'''
This is what I need to run as root and the everything works fine:
root(eno,freerunner)# cat upom
#!/bin/sh
/sbin/ifconfig usb0 192.168.0.200 netmask 255.255.255.0
/sbin/route add -host 192.168.0.202/32 dev usb0

/bin/echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -F
iptables -A INPUT -s 192.168.0.202 -i usb0 -d 192.168.0.200 -j ACCEPT
iptables -A INPUT -s 192.168.0.200 -i eth+ -d 192.168.0.202 -j ACCEPT
iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.0.202 -j ACCEPT
iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.2.0/24 -j ACCEPT

iptables -A FORWARD -s 192.168.0.202 -i usb0 -d 192.168.2.0/24 -o eth+ -j
ACCEPT
iptables -A FORWARD -s 192.168.2.0/24 -i eth+ -d 192.168.0.202 -o usb0 -j
ACCEPT

iptables -A OUTPUT -d 192.168.2.0/24 -o eth+ -j ACCEPT
iptables -A OUTPUT -d 192.168.0.202 -o usb0 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
root(eno,freerunner)#

'''Q: What image version is used?'''

'''A:'''

1. Kernel version using: uname -a

2. Root filesystem using: cat /etc/version or cat /etc/om-version

3. u-boot using: grep Bootloader /dev/mtdblock0

== Battery ==
=== What is the expected battery life? ===
See [[Neo FreeRunner (GTA02) Battery#Notes_about_expected_battery_life]] and more battery information in [[Neo_FreeRunner_(GTA02)_Battery]]
=== How do I enable fast charge mode for anything but the official mains charger? ===
See [[Forcing fast charge mode]].

== USB ==
'''Q:''' How do I connect an USB memory-stick etc?

'''A:''' This requires an adapter Mini-B 5-pole => Type A jack or an adapter jack => jack. [http://wiki.openmoko.org/wiki/Host_Mode see here]

'''Q:''' Once I have such an adapter, can I use it to connect 2 Neo to each other?

'''A:''' This question is equivalent to '''How to connect two [Unix/Linux] computers via USB cable and what sort of special cable is needed?''' -> http://www.linuxquestions.org/questions/linux-general-1/connecting-two-computers-with-a-usb-cable-data-cable-411073
<br >
It should work if one Neo is set to Host mode and the other one set to Device mode. One Neo could give power to the USB-port it the other Neo's battery is low. ''(I have to verify this)''

== GSM ==

=== SIM compatibility ===
'''Q:'''Sim card is not working, how do I run diagnostics?

'''A:'''
Here is the "how to" check.

Follow [[Manually_using_GSM]] until you get an OK prompt. More detalied documenation please refer [[FreeRunner_unable_to_work_with_3G_SIM_cards]] and [[Carriers]].

=== GSM/GPRS information ===

Following page contain very useful information:

* [http://wiki.openmoko.org/wiki/Gsmd GSM Daemon]

* [http://wiki.openmoko.org/wiki/Gsm General GSM page]

* [http://wiki.openmoko.org/wiki/Hardware:AT_Commands AT commands]

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

== GPS ==

'''Q: How do I get the GPS working?'''

'''A: '''See [[GTA02 GPS]]

'''Q''': it takes a long time (10min+) before the Freerunner gets first GPS data

'''A: '''See [[GPS Problems]].

== Wi-Fi ==

'''Q: How do I get the wlan working? '''

'''A: ''' See [[GTA02 WLAN]]

== Bluetooth ==

'''Q: How do I get the Bluetooth working? '''

'''A: ''' See [[Manually_using_Bluetooth]]

== Sysfs function==

'''Q: How do I get low level hardware related function, like power up device, dump register? '''

'''A: ''' See [[GTA02_sysfs]]

== Display ==

=== Can it play VGA video? ===

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

=== How to change the background picture of the root window? ===

Look [http://wiki.openmoko.org/wiki/Today/2007.2#Adjust_UI_components_at_runtime here].

== Software ==

=== Does it support Java? ===
There is a [https://wiki.evolvis.org/jalimo/index.php/OpenMoko port of Jalimo] for Openmoko.

=== Does it support Flash? So can I watch YouTube? ===

=== Does it support Ruby ===

Ruby 1.9 please refer http://blog.sparkymat.net/2008/08/10/ruby-19-on-openmoko/
Ruby 1.8.6 please refer http://blog.wolfman.com/articles/2008/08/10/ruby-1-8-6-on-openmoko-freerunner

=== How can I type a '/' in the software keyboard? ===

See [[Switching Keyboards]]

=== How do I get a qwerty software keyboard?===

See [[Switching Keyboards]]

===How to use an external USB or Bluetooth keyboard with ing FreeRunner ? ===

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

This'll put the Freerunner in to powered USB host mode, then just plug in the keyboard and it'll work. Personally I've made a .desktop file to switch into and out of host mode. To switch back to unpowered device mode just run:

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

[[Category:GTA02 Hardware]]

Neo FreeRunner FAQ

2008-08-19T13:20:54Z

Relet: /* What is the expected battery life? */

{{Gta02menu}}

== FreeRunner known hardware related issues ==

There is collection of FreeRunner hardware issue wiki page [[Freerunner_Hardware_Issues]] , could help you quickly know if you bump into same problem and the possible way to solve some of issues.

==Booting==
'''Q: I can't boot Neo with charger?'''

'''A:'''
1. You can't boot GTA02 without a spare battery. You should boot Neo with spare battery and attach your charger, then you can boot into neo.

2. Once your phone is booted, remove the spare battery. Freerunner will remain running,

3. Insert dead battery and let it charge.

'''Q: Unable to flash FreeRunner after booting either into NAND or NOR.'''
'''A:''' {{note|Please check [[Getting_Started_with_your_Neo_FreeRunner]] for more information about the flashing image.}}

'''Q: I can ssh into the phone via USB per the wiki instructions, but dfu-util does not find the phone. '''

'''A:'''
This is what I need to run as root and the everything works fine:
root(eno,freerunner)# cat upom
#!/bin/sh
/sbin/ifconfig usb0 192.168.0.200 netmask 255.255.255.0
/sbin/route add -host 192.168.0.202/32 dev usb0

/bin/echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -F
iptables -A INPUT -s 192.168.0.202 -i usb0 -d 192.168.0.200 -j ACCEPT
iptables -A INPUT -s 192.168.0.200 -i eth+ -d 192.168.0.202 -j ACCEPT
iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.0.202 -j ACCEPT
iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.2.0/24 -j ACCEPT

iptables -A FORWARD -s 192.168.0.202 -i usb0 -d 192.168.2.0/24 -o eth+ -j
ACCEPT
iptables -A FORWARD -s 192.168.2.0/24 -i eth+ -d 192.168.0.202 -o usb0 -j
ACCEPT

iptables -A OUTPUT -d 192.168.2.0/24 -o eth+ -j ACCEPT
iptables -A OUTPUT -d 192.168.0.202 -o usb0 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
root(eno,freerunner)#

'''Q: What image version is used?'''

'''A:'''

1. Kernel version using: uname -a

2. Root filesystem using: cat /etc/version or cat /etc/om-version

3. u-boot using: grep Bootloader /dev/mtdblock0

== Battery ==
=== What is the expected battery life? ===
See [[Neo FreeRunner (GTA02) Battery#Notes_about_expected_battery_life]] and more battery information in [[Neo_FreeRunner_(GTA02)_Battery]]
=== How do I enable fast charge mode for anything but the official mains charger? ===
???
==== Without soldering ====
???

== USB ==
'''Q:''' How do I connect an USB memory-stick etc?

'''A:''' This requires an adapter Mini-B 5-pole => Type A jack or an adapter jack => jack. [http://wiki.openmoko.org/wiki/Host_Mode see here]

'''Q:''' Once I have such an adapter, can I use it to connect 2 Neo to each other?

'''A:''' This question is equivalent to '''How to connect two [Unix/Linux] computers via USB cable and what sort of special cable is needed?''' -> http://www.linuxquestions.org/questions/linux-general-1/connecting-two-computers-with-a-usb-cable-data-cable-411073
<br >
It should work if one Neo is set to Host mode and the other one set to Device mode. One Neo could give power to the USB-port it the other Neo's battery is low. ''(I have to verify this)''

== GSM ==

=== SIM compatibility ===
'''Q:'''Sim card is not working, how do I run diagnostics?

'''A:'''
Here is the "how to" check.

Follow [[Manually_using_GSM]] until you get an OK prompt. More detalied documenation please refer [[FreeRunner_unable_to_work_with_3G_SIM_cards]] and [[Carriers]].

=== GSM/GPRS information ===

Following page contain very useful information:

* [http://wiki.openmoko.org/wiki/Gsmd GSM Daemon]

* [http://wiki.openmoko.org/wiki/Gsm General GSM page]

* [http://wiki.openmoko.org/wiki/Hardware:AT_Commands AT commands]

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

== GPS ==

'''Q: How do I get the GPS working?'''

'''A: '''See [[GTA02 GPS]]

'''Q''': it takes a long time (10min+) before the Freerunner gets first GPS data

'''A: '''See [[GPS Problems]].

== Wi-Fi ==

'''Q: How do I get the wlan working? '''

'''A: ''' See [[GTA02 WLAN]]

== Bluetooth ==

'''Q: How do I get the Bluetooth working? '''

'''A: ''' See [[Manually_using_Bluetooth]]

== Sysfs function==

'''Q: How do I get low level hardware related function, like power up device, dump register? '''

'''A: ''' See [[GTA02_sysfs]]

== Display ==

=== Can it play VGA video? ===

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

=== How to change the background picture of the root window? ===

Look [http://wiki.openmoko.org/wiki/Today/2007.2#Adjust_UI_components_at_runtime here].

== Software ==

=== Does it support Java? ===
There is a [https://wiki.evolvis.org/jalimo/index.php/OpenMoko port of Jalimo] for Openmoko.

=== Does it support Flash? So can I watch YouTube? ===

=== Does it support Ruby ===

Ruby 1.9 please refer http://blog.sparkymat.net/2008/08/10/ruby-19-on-openmoko/
Ruby 1.8.6 please refer http://blog.wolfman.com/articles/2008/08/10/ruby-1-8-6-on-openmoko-freerunner

=== How can I type a '/' in the software keyboard? ===

See [[Switching Keyboards]]

=== How do I get a qwerty software keyboard?===

See [[Switching Keyboards]]

===How to use an external USB or Bluetooth keyboard with ing FreeRunner ? ===

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

This'll put the Freerunner in to powered USB host mode, then just plug in the keyboard and it'll work. Personally I've made a .desktop file to switch into and out of host mode. To switch back to unpowered device mode just run:

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

[[Category:GTA02 Hardware]]

Talk:Neo USB charger specifications and compatibility list

2008-08-17T21:02:56Z

Relet: /* Charger identification */ new section

The separation between compatible USB chargers or not should be made, IMHO -- [[User:OlivierBerger|OlivierBerger]] 19:47, 19 July 2008 (UTC)

The USB charger spec seems to be refering to micro-USB chargers, not those with Mini-USB connectors (see chapter 4.1), maybe the text should be rewritten accordingly --[[User:CyrusDreams|CyrusDreams]] 19:09, 20 July 2008 (UTC)

== Charger identification ==

Is there any way to convince the moko that he should leech in fast charge mode from a regular charger which supports more than 100/500mA? I would like to use it with a car or bike charger without actually decreasing the battery life. -- [[User:Relet|Relet]] 21:02, 17 August 2008 (UTC)

Openmoko Local Groups: Berlin

2008-07-21T08:53:15Z

Relet: /* 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
|
|
|-
|[[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 [[Image:Moko.jpg|center]]
|
|-
|[[User:dk|dk]]
|java
|Gta02
|moabit
|interested in group order
|
|
|-
|[[User:relet|relet]]
|code
|would read your feed
|moabit
|
|02
|nak
|-
|[[User:Sbusch|sbusch]]
|coding (c, c++, java), linux
|coding on my free phone :-)
|Friedrichshain
|especially interested in voip and IM
|
|
|-
|[[User:thebohemina|thebohemian]]
|C, Java, OpenEmbedded, organize things
|OM for professional use, sharing knowledge, Free Software advocacy
|Friedrichshain
|
|GTA02, GTA01
|yes|-
|-
|...
|
|
|
|
|
|
|}

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

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

User talk:Relet

2008-07-21T08:28:05Z

Relet:

Hi,
du hast dich auf der Openmoko User Group Seite für Berlin eingetragen. Ich hab eine ML dafür aufgesetzt: http://www.freelists.org/list/openmoko-users-berlin

Falls du Interesse daran Treffen hast, trag dich da ein. :)

Gruß
Robert

::Danke! [[User:Relet|Relet]] 08:28, 21 July 2008 (UTC)

----

Distributions

2008-07-11T17:07:30Z

Relet: /* Features by Distribution */

This is a skeleton to try and get the strengths and weaknesses of the various distributions available for the Neo listed in one place. Please help contribute!

Initial information is available at http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/

I will probably start with what is there and fill in what I can.

== Features by Distribution ==
{| border=1 |
| Feature || OM2007.2 || FSO || ASU || SHR
|-
| Description || The Openmoko 2007.2 Stack, utilizing GTK+ and assorted applications. 2007.2, since it was the 2nd iteration of the GTK+ user interface that we released in 2007. || The FSO Stack, also known as the Openmoko Framework initiative. This one is called FSO, because it’s an implementation of the freesmartphone.org APIs. You may also have seen the term Zhone which describes the framework testing user interface and is a minor part of this stack. || August Software Update. The ASU Stack, the combination of a classical smartphone stack based on Trolltech’s Qtopia ported to X11 and enhanced with an EFL-based launcher and new applications. You may have seen the term Illume which is the launcher of ASU. || Stable Hybrid Release, a combination of the FSO, some of the 2007.2 GTK software, and the ASU that provides all of the functionality of the 2007.2 software, but with the stability of the FSO.
|-
| Availability || [http://buildhost.openmoko.org/daily/ Official Buildhost] and [[MokoMakefile]] support for development builds || Now (Milestone 1) || August 2008 || No
|-
| URL || ? || [http://trac.freesmartphone.org:8000/trac-example Devlopment tracker] || ? || [[Stable Hybrid Release]]
|-
!colspan=5| Connectivity
|-
| Telephony || Yes || Yes || Between "unstable" and "no" || N/A
|-
| SMS || Yes || No || Applications exist but don't function reliably || N/A
|-
| GPRS || Not through UI || Not through UI || Not through UI || N/A
|-
| WiFi || Yes || No || Yes || N/A
|-
| Bluetooth || Yes || No || Yes || N/A
|-
| GPS || Yes (1) || Yes (1) || Yes (1) || N/A
|-
!colspan=5| User Interaction
|-
| Stylus friendly || Yes || Yes || Yes || N/A
|-
| Finger friendly || Partly || Yes || No || N/A
|-
| Accelerometer || No || No || No || N/A
|-
!colspan=5| Applications
|-
| Terminal || Basic, but unusable due to lack of certain keyboard characters || No || No || N/A
|-
| PIM || Yes || No || Yes || N/A
|-
| Phonebook || Yes || No || Yes || N/A
|-
| Dialer || Yes || Yes || Yes || N/A
|-
!colspan=5| Application Compatibility (Toolkits / Runtimes)
|-
| GTK+ || Yes || ? || Yes || Yes
|-
| QT/Qtopia || No || Yes? || Yes || Yes?
|-
| Java || Jalimo? || ? || ? || ?
|-
| Python || Yup || ? || ? || ?
|-
|}

Latest Images can be found here: http://wiki.openmoko.org/wiki/Latest_Images

Footnotes:

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

[[Category:Software]]
[[Category:Distributions]]
[[Category:Documentation]]
[[Category:FSO]]

Latest Images

2008-07-11T17:07:04Z

Relet: highlight this, it's good.

This page is intended to summarize in one place the various images you can try out on your Openmoko Neo FreeRunner (GTA02) or 1973 (GTA01). Note however, that some of these are works in progress and may not have even released any files yet. Nothing is guaranteed to work. Proceed at your own risk.

Currently, the images in development include:
*The 2007.2 GTK Image that ships on the Freerunner
*The ASU (April|August Software Update) qtopia-based Image
*The FSO (FreeSmartPhone.org) Image
*Qtopia image from qtopia.net
*The SHR (Stable Hybrid Release) Image

A nice summary of these various stacks on Michael Lauer's blog: [http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO? TMTLA!]

;Another nice summary chart here in the Wiki - [[Distributions]]

Instructions on flashing your Openmoko device are provided at
* [[Getting_Started_with_your_Neo_FreeRunner]]
* [[Getting_Started_with_your_Neo1973]]
----
==2007.2 GTK Image==
The latest most stable release should reside here:
[http://buildhost.openmoko.org/releases/Freerunner/ http://buildhost.openmoko.org/releases/Freerunner/]

*You can download the latest daily builds here:
**For Neo FreeRunner [http://buildhost.openmoko.org/daily/freerunner/ http://buildhost.openmoko.org/daily/freerunner/]
***Look for files of the form: Openmoko-openmoko-devel-image-glibc-ipk-P1-Snapshot-YYYYMMDD-om-gta02.rootfs.tar.gz
***and: openmoko-devel-image-om-gta02.tar.gz
**For Neo 1973 the link is [http://buildhost.openmoko.org/daily/neo1973/ http://buildhost.openmoko.org/daily/neo1973/]
***Look for files of the form: openmoko-devel-image-om-gta01.tar.gz
***and: Openmoko-openmoko-devel-image-glibc-ipk-P1-Snapshot-YYYYMMDD-om-gta01.rootfs.tar.gz
**Tools, like dfu-util and openocd [http://buildhost.openmoko.org/daily/tools/ http://buildhost.openmoko.org/daily/tools/]

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]
=== ScaredyCat ===
Users may have heard of "ScaredyCat" images. These are usable images created by [http://blog.automated.it/category/openmoko/ Andy Powell] and are currently based on the 2007.02 software stack.

http://buildhost.automated.it/OM2007.2/
----

==ASU (April|August Software Update) qtopia-based Image==
There has not been a recommended release of the ASU yet. You may wish to review the [[ASU_Feature_Plan]] or some [http://dos.jogger.pl/2008/06/29/asu-to-przyszlosc/ screenshots]

*You can download the latest daily builds here:
**For Neo FreeRunner [http://buildhost.openmoko.org/daily/freerunner/ http://buildhost.openmoko.org/daily/freerunner/]
***Look for files of the form: openmoko-qtopia-x11-image-om-gta02.tar.gz
***and: Openmoko-openmoko-qtopia-x11-image-glibc-ipk-P1-Snapshot-YYYYMMDD-om-gta02.rootfs.tar.gz
**For Neo 1973 the link is [http://buildhost.openmoko.org/daily/neo1973/ http://buildhost.openmoko.org/daily/neo1973/]
***Look for files of the form: openmoko-qtopia-x11-image-om-gta01.tar.gz
***and: Openmoko-openmoko-qtopia-x11-image-glibc-ipk-P1-Snapshot-YYYYMMDD-om-gta01.rootfs.tar.gz
----

==FSO (FreeSmartPhone.org) Image==
Milestone 1 is here: [http://downloads.openmoko.org/framework/milestone1/ http://downloads.openmoko.org/framework/milestone1/]

[http://www.youtube.com/watch?v=toPe0S8QpJY Video of FSO Milestone 1]

Browse the source: [http://trac.freesmartphone.org:8000/trac-example/browser http://trac.freesmartphone.org:8000/trac-example/browser]

Learn more at its wiki page: [[OpenmokoFramework]]
----

==Qtopia image from qtopia.net==
[http://www.qtopia.net/modules/mydownloads/index.php Qtopia.net images] for the
*Neo FreeRunner [http://www.qtopia.net/modules/mydownloads/visit.php?lid=67 (qtopia-4.3.2-gta02-flash.tgz)]
**and the [http://www.qtopia.net/modules/mydownloads/visit.php?lid=68 root file system (ficgta02-qtopia-developer-rootfs.tgz)]
*For the Neo 1973 [http://qtopia.net/modules/devices/openmoko.php (Note: the below links do not work. The Neo 1973 files are temporarily unavailable from qtopia.net.)]
**[http://www.qtopia.net/modules/mydownloads/visit.php?lid=39 Neo 1973 root file system] (Link temporarily broken.)
**[http://www.qtopia.net/modules/mydownloads/visit.php?lid=48 Neo 1973 flash image] (Link temporarily broken.)
**You might also try [http://trolltech.com/developer/downloads/qtopia/qtopia-source-gpl ftp.trolltech.com snapshots]
**But the Neo 1973 image is available from here [http://buildhost.automated.it/OM2007.2/openmoko-qtopia-image-om-gta01.tar.gz openmoko-qtopia-image-om-gta01.tar.gz]
----

==SHR (Stable Hybrid Release) Image==
The Stable Hybrid Release (SHR) is intended to be a combination of the
FSO, some of the 2007.2 GTK software, and the ASU that provides all of
the functionality of the 2007.2 software, but with the stability of
the FSO and the new GUI toolkits provided by the ASU. It will probably
be based on an ASU build, with the FSO software and GTK end-user apps
added.

The SHR doesn't exist anywhere but in a few people's heads at the moment (2008-07-05). Hopefully, all the work in it will be integrated back into one of the other releases, and it will cease to exist. The point is to get us a release with stable calls & suspend/resume, plus access to all those other nifty apps we had on 2007.2 and the ASU.

Learn more at its wiki page: [[Stable_Hybrid_Release]]
----
[[category:Openmoko]]
[[category:Software]]

GPS Problems

2008-07-10T20:31:57Z

Relet:

See [[GPS]] for details on how to evaluate the Freerunner GPS with cat.

{|border="3"
|+Problems I'm having with the GPS
!Username||Checked outside?||External antenna?||Note
|-
|Pthorin ||Yes|| No ||I tried for about 40 minutes outside, I'm running om-gta02 P1-Snapshot-20080622. Did get GPS time outside, but only got lines like:
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
|-
|iandouglas ||Yes|| No ||Spent over a half hour outdoors, the NMEA port on my Samsung Blackjack 2 found my position just fine, but also got the same 99.99,99.99,99.99*30 line as Pthorin when powering on the GPS unit, starting gpsd, then running gpspipe at the command line
|-
|Dummy ||?|| ? ||
|}

=== Solved problems ===

''Let's collect hints which could solve the above problems here. E.g.: How to get the best results with your internal antenna''

* Before reporting a problem here, please check that you've had the GPS out in the open air, preferably with the GPS antenna pointed up, for over 15 mins. (the screen the right way up). This should get a lock in even the worst cases.

* Also note if you've tried unpluging and repluging the internal GPS connector. (See [[Disassembling_Neo1973]] about 2/3 of the way down. (this may differ on freerunner, pictures appreciated)

[[Category:GPS]]

GPS Problems

2008-07-10T20:31:16Z

Relet: solved?

See [[GPS]] for details on how to evaluate the Freerunner GPS with cat.

Before reporting a problem here, please check that you've had the GPS out in the open air, preferably with the GPS antenna pointed up, for over 15 mins. (the screen the right way up)

This should get a lock in even the worst cases.

Also note if you've tried unpluging and repluging the internal GPS connector. (See [[Disassembling_Neo1973]] about 2/3 of the way down. (this may differ on freerunner, pictures appreciated)

{|border="3"
|+Problems I'm having with the GPS
!Username||Checked outside?||External antenna?||Note
|-
|Pthorin ||Yes|| No ||I tried for about 40 minutes outside, I'm running om-gta02 P1-Snapshot-20080622. Did get GPS time outside, but only got lines like:
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
|-
|iandouglas ||Yes|| No ||Spent over a half hour outdoors, the NMEA port on my Samsung Blackjack 2 found my position just fine, but also got the same 99.99,99.99,99.99*30 line as Pthorin when powering on the GPS unit, starting gpsd, then running gpspipe at the command line
|-
|Dummy ||?|| ? ||
|}

=== Solved problems ===

''Let's collect hints which could solve the above problems here. E.g.: How to get the best results with your internal antenna''

[[Category:GPS]]

Distributions

2008-07-10T15:53:00Z

Relet:

Distributions

2008-07-10T15:48:52Z

Relet: /* Features by Distribution */

Getting Started with your Neo FreeRunner

2008-07-09T23:25:24Z

Relet: /* Un-crippling the 2007.2 image */

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

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

== The Package Contents ==

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

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

==Getting To Know the Neo FreeRunner==

<div align-center>
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 25px; padding-left: 0.5em;">
</td>
<td style="width: 10px; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu8.jpg|370px|thumb|AUX Button and phone jack(From left to right)|center]]</td><td style="padding: 1px 1em 0; background: #ffffff;">
[[Image:menu9.jpg|365px|thumb|Power Button, USB and external GPS Antenna (From left to right)|center]]</td></tr></table>
</div>

<div align-center>
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; padding-left: 0.5em;">
</td>
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu12.jpg|233px|thumb|AUX Back side with battery|center]]</td><td style="padding: 1px 1em 0; background: #ffffff;">
[[Image:menu11.jpg|260px|thumb|Put the SIM card and SD card here|center]]</td></tr></table>
</div>

<div align-center>
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; padding-left: 0.5em;">
</td>
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|open case from this side |center]]</td><td style="padding: 1px 1em 0; background: #ffffff;">
[[Image:menu14.jpg|250px|thumb|Opened|center]]</td></tr></table>
</div>

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

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

===Turning on the Neo Freerunner===

====Charging the Neo Freerunner====

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

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

You can boot your Neo FreeRunner in the following ways:

: [[Image:Circle２.gif|10px]] You can power it up into an Openmoko image directly.

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

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

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

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

<div align-center>
<table width="100%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 25px; padding-left: 0.5em;">

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

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

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

<div align-center>
<table width="100%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 25px; padding-left: 0.5em;">

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

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

<div align-center>
<table width="100%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 25px; padding-left: 0.5em;">

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

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

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

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

3. Set console to USB

4. Set console to Serial

5. Reset

6. Power off}}

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

===Unlocking the screen===

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

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

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

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

===Step1. Download the DFU-util===

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

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

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

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

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

Type in the following command in the terminal on a GNU/Linux host. On some systems you need to be root before this will work.
./dfu-util -a (partion name) -R -D (download image file name)

ex:

./dfu-util -a kernel -R -D uImage-2.6.24+svnr4082-r4055-r3-neo1973.bin

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:0px solid #ffffff; background:#ffffff; width:100%;floating="center"; "
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid ffffff; border:1px solid #ffffff; width:75% " |
<div align="left">
[[Image:menu15.jpg|thumb|Log into U-Boot in NOR Flash, connect your Neo with Linux Host via USB cable]]
Before you execute the command, please log into U-Boot in the NOR Flash. The Neo FreeRunner needs to be booted into U-Boot for flashing.

You will then need to connect your Neo with the GNU/Linux host via USB cable. Press Enter to execute the command. When flashing succeeds the following will be shown:

status(0) = No error condition is present<br>
Done!
</div>
|}

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

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

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

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

When flashing succeeds the following will be shown:

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

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

Connect the Neo FreeRunner to a GNU/Linux host with the USB cable. For Mac OS X please refer to [[MacOS_X]]. After booting into the Openmoko image there will be a new interface, usb0, on your GNU/Linux host.

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

ifconfig usb0 192.168.0.200 netmask 255.255.255.0
ssh root@192.168.0.202

Press Enter to get by the password.

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

auto usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0

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

config_usb0="192.168.0.200/24"

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

ssh root@192.168.0.202

Press Enter to get by the password.

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

192.168.0.202 openmoko

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

ssh root@openmoko

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

==Un-crippling the 2007.2 image==

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

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

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

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

To test GPS, you can use agpsui:

# opkg install openmoko-agpsui

For a nice map, try tangoGPS:

# opkg install tangogps

And if you want the Media Player back:

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

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

# opkg install gpe-icons gpe-gallery

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

==Appendix==
If you want to know more about the Neo FreeRunner then you can get more information in the following topics:
* [[GTA02 Openness]]
* [[Neo FreeRunner]]
* [[Neo FreeRunner GTA02 Hardware]]
* [[FreeRunner/Buttons and LEDs]]
* [[Latest_Images]]

[[Category:GTA02 Hardware]]

User:Relet

2008-07-09T20:32:27Z

Relet: New page: ...botching along. relet jabber ccc de http://relet.net

...botching along.

relet jabber ccc de

http://relet.net

Talk:Neo FreeRunner Wifi

2008-07-09T20:31:21Z

Relet: /* disabling wifi on startup */ new section

Passphrase issues:

I have noticed that with wireless sometimes it works better to use the password hash in the wpa_supplicant.conf instead of the ascii text.
You can use the wpa_passphrase utility (I don't know if this is included in the GTA02 or not as I don't have one) to generate the hash for the passphrase.

techiem2@escape-pod ~ $ wpa_passphrase MYWIFI "my passphrase"
network={
ssid="MYWIFI"
#psk="my passphrase"
psk=a4c08e767704a66d3fb27d4bf072e2da279f76adc568722b9a6f97964b982620
}

Of course you would probably want to redirect output to the end of your wpa_supplicant.conf (wpa_passphrase MYWIFI "my passphrase">>/etc/wpa_supplicant/wpa_supplicant.conf).

--[[User:Techiem2|techiem2]] 19:12, 3 July 2008 (UTC)

== disabling wifi on startup ==

What would be the cleanest way to not enable wifi on startup? -- [[User:Relet|Relet]] 20:31, 9 July 2008 (UTC)

Openmoko Local Groups: Berlin

2008-07-02T17:50:17Z

Relet: /* Possible Participants */

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

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

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

=== Meetings, Events ===
Meeting language is German ;-)
{|border=1
!Date
!Location
!Topic
!Who
|-
|8.-12. August 2007
|Flugplatz Finowfurt
|[https://events.ccc.de/camp/2007/Intro/ Chaos Communication Camp 2007] und [http://events.ccc.de/camp/2007/GSM_Village GSM Village]
|?
|-
|23.08.2007 / 18:00
|[https://berlin.ccc.de/wiki/CCC_Berlin CCCB] / [https://berlin.ccc.de/wiki/Club_Discordia Club Diskordia]
|First meeting. bring your hardware
|Roh, pH5, [[User:Minime|tim]](+ 2?), ? (please add yourself)
|-
|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]]