Openmoko - User contributions [en]

Om 2009

2009-05-21T23:15:48Z

Michaelshiloh: /* Bug List and Known Issues */

[[Image:Paroli.png|thumb|Screenshot of Paroli, the GSM app of OM2009]]
'''Om 2009''' is the next version of the official Openmoko distribution. It is currently under developement and should be released in Summer 2009 to replace [[Om 2008]]. It will be based on [[FSO|freesmartphone.org]] milestone 5.5 framework and use [[Paroli]] as GSM software

=== Features Status ===

Below is the feature list for Om 2009. It's broken down into features that have been implemented and need testing, and features that still need to be finished. Since [[Paroli]] is the chosen phone application, many of the features come straight from Paroli project.

==== Implemented ====

* incoming and outgoing phone calls
* sms incoming and outgoing
* simple phone book (no images)
* call log
* charging
* suspend and resume
* resume speed < 2 seconds - this is close but waiting on a kernel bug
* battery indicator - works for gta02 battery
* gsm indicator
* switch to elementary
* wifi GUI
* scrolling in UI - fixed by migrating from etk to elementary
* switching profiles
* in-call volume adjustment
* settings tool (this needs to be enabled by editing /etc/paroli/paroli.cfg)

==== Not Yet Implemented or Broken ====

* boot time < 2 minutes - currently examining ways to speed this up
** install udev-static devices - caveat you loose bind-home
** use readahead to cache python dirs before starting framework and paroli
** use readahead to cache dirs for X
** remove uneeded startup programs ( ie portmap )
** prime GSM during init for paroli's use
* screen lock
** currently X screen saver is used during screen blank
* user changeable ring tones - works via command line
* bluetooth - support in FSO milestone 5.5, needs GUI
* led indication for missed calls or sms
* GTA01: battery indicator doesn't work for gta01 battery

==== Bug List and Known Issues ====

* gsm0710muxd: "Modem does not respond to AT commands" [http://docs.openmoko.org/trac/ticket/2257 #2257]
* oeventsd rules ignored [http://trac.freesmartphone.org/ticket/381 FSO #381]
* After some received call or sms, the phone does not suspend anymore [http://trac.freesmartphone.org/ticket/435 FSO #435]
* Problem at Display->Profile: can't get back to illume, and illume, paroli or paroli-illume all look exactly the same
** WORKAROUND: Reboot. The first time it boots there is a problem but it's OK after that.

== Installing ==

* If you've not updated your GSM chip firmware, it's Moko8 and REALLY needs to be updated. See [[GSM/Flashing#uSD-card_Image_.28GTA02_only.29|GSM flashing]]
* Also update to the latest versions of [[qi]] or [[Bootloader|uboot]] bootloaders
* You can add a bind-home directory to the first partition (must be ext2 or ext3 ) of your SD card. On the OM2009 boot it will be mounted as /home/root. This way you can reflash your phone without losing anything in your home directory ( [[Paroli]] contacts and settings, maps, etc )

The latest OM2009 and qi/uboot images are available at http://downloads.openmoko.org/distro/testing/

Installing OM2009 is simple as flashing an image. Actually that's what you need to do..

# Download! You need the correct fso-paroli-image and uImage.bin files for your device. There are also rootfs tarballs for installing onto an SD card. [http://downloads.openmoko.org/distro/testing/NeoFreerunner Freerunner] or [http://downloads.openmoko.org/distro/testing/Neo1973 Neo1973]
# Flash! Detailed instructions for [[Flashing_the_Neo_Freerunner|Freerunner]] and [[Flashing_the_Neo_1973|Neo1973]].
# Start! The image will boot into fullscreen Paroli and all of the features listed above will be available. To learn more about Paroli, see [[Paroli]]

== Using OM2009 ==
'''Write your best tips here!!'''
* To learn to use Paroli, the phone software, go to http://wiki.openmoko.org/wiki/Paroli#FAQ
* To have log directory that isn't cleared when you reboot, the /var/log symlink needs to be turned into a directory:
rm /var/log
mkdir /var/log

== Development ==
'' When we set the very limited goals of OM2009 we had two goals in mind:''

''1. Give those members of the community who only wanted a daily phone, a distro they could use'' 
''2. Introduce technology that would allow the community to come together and improve on these basics''

''Community interaction, open development and user driven decision making are at the core of Om2009. Going forward this will be an effort with the community for the community. I invite you to join the effort to make om2009 with paroli the best Om-labeled distribution for the Freerunner. ''

'''How can you help?'''

''Test the distro, let us know about bugs you find, or even fix them and send us patches.''

''Tell us about your experiences using om2009, what should we change, where can we improve?''

''Paroli has come a long way but it still needs a lot of love and optimizing, so if you are into python or efl, check out the code from git.paroli.org, join #paroli on irc and let's get crackin'. There is lots of things to do, opimd needs to be integrated and improved, the UI needs polishing, overall speed can be increased etc etc''

''More into Chat and email? Feel like writing a jabber/irc/xxx or email client that really fits the screen? Or do you know of one? Let's hear about it. This device has a lot of potential and we are so close to reaching the far corners, the kernel is in good shape, the framework is doing great and telephony apps such as paroli or the shr suite are steadily improving.''

''So, get your Freerunner in shape again. Flash it with a nice current distro and let it do what it was meant to do :)''

''Let's make Om2009 a community product, something all of us can be proud of and say "we did this".''

Mirko/Openmoko at http://lists.openmoko.org/pipermail/community/2009-May/048061.html)

* [http://n2.nabble.com/Om2009-release-plan-tp2410042p2410042.html OM2009 release plan]

* [[Om_2009_get_active]]
* [[Paroli-issues]]

* Paroli: http://www.paroli-project.org/ and [[Paroli]]
* FSO: http://www.freesmartphone.org and [[OpenmokoFramework]]

* BUILDS: [http://downloads.openmoko.org/distro/testing/ Testing] and [http://downloads.openmoko.org/distro/unstable/ Daily/unstable]

=== Reporting Bugs ===

Please enable debugging as [[Om_2009#Using_OM2009|instructed above]]. Attaching frameworkd.log and paroli.log will aid in solving the bug.

Please search the bug list for you issue before adding it to trac. Some of these issues might be [[Paroli]] or FSO issue so you can also check their tracs for solutions or discussions.

* https://docs.openmoko.org/trac (Use the Om2009 tag so that we can track it against this release.)
* http://trac.freesmartphone.org/wiki
* http://www.paroli-project.org/trac

[[Category:Om 2009| ]]

Download

2009-05-06T01:11:50Z

Michaelshiloh: /* Om 2008.12 */

{{Languages|Download}}
This page lists various images you can try out on your Openmoko supported smartphone and some [[#Other downloads]].

See [[Distributions]] for a more descriptive comparison. Then see [[Development Branches Policy]] when you want to know where the really bleeding edge is.

{|align=right
|__TOC__
|}

== Installation instructions ==

See [[Flashing the Neo FreeRunner]] for installation instructions. Neo 1973 users: [[Getting Started with your Neo1973]]. If you want to install a system to a microSD card, see [[Booting from SD]].

The release directories can contain up to four files:

* a Root FileSystem image. These are the files with '''rootfs''' in their name. They come both as a .jffs2 ready-to-flash image, and as a .tar.gz ready-to-cp tarball.
* a Kernel image (files with '''uimage''' in their name).
* a u-boot bootloader (file with '''u-boot''' in the name).
* a splash image file.

Also, the archive directory contains two identical versions of most files, one having the date in the filename. For those convenience ?

One usually needs only to flash the phone with the root filesystem and the kernel image. The splash image is eyecandy. The u-Boot bootloader is a critical component, you don't want to install a new version of that systematically, but there have been improvements since the one released in shipping phones.

== Openmoko Inc. driven release targets ==
=== Om 2009 ===
Om 2009 is the 2009 release of Om. It is under development but you can download beta images
[http://downloads.openmoko.org/distro/testing/NeoFreerunner/ here]

{{Main|Om2009}}

=== Om 2008.12 ===
Om 2008.12 is an updated release of Om 2008.8.
You can download the image [http://downloads.openmoko.org/distro/releases/Om2008.12/ here]

{{Main|Om 2008.12 Update}}

=== Om 2008.9 (ASU) ===

Om 2008.9 is an updated release of Om 2008.8.
You can download the image [http://downloads.openmoko.org/distro/releases/Om2008.9/ here]

{{Main|Om 2008.9 Update}}

'''Neo FreeRunner images'''

There is no need to reflash if you have installed Om 2008.8 and used ''opkg update && opkg upgrade''.
Comment about naming scheme on the [http://lists.openmoko.org/pipermail/community/2008-September/031003.html community mailinglist]

=== The bleeding edge: Om "base / empty" images ===

The ''org.openmoko.dev'' branch does not have any applications preinstalled other than settings and installer, and it is unstable for now.

Images for ''testing'' are at:
http://downloads.openmoko.org/distro/unstable/
To get packages from ''testing'', use this ''/etc/opkg/testing.conf'' :
<pre>
src/gz testing-all http://downloads.openmoko.org/repository/testing/all
src/gz testing-arm http://downloads.openmoko.org/repository/testing/armv4t
src/gz testing-neo http://downloads.openmoko.org/repository/testing/neo1973
src/gz testing-gta02 http://downloads.openmoko.org/repository/testing/om-gta02
</pre>


''unstable'' comes from the same branch, compiled with the AUTOREV flag. There are no images, but packages are at http://downloads.openmoko.org/repository/unstable/

Reference: See [http://lists.openmoko.org/pipermail/community/2008-August/027997.html "Repository and Images" announcement] for details on other "Base image", "testing" and "unstable".

Once you have this base image, you can install the GTK+ telephony apps including gsmd, or Qtopia, or Mickey's framework. Check out the [[FDOM]] page for an idea of what to install.

=== Om 2007.2 images (GTK) ===

{{Main|Om 2007.2}}

Openmoko '''discontinued support''' for this release.
Two external developers still offer their own builds.

==== Celtune ====

Celtune offers different Images and a huge amount of packages (2007.2, pyneo, fso) for neo1973, freerunner and others. Celtune images can be found [http://rabenfrost.net/celtune/ here].

==== ScaredyCat ====

[http://blog.automated.it/category/openmoko/ Andy Powell] maintains images based on the 2007.2 software stack for the gta01 and gta02. A. Powell's ScaredyCat images can be found [http://buildhost.automated.it/OM2007.2/ here].

=== FSO images (freesmartphone.org) ===

{{Main|OpenmokoFramework}}

The file system will be in a jffs2 "summary" file. A file with the extension ".jffs2.summary" can be flashed to the FreeRunner just like an ordinary jffs2 file.

* [http://git.freesmartphone.org/ Browse the source]

* [[OpenmokoFramework/Status_Update_6|newest status update]]

* [http://downloads.freesmartphone.org/fso-stable/milestone5/ Downloads]

=== Android ===
Android now can run on Openmoko FreeRunner.
About the Image, you can check [[Android]] page , to get the detail information.
Android imagescan be found [http://people.openmoko.org/sean_mcneil/ here].

== Openmoko Community driven release targets ==

=== FDOM ===

{{Main|FDOM - a Fat and Dirty OM based distribution}}

Download images: http://compartida.net/openmoko/FDOM/

=== SHR images (Stable Hybrid Release) ===
{{Main|SHR}}
The Stable Hybrid Release (SHR) is intended to be a community driven distribution composed of the FSO and some basic applications, that can be configured to use several different graphical toolkits, for example GTK or EFL. SHR is based on the FSO build. At first, SHR was introduced in order to use the Openmoko2007.2 GTK software in combination with the new FSO, but things have changed.

Download images (unstable currently recommended):
* [http://build.shr-project.org/shr-testing/images/om-gta02 Neo Freerunner testing]
* [http://build.shr-project.org/shr-testing/images/om-gta01 Neo 1973 testing]
* [http://build.shr-project.org/shr-unstable/images/om-gta02 Neo Freerunner unstable]
* [http://build.shr-project.org/shr-unstable/images/om-gta01 Neo 1973 unstable]

== Non-Openmoko distributions ==

=== Qt Extended (formerly Qtopia) images ===

:''Main article: [[Qtopia / Qt Extended on FreeRunner|Qt Extended]]''

Images are available on the [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6&orderby=dateD Qt Extended download page], make sure your browser sends referrer Header when downloading. (Note: direct linking to the files does not work.)

'''Neo FreeRunner'''

* Qt Extended flash image for FIC Neo Freerunner (gta02) version 4.4.2 can be downloaded [http://qtextended.org/modules/mydownloads/visit.php?lid=98 here]. (The tarball contains rootfs and kernel)
* If you need to also download mwester's daily kernel (needed for previous version 4.4.1) you can find it [http://moko.mwester.net/dl.html#kernels here].

'''Neo 1973'''

* Qt Extended flash image for FIC Neo 1973 (gta01) version 4.4.2 can be downloaded [http://qtextended.org/modules/mydownloads/visit.php?lid=99 here]. (The tarball contains rootfs and kernel)

* A alternate Neo 1973 image can be downloaded [http://buildhost.automated.it/OM2007.2/openmoko-qtopia-image-om-gta01.tar.gz here]

'''More Qtopia downloads'''

Addtional packages can be added from the Trolltech feed for this image, found at
http://qtopia.net/packages/feed/4.3.2/neo/
To get to these packages, you need to add the feed as a source in the Qtopia package manager.

=== Debian images ===

{{Main|Debian}}

=== Hackable:1 images ===

{{Main|Hackable:1}}

== Other downloads ==

=== Applications repositories ===

If you are looking for a specific application instead of a full filesystem image:
* {{Main|Community Repository}}
* {{Main|Users Repositories}}

=== CAD files ===
You can download CAD files [http://downloads.openmoko.org/developer/CAD/ here].

=== Schematics ===

You can download the schematics of [[Neo 1973]] (GTA01) and [[Neo FreeRunner]] (GTA02) [http://downloads.openmoko.org/developer/schematics/ here]

=== Press material ===

Download Neo FreeRunner photos in various sizes for print and web use [http://openmoko.com/press-press-material.html here]

=== Tiddlywiki version of wiki.openmoko.org ===
If you want to carry this wiki along with you and to use it offline, then download
it [http://om-tiddlywiki.projects.openmoko.org/openmokowiki.html here] and store it locally, then browse through the pages which you think you need to have, click "save changes", so next time you open it all articles you have fetched previously will be available to you.

[[Category:Distributions]]

Qtopia / Qt Extended on FreeRunner

2008-12-25T04:07:43Z

Michaelshiloh: /* Test Qtopia */

{{Languages|Qtopia_on_FreeRunner}}

This page provides instructions on how to install Qtopia/Qt Extended (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.

{|align=right
|__TOC__
|}

== Current status ==

On 31 October 2008, Trolltech released the [http://qtextended.org/modules/mydownloads/visit.php?lid=98 Qtopia ROM flash image containing the rootfs] for the Openmoko Neo FreeRunner (gta02) containing the Qtopia 4.4.2 release (GPL version). This runs on the [http://qtextended.org/modules/mydownloads/visit.php?lid=91 mwebster ROM flash image containing the kernel]. At release time, 4.4.2 & current mwester's kernel mismatched, please clarify the previous sentence. Hypnotize has released [http://lists.openmoko.org/pipermail/community/2008-November/035245.html Qt Extended 4.4.2 images for the Neo FreeRunner] that work better.

This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does have a webkit based web browser and an GPS "Mapping Demo" application.

There are other third-party GPS applications available:
* [http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner xgps]
* [http://www.linux4.be/fr/roadmap.html RoadMap (experimental)]

([[TangoGPS]] does not work on QtExtended, because it depends upon an Xserver)

You can find all the Qtopia images [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 here] (including Qtextended/Qtopia 4.4 for FreeRunner and Neo1973!)

=== What is in the latest release (QtExtended 4.4.2)? ===
Qtopia 4.4 has been released with the name of [http://doc.trolltech.com/qtextended4.4/release-4-4-2.html QtExtended 4.4].
* a [http://n2.nabble.com/qtopia-update-tp832851p832888.html browser] based on webkit
* [http://n2.nabble.com/-qtopia--rotate-screen--tp841805p841841.html screen rotation in the settings application] (so no automatic rotation)
* [http://n2.nabble.com/Echo-issue-on-OM2008.08-potentially-solved-tp791642.html noise reduction]
* GPS api
* usb net/storage switching
* Gtalk support
* [http://n2.nabble.com/forum/Permalink.jtp?root=841805&post=1083388&page=y better support for non-english languages in the keyboard]

== Option 1: Flashing Qtopia to FreeRunner ==

Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]

== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==

Installation Requirements:

# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)

=== Preparing the SD card ===

See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the "Formatting the SD Card" steps, return here and execute the following:

<pre>
mount /dev/mmcblk0p1 /media/card
mkdir /media/card/boot

mkdir /media/mmcblk0p2
mount /dev/mmcblk0p2 /media/mmcblk0p2
</pre>

This will set you up properly for the installation of the root filesystem and the kernel in the steps below.

=== Installing Qtopia ===

==== Unpacking the Qtopia Root Filesystem Image ====

Download the Qtopia FLASH image from [[Latest Images#Qtopia images]] to your Linux box and extract its contents:

tar xzf qtopia-4.3.2-gta02-flash-*.tgz

You should now have two files:
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2
Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]]. However, in the mount command, substitute the image filename for "/dev/mtdblock0".

==== Creating a compressed tarball ====

Next, tar up the root filesystem:

# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .

Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted. Note the space and the period after the mountpoint.

==== Installing Root Filesystem ====

Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:

scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/

Log in to your FreeRunner and unpack the root filesystem:

<pre>
cd /media/mmcblk0p2
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm -f /media/mmcblk0p2/boot/*
</pre>

'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.

==== Installing Kernel ====

From your Linux box, rename <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> to <tt>uImage.bin</tt> and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the <tt>/media/card</tt> directory as well. There is plenty of room on the first partition to have <tt>uImage.bin</tt> in both locations.

<pre>
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin
scp uImage.bin root@192.168.0.202:/media/card/boot/
scp uImage.bin root@192.168.0.202:/media/card/
</pre>

==== Pointing Qtopia to the SD Card ====

Lorn Potter on the mailing lists pointed this out:

Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card.

You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd /dev node, to be able to run it this way

Another user's solution to this is the following:

Edit this file: /opt/Qtopia/etc/default/Trolltech/Storage.conf
And change the [MountPoint0] section so it resembles this:
<pre>
[MountPoint0]
Name[] = SD Card
Path=/dev/mmcblk0p1
Removable = 0
Applications = 0
Documents = 0
ContentDatabase = 0
</pre>

=== Simplified complete procedure using Ubuntu computer and microSD to USB adapter ===

This procedure was developed with:

* Ubuntu 8.10
* SanDisk microSD to USB adapter
* Qt Extended 4.4.2 2008/10/31

==== Prepare microSD card ====

Create an 8 MB partition for the kernel and use the remaining space for the root file system.

Insert microSD card into adapter, and plug adapter into Ubuntu computer. If any partitions on the microSD card mount automatically, unmount them.

CAUTION: Make sure you know which device your microSD card is. You don't want to perform these steps on your main hard disk!

<pre>
sudo umount /dev/sdb1

sudo fdisk /dev/sdb
</pre>

I assume you know how to use fdisk. Delete any existing partitions, then create two new partitions, the first of size +8M, the second using all remaining space. Set the file system type of the first partition to FAT16 (type '6'). Your partition table should look like this:

<pre>
/dev/sdb1 1 9 9040+ 6 FAT16
/dev/sdb2 10 984 982800 83 Linux
</pre>

Save your partition table and quit fdisk. Format the partitions appropriately:

<pre>
sudo mkfs.vfat /dev/sdb1
sudo mkfs.ext3 /dev/sdb2
</pre>

==== Get the latest version of Qtopia ====

Visit [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6:Qtopia] and get the appropriate file. The Qtopia ROM flash images contain both the file system and the kernel image:

<pre>
wget http://qtextended.org/modules/mydownloads/visit.php?lid=98
tar -zxvf qtextended-4.4.2-gta02-flash.tgz
</pre>

==== Copy the kernel image to the microSD card ====

First mount the first partition, which is the boot partition, of the microSD card, and make a /boot subdirectory:

<pre>
sudo mkdir /media/card
sudo mount /dev/sdb1 /media/card
sudo mkdir /media/card/boot
</pre>

Depending on your version of U-Boot, the kernel image might be expected at the root of the boot partition, or in the /boot directory. Also, the image file name might be expected to have a .bin extension, or not. We create all four variations:

<pre>
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage
</pre>

Wait for data to be written to the microSD card and unmount the first partition:

<pre>
sync
sudo umount /dev/sdb1
</pre>

==== Copy the jffs2 root file system to the microSD card ====

First we need to make a fake MTD device in RAM so that we can mount the jffs2 root file system:

<pre>
sudo modprobe mtd
sudo modprobe jffs2
sudo modprobe mtdram total_size=59024 # default is 4 MByte - set to max.
sudo modprobe mtdchar
sudo modprobe mtdblock
</pre>

Next we're going to copy onto this fake device. Make sure there are no other MTD devices on your computer and change the device numbers below as necessary:

<pre>
cat /proc/mtd
dev: size erasesize name
mtd0: 039a4000 00020000 "mtdram test device"
</pre>

Now copy the jffs2 file system to the fake MTD device:

<pre>
sudo dd if=qtextended-4.4.2-gta02-rootfs-10302135.jffs2 of=/dev/mtd0
</pre>

Create a mount point, mount the fake MTD device, and check that the contents seem right:

<pre>
sudo mkdir /mnt/tmp
sudo mount -t jffs2 /dev/mtdblock0 /mnt/tmp
ls /mnt/tmp
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Mount the second partition of the microSD card and copy the root file system to it:
copy root file system to sd card using tar

<pre>
sudo mkdir /media/rootfs
sudo mount /dev/sdb2 /media/rootfs
cd /mnt/tmp
sudo tar -cf - . | (cd /media/rootfs && sudo tar -xpvf -)
</pre>

Warnings about "implausibly old time stamp" don't seem to cause any trouble.

Use "sync" to make sure that all data is written to the microSD card:

<pre>
sync
</pre>

Inspect contents of second partition:

<pre>
ls /media/rootfs
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Note: There was a report that some versions of U-Boot cannot find the kernel image file in the first partition if a kernel image exists in the second partition boot/ directory. I have not confirmed this but there is no need for it so it seems safest to delete it now:

<pre>
sudo rm -f /media/rootfs/boot/*
</pre>

Wait for data to be written to the microSD card and unmount the second partition:

<pre>
sync
sudo umount /dev/sdb2
</pre>

==== Test Qtopia ====

Remove the microSD card from the USB adapter, install it in the Neo FreeRunner, boot into U-Boot, and select the option to boot from microSD card.

== Option 3: updating from source ==

{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:

* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)
<pre>
cd /
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz
</pre>

* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/

Since qtopia was renamed in qtextended you could find the snapshots on http://qtextended.org/downloads/snapshots/

* once dowloaded untar it
<pre>tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz</pre>
* make a "build" dir
<pre>
mkdir build
cd build
</pre>
* configure and make:
<pre>../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01
make
</pre>
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:
<pre>
make install
</pre>
will make a root directory into the ''build'' directory. There you can find an ''image'' that directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.

For compiling qt-extended 4.4.2, you may need to use the following commands:
<pre>
* cd build
* $QTOPIA_DEPOT_PATH/configure -device neo -verbose -build-qt -force-build-qt
* bin/qbuild image
</pre>

This forces building qt as well which resolved problems with the qbuild test using all the system ram.

== Booting into Qtopia ==

Now shutdown the FreeRunner

shutdown -h now

Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])

* Press and hold Power button
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.
* A boot menu will appear.
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.

Qtopia should now boot.

'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run

umount /dev/mmcblk0p2
fsck.ext3.e2fsprogs /dev/mmcblk0p2

This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.

== Internationalization ==

Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.

Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].

== Suspend /Resume ==
It seems that suspend/resume only works when the FreeRunner has been connected to a powersource (only a few seconds if sufficient). If you boot from battery, it will never suspend until you have plugged it in at least for a couple of seconds.

== Bugs ==

See [http://trolltech.org/developer/task-tracker/index_html?method=front Trolltech's tracker] ([http://trolltech.org/developer/task-tracker/index_html?method=advsearch&searchstr=&bugs=on&sugs=on&product=2&functionalarea=&versionfound=&versionfixed=&priority=-1&status=0&resolution=-1 Qtopia Tracker]).

Bug reports should be sent to qt-bugs@trolltech.com or by web form at http://trolltech.com/bugreport-form.

== Bugs in 4.4.1 ==
* Boot and Shutdown Splash will not work because splash-write was not compiled into Busybox
* Timezone & time on latest Qt 4.4.1
* The first item in a list is missing the top half

[[Category:Qtopia]]

Qtopia / Qt Extended on FreeRunner

2008-12-25T04:04:35Z

Michaelshiloh: /* Copy the jffs2 root file system to the microSD card */

{{Languages|Qtopia_on_FreeRunner}}

This page provides instructions on how to install Qtopia/Qt Extended (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.

{|align=right
|__TOC__
|}

== Current status ==

On 31 October 2008, Trolltech released the [http://qtextended.org/modules/mydownloads/visit.php?lid=98 Qtopia ROM flash image containing the rootfs] for the Openmoko Neo FreeRunner (gta02) containing the Qtopia 4.4.2 release (GPL version). This runs on the [http://qtextended.org/modules/mydownloads/visit.php?lid=91 mwebster ROM flash image containing the kernel]. At release time, 4.4.2 & current mwester's kernel mismatched, please clarify the previous sentence. Hypnotize has released [http://lists.openmoko.org/pipermail/community/2008-November/035245.html Qt Extended 4.4.2 images for the Neo FreeRunner] that work better.

This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does have a webkit based web browser and an GPS "Mapping Demo" application.

There are other third-party GPS applications available:
* [http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner xgps]
* [http://www.linux4.be/fr/roadmap.html RoadMap (experimental)]

([[TangoGPS]] does not work on QtExtended, because it depends upon an Xserver)

You can find all the Qtopia images [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 here] (including Qtextended/Qtopia 4.4 for FreeRunner and Neo1973!)

=== What is in the latest release (QtExtended 4.4.2)? ===
Qtopia 4.4 has been released with the name of [http://doc.trolltech.com/qtextended4.4/release-4-4-2.html QtExtended 4.4].
* a [http://n2.nabble.com/qtopia-update-tp832851p832888.html browser] based on webkit
* [http://n2.nabble.com/-qtopia--rotate-screen--tp841805p841841.html screen rotation in the settings application] (so no automatic rotation)
* [http://n2.nabble.com/Echo-issue-on-OM2008.08-potentially-solved-tp791642.html noise reduction]
* GPS api
* usb net/storage switching
* Gtalk support
* [http://n2.nabble.com/forum/Permalink.jtp?root=841805&post=1083388&page=y better support for non-english languages in the keyboard]

== Option 1: Flashing Qtopia to FreeRunner ==

Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]

== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==

Installation Requirements:

# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)

=== Preparing the SD card ===

See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the "Formatting the SD Card" steps, return here and execute the following:

<pre>
mount /dev/mmcblk0p1 /media/card
mkdir /media/card/boot

mkdir /media/mmcblk0p2
mount /dev/mmcblk0p2 /media/mmcblk0p2
</pre>

This will set you up properly for the installation of the root filesystem and the kernel in the steps below.

=== Installing Qtopia ===

==== Unpacking the Qtopia Root Filesystem Image ====

Download the Qtopia FLASH image from [[Latest Images#Qtopia images]] to your Linux box and extract its contents:

tar xzf qtopia-4.3.2-gta02-flash-*.tgz

You should now have two files:
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2
Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]]. However, in the mount command, substitute the image filename for "/dev/mtdblock0".

==== Creating a compressed tarball ====

Next, tar up the root filesystem:

# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .

Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted. Note the space and the period after the mountpoint.

==== Installing Root Filesystem ====

Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:

scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/

Log in to your FreeRunner and unpack the root filesystem:

<pre>
cd /media/mmcblk0p2
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm -f /media/mmcblk0p2/boot/*
</pre>

'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.

==== Installing Kernel ====

From your Linux box, rename <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> to <tt>uImage.bin</tt> and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the <tt>/media/card</tt> directory as well. There is plenty of room on the first partition to have <tt>uImage.bin</tt> in both locations.

<pre>
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin
scp uImage.bin root@192.168.0.202:/media/card/boot/
scp uImage.bin root@192.168.0.202:/media/card/
</pre>

==== Pointing Qtopia to the SD Card ====

Lorn Potter on the mailing lists pointed this out:

Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card.

You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd /dev node, to be able to run it this way

Another user's solution to this is the following:

Edit this file: /opt/Qtopia/etc/default/Trolltech/Storage.conf
And change the [MountPoint0] section so it resembles this:
<pre>
[MountPoint0]
Name[] = SD Card
Path=/dev/mmcblk0p1
Removable = 0
Applications = 0
Documents = 0
ContentDatabase = 0
</pre>

=== Simplified complete procedure using Ubuntu computer and microSD to USB adapter ===

This procedure was developed with:

* Ubuntu 8.10
* SanDisk microSD to USB adapter
* Qt Extended 4.4.2 2008/10/31

==== Prepare microSD card ====

Create an 8 MB partition for the kernel and use the remaining space for the root file system.

Insert microSD card into adapter, and plug adapter into Ubuntu computer. If any partitions on the microSD card mount automatically, unmount them.

CAUTION: Make sure you know which device your microSD card is. You don't want to perform these steps on your main hard disk!

<pre>
sudo umount /dev/sdb1

sudo fdisk /dev/sdb
</pre>

I assume you know how to use fdisk. Delete any existing partitions, then create two new partitions, the first of size +8M, the second using all remaining space. Set the file system type of the first partition to FAT16 (type '6'). Your partition table should look like this:

<pre>
/dev/sdb1 1 9 9040+ 6 FAT16
/dev/sdb2 10 984 982800 83 Linux
</pre>

Save your partition table and quit fdisk. Format the partitions appropriately:

<pre>
sudo mkfs.vfat /dev/sdb1
sudo mkfs.ext3 /dev/sdb2
</pre>

==== Get the latest version of Qtopia ====

Visit [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6:Qtopia] and get the appropriate file. The Qtopia ROM flash images contain both the file system and the kernel image:

<pre>
wget http://qtextended.org/modules/mydownloads/visit.php?lid=98
tar -zxvf qtextended-4.4.2-gta02-flash.tgz
</pre>

==== Copy the kernel image to the microSD card ====

First mount the first partition, which is the boot partition, of the microSD card, and make a /boot subdirectory:

<pre>
sudo mkdir /media/card
sudo mount /dev/sdb1 /media/card
sudo mkdir /media/card/boot
</pre>

Depending on your version of U-Boot, the kernel image might be expected at the root of the boot partition, or in the /boot directory. Also, the image file name might be expected to have a .bin extension, or not. We create all four variations:

<pre>
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage
</pre>

Wait for data to be written to the microSD card and unmount the first partition:

<pre>
sync
sudo umount /dev/sdb1
</pre>

==== Copy the jffs2 root file system to the microSD card ====

First we need to make a fake MTD device in RAM so that we can mount the jffs2 root file system:

<pre>
sudo modprobe mtd
sudo modprobe jffs2
sudo modprobe mtdram total_size=59024 # default is 4 MByte - set to max.
sudo modprobe mtdchar
sudo modprobe mtdblock
</pre>

Next we're going to copy onto this fake device. Make sure there are no other MTD devices on your computer and change the device numbers below as necessary:

<pre>
cat /proc/mtd
dev: size erasesize name
mtd0: 039a4000 00020000 "mtdram test device"
</pre>

Now copy the jffs2 file system to the fake MTD device:

<pre>
sudo dd if=qtextended-4.4.2-gta02-rootfs-10302135.jffs2 of=/dev/mtd0
</pre>

Create a mount point, mount the fake MTD device, and check that the contents seem right:

<pre>
sudo mkdir /mnt/tmp
sudo mount -t jffs2 /dev/mtdblock0 /mnt/tmp
ls /mnt/tmp
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Mount the second partition of the microSD card and copy the root file system to it:
copy root file system to sd card using tar

<pre>
sudo mkdir /media/rootfs
sudo mount /dev/sdb2 /media/rootfs
cd /mnt/tmp
sudo tar -cf - . | (cd /media/rootfs && sudo tar -xpvf -)
</pre>

Warnings about "implausibly old time stamp" don't seem to cause any trouble.

Use "sync" to make sure that all data is written to the microSD card:

<pre>
sync
</pre>

Inspect contents of second partition:

<pre>
ls /media/rootfs
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Note: There was a report that some versions of U-Boot cannot find the kernel image file in the first partition if a kernel image exists in the second partition boot/ directory. I have not confirmed this but there is no need for it so it seems safest to delete it now:

<pre>
sudo rm -f /media/rootfs/boot/*
</pre>

Wait for data to be written to the microSD card and unmount the second partition:

<pre>
sync
sudo umount /dev/sdb2
</pre>

==== Test Qtopia ====

Remove the microSD card from the USB adapter, install it in the Neo FreeRunner, boot into uBoot, and select the option to boot from microSD card.

== Option 3: updating from source ==

{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:

* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)
<pre>
cd /
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz
</pre>

* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/

Since qtopia was renamed in qtextended you could find the snapshots on http://qtextended.org/downloads/snapshots/

* once dowloaded untar it
<pre>tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz</pre>
* make a "build" dir
<pre>
mkdir build
cd build
</pre>
* configure and make:
<pre>../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01
make
</pre>
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:
<pre>
make install
</pre>
will make a root directory into the ''build'' directory. There you can find an ''image'' that directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.

For compiling qt-extended 4.4.2, you may need to use the following commands:
<pre>
* cd build
* $QTOPIA_DEPOT_PATH/configure -device neo -verbose -build-qt -force-build-qt
* bin/qbuild image
</pre>

This forces building qt as well which resolved problems with the qbuild test using all the system ram.

== Booting into Qtopia ==

Now shutdown the FreeRunner

shutdown -h now

Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])

* Press and hold Power button
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.
* A boot menu will appear.
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.

Qtopia should now boot.

'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run

umount /dev/mmcblk0p2
fsck.ext3.e2fsprogs /dev/mmcblk0p2

This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.

== Internationalization ==

Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.

Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].

== Suspend /Resume ==
It seems that suspend/resume only works when the FreeRunner has been connected to a powersource (only a few seconds if sufficient). If you boot from battery, it will never suspend until you have plugged it in at least for a couple of seconds.

== Bugs ==

See [http://trolltech.org/developer/task-tracker/index_html?method=front Trolltech's tracker] ([http://trolltech.org/developer/task-tracker/index_html?method=advsearch&searchstr=&bugs=on&sugs=on&product=2&functionalarea=&versionfound=&versionfixed=&priority=-1&status=0&resolution=-1 Qtopia Tracker]).

Bug reports should be sent to qt-bugs@trolltech.com or by web form at http://trolltech.com/bugreport-form.

== Bugs in 4.4.1 ==
* Boot and Shutdown Splash will not work because splash-write was not compiled into Busybox
* Timezone & time on latest Qt 4.4.1
* The first item in a list is missing the top half

[[Category:Qtopia]]

Qtopia / Qt Extended on FreeRunner

2008-12-25T04:03:42Z

Michaelshiloh: /* Copy the jffs2 root file system to the microSD card */

{{Languages|Qtopia_on_FreeRunner}}

This page provides instructions on how to install Qtopia/Qt Extended (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.

{|align=right
|__TOC__
|}

== Current status ==

On 31 October 2008, Trolltech released the [http://qtextended.org/modules/mydownloads/visit.php?lid=98 Qtopia ROM flash image containing the rootfs] for the Openmoko Neo FreeRunner (gta02) containing the Qtopia 4.4.2 release (GPL version). This runs on the [http://qtextended.org/modules/mydownloads/visit.php?lid=91 mwebster ROM flash image containing the kernel]. At release time, 4.4.2 & current mwester's kernel mismatched, please clarify the previous sentence. Hypnotize has released [http://lists.openmoko.org/pipermail/community/2008-November/035245.html Qt Extended 4.4.2 images for the Neo FreeRunner] that work better.

This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does have a webkit based web browser and an GPS "Mapping Demo" application.

There are other third-party GPS applications available:
* [http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner xgps]
* [http://www.linux4.be/fr/roadmap.html RoadMap (experimental)]

([[TangoGPS]] does not work on QtExtended, because it depends upon an Xserver)

You can find all the Qtopia images [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 here] (including Qtextended/Qtopia 4.4 for FreeRunner and Neo1973!)

=== What is in the latest release (QtExtended 4.4.2)? ===
Qtopia 4.4 has been released with the name of [http://doc.trolltech.com/qtextended4.4/release-4-4-2.html QtExtended 4.4].
* a [http://n2.nabble.com/qtopia-update-tp832851p832888.html browser] based on webkit
* [http://n2.nabble.com/-qtopia--rotate-screen--tp841805p841841.html screen rotation in the settings application] (so no automatic rotation)
* [http://n2.nabble.com/Echo-issue-on-OM2008.08-potentially-solved-tp791642.html noise reduction]
* GPS api
* usb net/storage switching
* Gtalk support
* [http://n2.nabble.com/forum/Permalink.jtp?root=841805&post=1083388&page=y better support for non-english languages in the keyboard]

== Option 1: Flashing Qtopia to FreeRunner ==

Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]

== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==

Installation Requirements:

# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)

=== Preparing the SD card ===

See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the "Formatting the SD Card" steps, return here and execute the following:

<pre>
mount /dev/mmcblk0p1 /media/card
mkdir /media/card/boot

mkdir /media/mmcblk0p2
mount /dev/mmcblk0p2 /media/mmcblk0p2
</pre>

This will set you up properly for the installation of the root filesystem and the kernel in the steps below.

=== Installing Qtopia ===

==== Unpacking the Qtopia Root Filesystem Image ====

Download the Qtopia FLASH image from [[Latest Images#Qtopia images]] to your Linux box and extract its contents:

tar xzf qtopia-4.3.2-gta02-flash-*.tgz

You should now have two files:
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2
Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]]. However, in the mount command, substitute the image filename for "/dev/mtdblock0".

==== Creating a compressed tarball ====

Next, tar up the root filesystem:

# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .

Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted. Note the space and the period after the mountpoint.

==== Installing Root Filesystem ====

Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:

scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/

Log in to your FreeRunner and unpack the root filesystem:

<pre>
cd /media/mmcblk0p2
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm -f /media/mmcblk0p2/boot/*
</pre>

'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.

==== Installing Kernel ====

From your Linux box, rename <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> to <tt>uImage.bin</tt> and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the <tt>/media/card</tt> directory as well. There is plenty of room on the first partition to have <tt>uImage.bin</tt> in both locations.

<pre>
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin
scp uImage.bin root@192.168.0.202:/media/card/boot/
scp uImage.bin root@192.168.0.202:/media/card/
</pre>

==== Pointing Qtopia to the SD Card ====

Lorn Potter on the mailing lists pointed this out:

Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card.

You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd /dev node, to be able to run it this way

Another user's solution to this is the following:

Edit this file: /opt/Qtopia/etc/default/Trolltech/Storage.conf
And change the [MountPoint0] section so it resembles this:
<pre>
[MountPoint0]
Name[] = SD Card
Path=/dev/mmcblk0p1
Removable = 0
Applications = 0
Documents = 0
ContentDatabase = 0
</pre>

=== Simplified complete procedure using Ubuntu computer and microSD to USB adapter ===

This procedure was developed with:

* Ubuntu 8.10
* SanDisk microSD to USB adapter
* Qt Extended 4.4.2 2008/10/31

==== Prepare microSD card ====

Create an 8 MB partition for the kernel and use the remaining space for the root file system.

Insert microSD card into adapter, and plug adapter into Ubuntu computer. If any partitions on the microSD card mount automatically, unmount them.

CAUTION: Make sure you know which device your microSD card is. You don't want to perform these steps on your main hard disk!

<pre>
sudo umount /dev/sdb1

sudo fdisk /dev/sdb
</pre>

I assume you know how to use fdisk. Delete any existing partitions, then create two new partitions, the first of size +8M, the second using all remaining space. Set the file system type of the first partition to FAT16 (type '6'). Your partition table should look like this:

<pre>
/dev/sdb1 1 9 9040+ 6 FAT16
/dev/sdb2 10 984 982800 83 Linux
</pre>

Save your partition table and quit fdisk. Format the partitions appropriately:

<pre>
sudo mkfs.vfat /dev/sdb1
sudo mkfs.ext3 /dev/sdb2
</pre>

==== Get the latest version of Qtopia ====

Visit [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6:Qtopia] and get the appropriate file. The Qtopia ROM flash images contain both the file system and the kernel image:

<pre>
wget http://qtextended.org/modules/mydownloads/visit.php?lid=98
tar -zxvf qtextended-4.4.2-gta02-flash.tgz
</pre>

==== Copy the kernel image to the microSD card ====

First mount the first partition, which is the boot partition, of the microSD card, and make a /boot subdirectory:

<pre>
sudo mkdir /media/card
sudo mount /dev/sdb1 /media/card
sudo mkdir /media/card/boot
</pre>

Depending on your version of U-Boot, the kernel image might be expected at the root of the boot partition, or in the /boot directory. Also, the image file name might be expected to have a .bin extension, or not. We create all four variations:

<pre>
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage
</pre>

Wait for data to be written to the microSD card and unmount the first partition:

<pre>
sync
sudo umount /dev/sdb1
</pre>

==== Copy the jffs2 root file system to the microSD card ====

First we need to make a fake MTD device in RAM so that we can mount the jffs2 root file system:

<pre>
sudo modprobe mtd
sudo modprobe jffs2
sudo modprobe mtdram total_size=59024 # default is 4 MByte - set to max.
sudo modprobe mtdchar
sudo modprobe mtdblock
</pre>

Next we're going to copy onto this fake device. Make sure there are no other MTD devices on your computer and change the device numbers below as necessary:

<pre>
cat /proc/mtd
dev: size erasesize name
mtd0: 039a4000 00020000 "mtdram test device"
</pre>

Now copy the jffs2 file system to the fake MTD device:

<pre>
sudo dd if=qtextended-4.4.2-gta02-rootfs-10302135.jffs2 of=/dev/mtd0
</pre>

Create a mount point, mount the fake MTD device, and check that the contents seem right:

<pre>
sudo mkdir /mnt/tmp
sudo mount -t jffs2 /dev/mtdblock0 /mnt/tmp
ls /mnt/tmp
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Mount the second partition of the microSD card and copy the root file system to it:
copy root file system to sd card using tar

<pre>
sudo mkdir /media/rootfs
sudo mount /dev/sdb2 /media/rootfs
cd /mnt/tmp
sudo tar -cf - . | (cd /media/rootfs && sudo tar -xpvf -)
</pre>

Warnings about "implausibly old time stamp" don't seem to cause any trouble.

Use "sync" to make sure that all data is written to the microSD card:

<pre>
sync
</pre>

Inspect contents of second partition:

<pre>
ls /media/rootfs
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Note: There was a report that some versions of U-Boot cannot find the kernel image file in the first partition if a kernel image exists in the second partition boot/ directory. I have not confirmed this but there is no need for it so it seems safest to delete it now:

<pre>
sudo rm -f /media/rootfs/boot/*
</pre>

Wait for data to be written to the microSD card and unmount the second partition:

<pre>
sync
umount /dev/sdb2
</pre>

==== Test Qtopia ====

Remove the microSD card from the USB adapter, install it in the Neo FreeRunner, boot into uBoot, and select the option to boot from microSD card.

== Option 3: updating from source ==

{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:

* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)
<pre>
cd /
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz
</pre>

* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/

Since qtopia was renamed in qtextended you could find the snapshots on http://qtextended.org/downloads/snapshots/

* once dowloaded untar it
<pre>tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz</pre>
* make a "build" dir
<pre>
mkdir build
cd build
</pre>
* configure and make:
<pre>../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01
make
</pre>
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:
<pre>
make install
</pre>
will make a root directory into the ''build'' directory. There you can find an ''image'' that directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.

For compiling qt-extended 4.4.2, you may need to use the following commands:
<pre>
* cd build
* $QTOPIA_DEPOT_PATH/configure -device neo -verbose -build-qt -force-build-qt
* bin/qbuild image
</pre>

This forces building qt as well which resolved problems with the qbuild test using all the system ram.

== Booting into Qtopia ==

Now shutdown the FreeRunner

shutdown -h now

Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])

* Press and hold Power button
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.
* A boot menu will appear.
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.

Qtopia should now boot.

'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run

umount /dev/mmcblk0p2
fsck.ext3.e2fsprogs /dev/mmcblk0p2

This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.

== Internationalization ==

Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.

Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].

== Suspend /Resume ==
It seems that suspend/resume only works when the FreeRunner has been connected to a powersource (only a few seconds if sufficient). If you boot from battery, it will never suspend until you have plugged it in at least for a couple of seconds.

== Bugs ==

See [http://trolltech.org/developer/task-tracker/index_html?method=front Trolltech's tracker] ([http://trolltech.org/developer/task-tracker/index_html?method=advsearch&searchstr=&bugs=on&sugs=on&product=2&functionalarea=&versionfound=&versionfixed=&priority=-1&status=0&resolution=-1 Qtopia Tracker]).

Bug reports should be sent to qt-bugs@trolltech.com or by web form at http://trolltech.com/bugreport-form.

== Bugs in 4.4.1 ==
* Boot and Shutdown Splash will not work because splash-write was not compiled into Busybox
* Timezone & time on latest Qt 4.4.1
* The first item in a list is missing the top half

[[Category:Qtopia]]

Qtopia / Qt Extended on FreeRunner

2008-12-25T04:02:28Z

Michaelshiloh: /* Copy the jffs2 root file system to the microSD card */

{{Languages|Qtopia_on_FreeRunner}}

This page provides instructions on how to install Qtopia/Qt Extended (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.

{|align=right
|__TOC__
|}

== Current status ==

On 31 October 2008, Trolltech released the [http://qtextended.org/modules/mydownloads/visit.php?lid=98 Qtopia ROM flash image containing the rootfs] for the Openmoko Neo FreeRunner (gta02) containing the Qtopia 4.4.2 release (GPL version). This runs on the [http://qtextended.org/modules/mydownloads/visit.php?lid=91 mwebster ROM flash image containing the kernel]. At release time, 4.4.2 & current mwester's kernel mismatched, please clarify the previous sentence. Hypnotize has released [http://lists.openmoko.org/pipermail/community/2008-November/035245.html Qt Extended 4.4.2 images for the Neo FreeRunner] that work better.

This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does have a webkit based web browser and an GPS "Mapping Demo" application.

There are other third-party GPS applications available:
* [http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner xgps]
* [http://www.linux4.be/fr/roadmap.html RoadMap (experimental)]

([[TangoGPS]] does not work on QtExtended, because it depends upon an Xserver)

You can find all the Qtopia images [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 here] (including Qtextended/Qtopia 4.4 for FreeRunner and Neo1973!)

=== What is in the latest release (QtExtended 4.4.2)? ===
Qtopia 4.4 has been released with the name of [http://doc.trolltech.com/qtextended4.4/release-4-4-2.html QtExtended 4.4].
* a [http://n2.nabble.com/qtopia-update-tp832851p832888.html browser] based on webkit
* [http://n2.nabble.com/-qtopia--rotate-screen--tp841805p841841.html screen rotation in the settings application] (so no automatic rotation)
* [http://n2.nabble.com/Echo-issue-on-OM2008.08-potentially-solved-tp791642.html noise reduction]
* GPS api
* usb net/storage switching
* Gtalk support
* [http://n2.nabble.com/forum/Permalink.jtp?root=841805&post=1083388&page=y better support for non-english languages in the keyboard]

== Option 1: Flashing Qtopia to FreeRunner ==

Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]

== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==

Installation Requirements:

# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)

=== Preparing the SD card ===

See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the "Formatting the SD Card" steps, return here and execute the following:

<pre>
mount /dev/mmcblk0p1 /media/card
mkdir /media/card/boot

mkdir /media/mmcblk0p2
mount /dev/mmcblk0p2 /media/mmcblk0p2
</pre>

This will set you up properly for the installation of the root filesystem and the kernel in the steps below.

=== Installing Qtopia ===

==== Unpacking the Qtopia Root Filesystem Image ====

Download the Qtopia FLASH image from [[Latest Images#Qtopia images]] to your Linux box and extract its contents:

tar xzf qtopia-4.3.2-gta02-flash-*.tgz

You should now have two files:
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2
Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]]. However, in the mount command, substitute the image filename for "/dev/mtdblock0".

==== Creating a compressed tarball ====

Next, tar up the root filesystem:

# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .

Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted. Note the space and the period after the mountpoint.

==== Installing Root Filesystem ====

Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:

scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/

Log in to your FreeRunner and unpack the root filesystem:

<pre>
cd /media/mmcblk0p2
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm -f /media/mmcblk0p2/boot/*
</pre>

'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.

==== Installing Kernel ====

From your Linux box, rename <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> to <tt>uImage.bin</tt> and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the <tt>/media/card</tt> directory as well. There is plenty of room on the first partition to have <tt>uImage.bin</tt> in both locations.

<pre>
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin
scp uImage.bin root@192.168.0.202:/media/card/boot/
scp uImage.bin root@192.168.0.202:/media/card/
</pre>

==== Pointing Qtopia to the SD Card ====

Lorn Potter on the mailing lists pointed this out:

Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card.

You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd /dev node, to be able to run it this way

Another user's solution to this is the following:

Edit this file: /opt/Qtopia/etc/default/Trolltech/Storage.conf
And change the [MountPoint0] section so it resembles this:
<pre>
[MountPoint0]
Name[] = SD Card
Path=/dev/mmcblk0p1
Removable = 0
Applications = 0
Documents = 0
ContentDatabase = 0
</pre>

=== Simplified complete procedure using Ubuntu computer and microSD to USB adapter ===

This procedure was developed with:

* Ubuntu 8.10
* SanDisk microSD to USB adapter
* Qt Extended 4.4.2 2008/10/31

==== Prepare microSD card ====

Create an 8 MB partition for the kernel and use the remaining space for the root file system.

Insert microSD card into adapter, and plug adapter into Ubuntu computer. If any partitions on the microSD card mount automatically, unmount them.

CAUTION: Make sure you know which device your microSD card is. You don't want to perform these steps on your main hard disk!

<pre>
sudo umount /dev/sdb1

sudo fdisk /dev/sdb
</pre>

I assume you know how to use fdisk. Delete any existing partitions, then create two new partitions, the first of size +8M, the second using all remaining space. Set the file system type of the first partition to FAT16 (type '6'). Your partition table should look like this:

<pre>
/dev/sdb1 1 9 9040+ 6 FAT16
/dev/sdb2 10 984 982800 83 Linux
</pre>

Save your partition table and quit fdisk. Format the partitions appropriately:

<pre>
sudo mkfs.vfat /dev/sdb1
sudo mkfs.ext3 /dev/sdb2
</pre>

==== Get the latest version of Qtopia ====

Visit [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6:Qtopia] and get the appropriate file. The Qtopia ROM flash images contain both the file system and the kernel image:

<pre>
wget http://qtextended.org/modules/mydownloads/visit.php?lid=98
tar -zxvf qtextended-4.4.2-gta02-flash.tgz
</pre>

==== Copy the kernel image to the microSD card ====

First mount the first partition, which is the boot partition, of the microSD card, and make a /boot subdirectory:

<pre>
sudo mkdir /media/card
sudo mount /dev/sdb1 /media/card
sudo mkdir /media/card/boot
</pre>

Depending on your version of U-Boot, the kernel image might be expected at the root of the boot partition, or in the /boot directory. Also, the image file name might be expected to have a .bin extension, or not. We create all four variations:

<pre>
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage
</pre>

Wait for data to be written to the microSD card and unmount the first partition:

<pre>
sync
sudo umount /dev/sdb1
</pre>

==== Copy the jffs2 root file system to the microSD card ====

First we need to make a fake MTD device in RAM so that we can mount the jffs2 root file system:

<pre>
sudo modprobe mtd
sudo modprobe jffs2
sudo modprobe mtdram total_size=59024 # default is 4 MByte - set to max.
sudo modprobe mtdchar
sudo modprobe mtdblock
</pre>

Next we're going to copy onto this fake device. Make sure there are no other MTD devices on your computer and change the device numbers below as necessary:

<pre>
cat /proc/mtd
dev: size erasesize name
mtd0: 039a4000 00020000 "mtdram test device"
</pre>

Now copy the jffs2 file system to the fake MTD device:

<pre>
sudo dd if=qtextended-4.4.2-gta02-rootfs-10302135.jffs2 of=/dev/mtd0
</pre>

Create a mount point, mount the fake MTD device, and check that the contents seem right:

<pre>
sudo mkdir /mnt/tmp
sudo mount -t jffs2 /dev/mtdblock0 /mnt/tmp
ls /mnt/tmp
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Mount the second partition of the microSD card and copy the root file system to it:
copy root file system to sd card using tar

<pre>
sudo mkdir /media/rootfs
sudo mount /dev/sdb2 /media/rootfs
cd /mnt/tmp
sudo tar -cf - . | (cd /media/rootfs && sudo tar -xpvf -)
</pre>

Warnings about "implausibly old time stamp" don't seem to cause any trouble.

Use "sync" to make sure that all data is written to the microSD card:

<pre>
sync
</pre>

Inspect contents of second partition:

<pre>
ls /media/rootfs
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Note: There was a report that some versions of U-Boot cannot find the kernel image file in the first partition if a kernel image exists in the second partition boot/ directory. I have not confirmed this but there is no need for it so it seems safest to delete it now:

<pre>
sudo rm -f /media/rootfs/boot/*
<pre>

Wait for data to be written to the microSD card and unmount the second partition:

<pre>
sync
umount /dev/sdb2
</pre>

==== Test Qtopia ====

Remove the microSD card from the USB adapter, install it in the Neo FreeRunner, boot into uBoot, and select the option to boot from microSD card.

== Option 3: updating from source ==

{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:

* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)
<pre>
cd /
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz
</pre>

* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/

Since qtopia was renamed in qtextended you could find the snapshots on http://qtextended.org/downloads/snapshots/

* once dowloaded untar it
<pre>tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz</pre>
* make a "build" dir
<pre>
mkdir build
cd build
</pre>
* configure and make:
<pre>../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01
make
</pre>
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:
<pre>
make install
</pre>
will make a root directory into the ''build'' directory. There you can find an ''image'' that directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.

For compiling qt-extended 4.4.2, you may need to use the following commands:
<pre>
* cd build
* $QTOPIA_DEPOT_PATH/configure -device neo -verbose -build-qt -force-build-qt
* bin/qbuild image
</pre>

This forces building qt as well which resolved problems with the qbuild test using all the system ram.

== Booting into Qtopia ==

Now shutdown the FreeRunner

shutdown -h now

Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])

* Press and hold Power button
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.
* A boot menu will appear.
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.

Qtopia should now boot.

'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run

umount /dev/mmcblk0p2
fsck.ext3.e2fsprogs /dev/mmcblk0p2

This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.

== Internationalization ==

Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.

Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].

== Suspend /Resume ==
It seems that suspend/resume only works when the FreeRunner has been connected to a powersource (only a few seconds if sufficient). If you boot from battery, it will never suspend until you have plugged it in at least for a couple of seconds.

== Bugs ==

See [http://trolltech.org/developer/task-tracker/index_html?method=front Trolltech's tracker] ([http://trolltech.org/developer/task-tracker/index_html?method=advsearch&searchstr=&bugs=on&sugs=on&product=2&functionalarea=&versionfound=&versionfixed=&priority=-1&status=0&resolution=-1 Qtopia Tracker]).

Bug reports should be sent to qt-bugs@trolltech.com or by web form at http://trolltech.com/bugreport-form.

== Bugs in 4.4.1 ==
* Boot and Shutdown Splash will not work because splash-write was not compiled into Busybox
* Timezone & time on latest Qt 4.4.1
* The first item in a list is missing the top half

[[Category:Qtopia]]

Qtopia / Qt Extended on FreeRunner

2008-12-25T03:58:17Z

Michaelshiloh: /* Copy the kernel image to the microSD card */

{{Languages|Qtopia_on_FreeRunner}}

This page provides instructions on how to install Qtopia/Qt Extended (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.

{|align=right
|__TOC__
|}

== Current status ==

On 31 October 2008, Trolltech released the [http://qtextended.org/modules/mydownloads/visit.php?lid=98 Qtopia ROM flash image containing the rootfs] for the Openmoko Neo FreeRunner (gta02) containing the Qtopia 4.4.2 release (GPL version). This runs on the [http://qtextended.org/modules/mydownloads/visit.php?lid=91 mwebster ROM flash image containing the kernel]. At release time, 4.4.2 & current mwester's kernel mismatched, please clarify the previous sentence. Hypnotize has released [http://lists.openmoko.org/pipermail/community/2008-November/035245.html Qt Extended 4.4.2 images for the Neo FreeRunner] that work better.

This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does have a webkit based web browser and an GPS "Mapping Demo" application.

There are other third-party GPS applications available:
* [http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner xgps]
* [http://www.linux4.be/fr/roadmap.html RoadMap (experimental)]

([[TangoGPS]] does not work on QtExtended, because it depends upon an Xserver)

You can find all the Qtopia images [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 here] (including Qtextended/Qtopia 4.4 for FreeRunner and Neo1973!)

=== What is in the latest release (QtExtended 4.4.2)? ===
Qtopia 4.4 has been released with the name of [http://doc.trolltech.com/qtextended4.4/release-4-4-2.html QtExtended 4.4].
* a [http://n2.nabble.com/qtopia-update-tp832851p832888.html browser] based on webkit
* [http://n2.nabble.com/-qtopia--rotate-screen--tp841805p841841.html screen rotation in the settings application] (so no automatic rotation)
* [http://n2.nabble.com/Echo-issue-on-OM2008.08-potentially-solved-tp791642.html noise reduction]
* GPS api
* usb net/storage switching
* Gtalk support
* [http://n2.nabble.com/forum/Permalink.jtp?root=841805&post=1083388&page=y better support for non-english languages in the keyboard]

== Option 1: Flashing Qtopia to FreeRunner ==

Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]

== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==

Installation Requirements:

# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)

=== Preparing the SD card ===

See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the "Formatting the SD Card" steps, return here and execute the following:

<pre>
mount /dev/mmcblk0p1 /media/card
mkdir /media/card/boot

mkdir /media/mmcblk0p2
mount /dev/mmcblk0p2 /media/mmcblk0p2
</pre>

This will set you up properly for the installation of the root filesystem and the kernel in the steps below.

=== Installing Qtopia ===

==== Unpacking the Qtopia Root Filesystem Image ====

Download the Qtopia FLASH image from [[Latest Images#Qtopia images]] to your Linux box and extract its contents:

tar xzf qtopia-4.3.2-gta02-flash-*.tgz

You should now have two files:
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2
Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]]. However, in the mount command, substitute the image filename for "/dev/mtdblock0".

==== Creating a compressed tarball ====

Next, tar up the root filesystem:

# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .

Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted. Note the space and the period after the mountpoint.

==== Installing Root Filesystem ====

Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:

scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/

Log in to your FreeRunner and unpack the root filesystem:

<pre>
cd /media/mmcblk0p2
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm -f /media/mmcblk0p2/boot/*
</pre>

'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.

==== Installing Kernel ====

From your Linux box, rename <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> to <tt>uImage.bin</tt> and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the <tt>/media/card</tt> directory as well. There is plenty of room on the first partition to have <tt>uImage.bin</tt> in both locations.

<pre>
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin
scp uImage.bin root@192.168.0.202:/media/card/boot/
scp uImage.bin root@192.168.0.202:/media/card/
</pre>

==== Pointing Qtopia to the SD Card ====

Lorn Potter on the mailing lists pointed this out:

Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card.

You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd /dev node, to be able to run it this way

Another user's solution to this is the following:

Edit this file: /opt/Qtopia/etc/default/Trolltech/Storage.conf
And change the [MountPoint0] section so it resembles this:
<pre>
[MountPoint0]
Name[] = SD Card
Path=/dev/mmcblk0p1
Removable = 0
Applications = 0
Documents = 0
ContentDatabase = 0
</pre>

=== Simplified complete procedure using Ubuntu computer and microSD to USB adapter ===

This procedure was developed with:

* Ubuntu 8.10
* SanDisk microSD to USB adapter
* Qt Extended 4.4.2 2008/10/31

==== Prepare microSD card ====

Create an 8 MB partition for the kernel and use the remaining space for the root file system.

Insert microSD card into adapter, and plug adapter into Ubuntu computer. If any partitions on the microSD card mount automatically, unmount them.

CAUTION: Make sure you know which device your microSD card is. You don't want to perform these steps on your main hard disk!

<pre>
sudo umount /dev/sdb1

sudo fdisk /dev/sdb
</pre>

I assume you know how to use fdisk. Delete any existing partitions, then create two new partitions, the first of size +8M, the second using all remaining space. Set the file system type of the first partition to FAT16 (type '6'). Your partition table should look like this:

<pre>
/dev/sdb1 1 9 9040+ 6 FAT16
/dev/sdb2 10 984 982800 83 Linux
</pre>

Save your partition table and quit fdisk. Format the partitions appropriately:

<pre>
sudo mkfs.vfat /dev/sdb1
sudo mkfs.ext3 /dev/sdb2
</pre>

==== Get the latest version of Qtopia ====

Visit [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6:Qtopia] and get the appropriate file. The Qtopia ROM flash images contain both the file system and the kernel image:

<pre>
wget http://qtextended.org/modules/mydownloads/visit.php?lid=98
tar -zxvf qtextended-4.4.2-gta02-flash.tgz
</pre>

==== Copy the kernel image to the microSD card ====

First mount the first partition, which is the boot partition, of the microSD card, and make a /boot subdirectory:

<pre>
sudo mkdir /media/card
sudo mount /dev/sdb1 /media/card
sudo mkdir /media/card/boot
</pre>

Depending on your version of U-Boot, the kernel image might be expected at the root of the boot partition, or in the /boot directory. Also, the image file name might be expected to have a .bin extension, or not. We create all four variations:

<pre>
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage
</pre>

Wait for data to be written to the microSD card and unmount the first partition:

<pre>
sync
sudo umount /dev/sdb1
</pre>

==== Copy the jffs2 root file system to the microSD card ====

First we need to make a fake MTD device in RAM so that we can mount the jffs2 root file system:

<pre>
sudo modprobe mtd
sudo modprobe jffs2
sudo modprobe mtdram total_size=59024 # default is 4 MByte - set to max.
sudo modprobe mtdchar
sudo modprobe mtdblock
</pre>

Next we're going to copy onto this fake device. Make sure there are no other MTD devices on your computer and change the device numbers below as necessary:

<pre>
cat /proc/mtd
dev: size erasesize name
mtd0: 039a4000 00020000 "mtdram test device"
</pre>

Now copy the jffs2 file system to the fake MTD device:

<pre>
sudo dd if=qtextended-4.4.2-gta02-rootfs-10302135.jffs2 of=/dev/mtd0
</pre>

Create a mount point, mount the fake MTD device, and check that the contents seem right:

<pre>
sudo mkdir /mnt/tmp
sudo mount -t jffs2 /dev/mtdblock0 /mnt/tmp
ls /mnt/tmp
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Mount the second partition of the microSD card and copy the root file system to it:
copy root file system to sd card using tar

<pre>
sudo mkdir /media/rootfs
sudo mount /dev/sdb2 /media/rootfs
cd /mnt/tmp
sudo tar -cf - . | (cd /media/rootfs && sudo tar -xpvf -)
</pre>

Use "sync" to make sure that all data is written to the microSD card:

<pre>
sync
</pre>

Inspect contents of second partition:

<pre>
ls /media/rootfs
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Note: There was a report that some versions of U-Boot cannot find the kernel image file in the first partition if a kernel image exists in the second partition boot/ directory. I have not confirmed this but there is no need for it so it seems safest to delete it now:

<pre>
sudo rm -f /media/rootfs/boot/*
<pre>

Wait for data to be written to the microSD card and unmount the second partition:

<pre>
sync
umount /dev/sdb2
</pre>

==== Test Qtopia ====

Remove the microSD card from the USB adapter, install it in the Neo FreeRunner, boot into uBoot, and select the option to boot from microSD card.

== Option 3: updating from source ==

{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:

* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)
<pre>
cd /
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz
</pre>

* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/

Since qtopia was renamed in qtextended you could find the snapshots on http://qtextended.org/downloads/snapshots/

* once dowloaded untar it
<pre>tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz</pre>
* make a "build" dir
<pre>
mkdir build
cd build
</pre>
* configure and make:
<pre>../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01
make
</pre>
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:
<pre>
make install
</pre>
will make a root directory into the ''build'' directory. There you can find an ''image'' that directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.

For compiling qt-extended 4.4.2, you may need to use the following commands:
<pre>
* cd build
* $QTOPIA_DEPOT_PATH/configure -device neo -verbose -build-qt -force-build-qt
* bin/qbuild image
</pre>

This forces building qt as well which resolved problems with the qbuild test using all the system ram.

== Booting into Qtopia ==

Now shutdown the FreeRunner

shutdown -h now

Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])

* Press and hold Power button
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.
* A boot menu will appear.
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.

Qtopia should now boot.

'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run

umount /dev/mmcblk0p2
fsck.ext3.e2fsprogs /dev/mmcblk0p2

This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.

== Internationalization ==

Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.

Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].

== Suspend /Resume ==
It seems that suspend/resume only works when the FreeRunner has been connected to a powersource (only a few seconds if sufficient). If you boot from battery, it will never suspend until you have plugged it in at least for a couple of seconds.

== Bugs ==

See [http://trolltech.org/developer/task-tracker/index_html?method=front Trolltech's tracker] ([http://trolltech.org/developer/task-tracker/index_html?method=advsearch&searchstr=&bugs=on&sugs=on&product=2&functionalarea=&versionfound=&versionfixed=&priority=-1&status=0&resolution=-1 Qtopia Tracker]).

Bug reports should be sent to qt-bugs@trolltech.com or by web form at http://trolltech.com/bugreport-form.

== Bugs in 4.4.1 ==
* Boot and Shutdown Splash will not work because splash-write was not compiled into Busybox
* Timezone & time on latest Qt 4.4.1
* The first item in a list is missing the top half

[[Category:Qtopia]]

Qtopia / Qt Extended on FreeRunner

2008-12-25T03:57:51Z

Michaelshiloh: /* Copy the kernel image to the microSD card */

{{Languages|Qtopia_on_FreeRunner}}

This page provides instructions on how to install Qtopia/Qt Extended (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.

{|align=right
|__TOC__
|}

== Current status ==

On 31 October 2008, Trolltech released the [http://qtextended.org/modules/mydownloads/visit.php?lid=98 Qtopia ROM flash image containing the rootfs] for the Openmoko Neo FreeRunner (gta02) containing the Qtopia 4.4.2 release (GPL version). This runs on the [http://qtextended.org/modules/mydownloads/visit.php?lid=91 mwebster ROM flash image containing the kernel]. At release time, 4.4.2 & current mwester's kernel mismatched, please clarify the previous sentence. Hypnotize has released [http://lists.openmoko.org/pipermail/community/2008-November/035245.html Qt Extended 4.4.2 images for the Neo FreeRunner] that work better.

This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does have a webkit based web browser and an GPS "Mapping Demo" application.

There are other third-party GPS applications available:
* [http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner xgps]
* [http://www.linux4.be/fr/roadmap.html RoadMap (experimental)]

([[TangoGPS]] does not work on QtExtended, because it depends upon an Xserver)

You can find all the Qtopia images [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 here] (including Qtextended/Qtopia 4.4 for FreeRunner and Neo1973!)

=== What is in the latest release (QtExtended 4.4.2)? ===
Qtopia 4.4 has been released with the name of [http://doc.trolltech.com/qtextended4.4/release-4-4-2.html QtExtended 4.4].
* a [http://n2.nabble.com/qtopia-update-tp832851p832888.html browser] based on webkit
* [http://n2.nabble.com/-qtopia--rotate-screen--tp841805p841841.html screen rotation in the settings application] (so no automatic rotation)
* [http://n2.nabble.com/Echo-issue-on-OM2008.08-potentially-solved-tp791642.html noise reduction]
* GPS api
* usb net/storage switching
* Gtalk support
* [http://n2.nabble.com/forum/Permalink.jtp?root=841805&post=1083388&page=y better support for non-english languages in the keyboard]

== Option 1: Flashing Qtopia to FreeRunner ==

Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]

== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==

Installation Requirements:

# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)

=== Preparing the SD card ===

See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the "Formatting the SD Card" steps, return here and execute the following:

<pre>
mount /dev/mmcblk0p1 /media/card
mkdir /media/card/boot

mkdir /media/mmcblk0p2
mount /dev/mmcblk0p2 /media/mmcblk0p2
</pre>

This will set you up properly for the installation of the root filesystem and the kernel in the steps below.

=== Installing Qtopia ===

==== Unpacking the Qtopia Root Filesystem Image ====

Download the Qtopia FLASH image from [[Latest Images#Qtopia images]] to your Linux box and extract its contents:

tar xzf qtopia-4.3.2-gta02-flash-*.tgz

You should now have two files:
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2
Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]]. However, in the mount command, substitute the image filename for "/dev/mtdblock0".

==== Creating a compressed tarball ====

Next, tar up the root filesystem:

# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .

Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted. Note the space and the period after the mountpoint.

==== Installing Root Filesystem ====

Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:

scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/

Log in to your FreeRunner and unpack the root filesystem:

<pre>
cd /media/mmcblk0p2
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm -f /media/mmcblk0p2/boot/*
</pre>

'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.

==== Installing Kernel ====

From your Linux box, rename <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> to <tt>uImage.bin</tt> and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the <tt>/media/card</tt> directory as well. There is plenty of room on the first partition to have <tt>uImage.bin</tt> in both locations.

<pre>
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin
scp uImage.bin root@192.168.0.202:/media/card/boot/
scp uImage.bin root@192.168.0.202:/media/card/
</pre>

==== Pointing Qtopia to the SD Card ====

Lorn Potter on the mailing lists pointed this out:

Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card.

You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd /dev node, to be able to run it this way

Another user's solution to this is the following:

Edit this file: /opt/Qtopia/etc/default/Trolltech/Storage.conf
And change the [MountPoint0] section so it resembles this:
<pre>
[MountPoint0]
Name[] = SD Card
Path=/dev/mmcblk0p1
Removable = 0
Applications = 0
Documents = 0
ContentDatabase = 0
</pre>

=== Simplified complete procedure using Ubuntu computer and microSD to USB adapter ===

This procedure was developed with:

* Ubuntu 8.10
* SanDisk microSD to USB adapter
* Qt Extended 4.4.2 2008/10/31

==== Prepare microSD card ====

Create an 8 MB partition for the kernel and use the remaining space for the root file system.

Insert microSD card into adapter, and plug adapter into Ubuntu computer. If any partitions on the microSD card mount automatically, unmount them.

CAUTION: Make sure you know which device your microSD card is. You don't want to perform these steps on your main hard disk!

<pre>
sudo umount /dev/sdb1

sudo fdisk /dev/sdb
</pre>

I assume you know how to use fdisk. Delete any existing partitions, then create two new partitions, the first of size +8M, the second using all remaining space. Set the file system type of the first partition to FAT16 (type '6'). Your partition table should look like this:

<pre>
/dev/sdb1 1 9 9040+ 6 FAT16
/dev/sdb2 10 984 982800 83 Linux
</pre>

Save your partition table and quit fdisk. Format the partitions appropriately:

<pre>
sudo mkfs.vfat /dev/sdb1
sudo mkfs.ext3 /dev/sdb2
</pre>

==== Get the latest version of Qtopia ====

Visit [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6:Qtopia] and get the appropriate file. The Qtopia ROM flash images contain both the file system and the kernel image:

<pre>
wget http://qtextended.org/modules/mydownloads/visit.php?lid=98
tar -zxvf qtextended-4.4.2-gta02-flash.tgz
</pre>

==== Copy the kernel image to the microSD card ====

First mount the first partition, which is the boot partition, of the microSD card, and make a /boot subdirectory:

<pre>
sudo mkdir /media/card
sudo mount /dev/sdb1 /media/card
sudo mkdir /media/card/boot
</pre>

Depending on your version of U-Boot, the kernel image might be expected at the root of the boot partition, or in the /boot directory. Also, the image file name might be expected to have a .bin extension, or not. We create all four variations:

<pre>
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage
</pre>

Wait for data to be written to the microSD card and unmount the first partition:

<pre>
sync
sudo umount /dev/sdb2
</pre>

==== Copy the jffs2 root file system to the microSD card ====

First we need to make a fake MTD device in RAM so that we can mount the jffs2 root file system:

<pre>
sudo modprobe mtd
sudo modprobe jffs2
sudo modprobe mtdram total_size=59024 # default is 4 MByte - set to max.
sudo modprobe mtdchar
sudo modprobe mtdblock
</pre>

Next we're going to copy onto this fake device. Make sure there are no other MTD devices on your computer and change the device numbers below as necessary:

<pre>
cat /proc/mtd
dev: size erasesize name
mtd0: 039a4000 00020000 "mtdram test device"
</pre>

Now copy the jffs2 file system to the fake MTD device:

<pre>
sudo dd if=qtextended-4.4.2-gta02-rootfs-10302135.jffs2 of=/dev/mtd0
</pre>

Create a mount point, mount the fake MTD device, and check that the contents seem right:

<pre>
sudo mkdir /mnt/tmp
sudo mount -t jffs2 /dev/mtdblock0 /mnt/tmp
ls /mnt/tmp
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Mount the second partition of the microSD card and copy the root file system to it:
copy root file system to sd card using tar

<pre>
sudo mkdir /media/rootfs
sudo mount /dev/sdb2 /media/rootfs
cd /mnt/tmp
sudo tar -cf - . | (cd /media/rootfs && sudo tar -xpvf -)
</pre>

Use "sync" to make sure that all data is written to the microSD card:

<pre>
sync
</pre>

Inspect contents of second partition:

<pre>
ls /media/rootfs
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Note: There was a report that some versions of U-Boot cannot find the kernel image file in the first partition if a kernel image exists in the second partition boot/ directory. I have not confirmed this but there is no need for it so it seems safest to delete it now:

<pre>
sudo rm -f /media/rootfs/boot/*
<pre>

Wait for data to be written to the microSD card and unmount the second partition:

<pre>
sync
umount /dev/sdb2
</pre>

==== Test Qtopia ====

Remove the microSD card from the USB adapter, install it in the Neo FreeRunner, boot into uBoot, and select the option to boot from microSD card.

== Option 3: updating from source ==

{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:

* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)
<pre>
cd /
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz
</pre>

* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/

Since qtopia was renamed in qtextended you could find the snapshots on http://qtextended.org/downloads/snapshots/

* once dowloaded untar it
<pre>tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz</pre>
* make a "build" dir
<pre>
mkdir build
cd build
</pre>
* configure and make:
<pre>../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01
make
</pre>
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:
<pre>
make install
</pre>
will make a root directory into the ''build'' directory. There you can find an ''image'' that directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.

For compiling qt-extended 4.4.2, you may need to use the following commands:
<pre>
* cd build
* $QTOPIA_DEPOT_PATH/configure -device neo -verbose -build-qt -force-build-qt
* bin/qbuild image
</pre>

This forces building qt as well which resolved problems with the qbuild test using all the system ram.

== Booting into Qtopia ==

Now shutdown the FreeRunner

shutdown -h now

Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])

* Press and hold Power button
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.
* A boot menu will appear.
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.

Qtopia should now boot.

'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run

umount /dev/mmcblk0p2
fsck.ext3.e2fsprogs /dev/mmcblk0p2

This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.

== Internationalization ==

Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.

Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].

== Suspend /Resume ==
It seems that suspend/resume only works when the FreeRunner has been connected to a powersource (only a few seconds if sufficient). If you boot from battery, it will never suspend until you have plugged it in at least for a couple of seconds.

== Bugs ==

See [http://trolltech.org/developer/task-tracker/index_html?method=front Trolltech's tracker] ([http://trolltech.org/developer/task-tracker/index_html?method=advsearch&searchstr=&bugs=on&sugs=on&product=2&functionalarea=&versionfound=&versionfixed=&priority=-1&status=0&resolution=-1 Qtopia Tracker]).

Bug reports should be sent to qt-bugs@trolltech.com or by web form at http://trolltech.com/bugreport-form.

== Bugs in 4.4.1 ==
* Boot and Shutdown Splash will not work because splash-write was not compiled into Busybox
* Timezone & time on latest Qt 4.4.1
* The first item in a list is missing the top half

[[Category:Qtopia]]

Qtopia / Qt Extended on FreeRunner

2008-12-25T03:56:26Z

Michaelshiloh: /* Copy the kernel image to the microSD card */

{{Languages|Qtopia_on_FreeRunner}}

This page provides instructions on how to install Qtopia/Qt Extended (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.

{|align=right
|__TOC__
|}

== Current status ==

On 31 October 2008, Trolltech released the [http://qtextended.org/modules/mydownloads/visit.php?lid=98 Qtopia ROM flash image containing the rootfs] for the Openmoko Neo FreeRunner (gta02) containing the Qtopia 4.4.2 release (GPL version). This runs on the [http://qtextended.org/modules/mydownloads/visit.php?lid=91 mwebster ROM flash image containing the kernel]. At release time, 4.4.2 & current mwester's kernel mismatched, please clarify the previous sentence. Hypnotize has released [http://lists.openmoko.org/pipermail/community/2008-November/035245.html Qt Extended 4.4.2 images for the Neo FreeRunner] that work better.

This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does have a webkit based web browser and an GPS "Mapping Demo" application.

There are other third-party GPS applications available:
* [http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner xgps]
* [http://www.linux4.be/fr/roadmap.html RoadMap (experimental)]

([[TangoGPS]] does not work on QtExtended, because it depends upon an Xserver)

You can find all the Qtopia images [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 here] (including Qtextended/Qtopia 4.4 for FreeRunner and Neo1973!)

=== What is in the latest release (QtExtended 4.4.2)? ===
Qtopia 4.4 has been released with the name of [http://doc.trolltech.com/qtextended4.4/release-4-4-2.html QtExtended 4.4].
* a [http://n2.nabble.com/qtopia-update-tp832851p832888.html browser] based on webkit
* [http://n2.nabble.com/-qtopia--rotate-screen--tp841805p841841.html screen rotation in the settings application] (so no automatic rotation)
* [http://n2.nabble.com/Echo-issue-on-OM2008.08-potentially-solved-tp791642.html noise reduction]
* GPS api
* usb net/storage switching
* Gtalk support
* [http://n2.nabble.com/forum/Permalink.jtp?root=841805&post=1083388&page=y better support for non-english languages in the keyboard]

== Option 1: Flashing Qtopia to FreeRunner ==

Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]

== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==

Installation Requirements:

# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)

=== Preparing the SD card ===

See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the "Formatting the SD Card" steps, return here and execute the following:

<pre>
mount /dev/mmcblk0p1 /media/card
mkdir /media/card/boot

mkdir /media/mmcblk0p2
mount /dev/mmcblk0p2 /media/mmcblk0p2
</pre>

This will set you up properly for the installation of the root filesystem and the kernel in the steps below.

=== Installing Qtopia ===

==== Unpacking the Qtopia Root Filesystem Image ====

Download the Qtopia FLASH image from [[Latest Images#Qtopia images]] to your Linux box and extract its contents:

tar xzf qtopia-4.3.2-gta02-flash-*.tgz

You should now have two files:
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2
Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]]. However, in the mount command, substitute the image filename for "/dev/mtdblock0".

==== Creating a compressed tarball ====

Next, tar up the root filesystem:

# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .

Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted. Note the space and the period after the mountpoint.

==== Installing Root Filesystem ====

Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:

scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/

Log in to your FreeRunner and unpack the root filesystem:

<pre>
cd /media/mmcblk0p2
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm -f /media/mmcblk0p2/boot/*
</pre>

'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.

==== Installing Kernel ====

From your Linux box, rename <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> to <tt>uImage.bin</tt> and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the <tt>/media/card</tt> directory as well. There is plenty of room on the first partition to have <tt>uImage.bin</tt> in both locations.

<pre>
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin
scp uImage.bin root@192.168.0.202:/media/card/boot/
scp uImage.bin root@192.168.0.202:/media/card/
</pre>

==== Pointing Qtopia to the SD Card ====

Lorn Potter on the mailing lists pointed this out:

Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card.

You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd /dev node, to be able to run it this way

Another user's solution to this is the following:

Edit this file: /opt/Qtopia/etc/default/Trolltech/Storage.conf
And change the [MountPoint0] section so it resembles this:
<pre>
[MountPoint0]
Name[] = SD Card
Path=/dev/mmcblk0p1
Removable = 0
Applications = 0
Documents = 0
ContentDatabase = 0
</pre>

=== Simplified complete procedure using Ubuntu computer and microSD to USB adapter ===

This procedure was developed with:

* Ubuntu 8.10
* SanDisk microSD to USB adapter
* Qt Extended 4.4.2 2008/10/31

==== Prepare microSD card ====

Create an 8 MB partition for the kernel and use the remaining space for the root file system.

Insert microSD card into adapter, and plug adapter into Ubuntu computer. If any partitions on the microSD card mount automatically, unmount them.

CAUTION: Make sure you know which device your microSD card is. You don't want to perform these steps on your main hard disk!

<pre>
sudo umount /dev/sdb1

sudo fdisk /dev/sdb
</pre>

I assume you know how to use fdisk. Delete any existing partitions, then create two new partitions, the first of size +8M, the second using all remaining space. Set the file system type of the first partition to FAT16 (type '6'). Your partition table should look like this:

<pre>
/dev/sdb1 1 9 9040+ 6 FAT16
/dev/sdb2 10 984 982800 83 Linux
</pre>

Save your partition table and quit fdisk. Format the partitions appropriately:

<pre>
sudo mkfs.vfat /dev/sdb1
sudo mkfs.ext3 /dev/sdb2
</pre>

==== Get the latest version of Qtopia ====

Visit [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6:Qtopia] and get the appropriate file. The Qtopia ROM flash images contain both the file system and the kernel image:

<pre>
wget http://qtextended.org/modules/mydownloads/visit.php?lid=98
tar -zxvf qtextended-4.4.2-gta02-flash.tgz
</pre>

==== Copy the kernel image to the microSD card ====

First mount the first partition, which is the boot partition, of the microSD card, and make a /boot subdirectory:

<pre>
sudo mkdir /media/card
sudo mount /dev/sdb1 /media/card
sudo mkdir /media/card/boot
</pre>

Depending on your version of U-Boot, the kernel image might be expected at the root of the boot partition, or in the /boot directory. Also, the image file name might be expected to have a .bin extension, or not. We create all four variations:

<pre>
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage
</pre>

Wait for data to be written to the microSD card and unmount the first partition:

<pre>
sync
umount /dev/sdb2
</pre>

==== Copy the jffs2 root file system to the microSD card ====

First we need to make a fake MTD device in RAM so that we can mount the jffs2 root file system:

<pre>
sudo modprobe mtd
sudo modprobe jffs2
sudo modprobe mtdram total_size=59024 # default is 4 MByte - set to max.
sudo modprobe mtdchar
sudo modprobe mtdblock
</pre>

Next we're going to copy onto this fake device. Make sure there are no other MTD devices on your computer and change the device numbers below as necessary:

<pre>
cat /proc/mtd
dev: size erasesize name
mtd0: 039a4000 00020000 "mtdram test device"
</pre>

Now copy the jffs2 file system to the fake MTD device:

<pre>
sudo dd if=qtextended-4.4.2-gta02-rootfs-10302135.jffs2 of=/dev/mtd0
</pre>

Create a mount point, mount the fake MTD device, and check that the contents seem right:

<pre>
sudo mkdir /mnt/tmp
sudo mount -t jffs2 /dev/mtdblock0 /mnt/tmp
ls /mnt/tmp
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Mount the second partition of the microSD card and copy the root file system to it:
copy root file system to sd card using tar

<pre>
sudo mkdir /media/rootfs
sudo mount /dev/sdb2 /media/rootfs
cd /mnt/tmp
sudo tar -cf - . | (cd /media/rootfs && sudo tar -xpvf -)
</pre>

Use "sync" to make sure that all data is written to the microSD card:

<pre>
sync
</pre>

Inspect contents of second partition:

<pre>
ls /media/rootfs
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Note: There was a report that some versions of U-Boot cannot find the kernel image file in the first partition if a kernel image exists in the second partition boot/ directory. I have not confirmed this but there is no need for it so it seems safest to delete it now:

<pre>
sudo rm -f /media/rootfs/boot/*
<pre>

Wait for data to be written to the microSD card and unmount the second partition:

<pre>
sync
umount /dev/sdb2
</pre>

==== Test Qtopia ====

Remove the microSD card from the USB adapter, install it in the Neo FreeRunner, boot into uBoot, and select the option to boot from microSD card.

== Option 3: updating from source ==

{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:

* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)
<pre>
cd /
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz
</pre>

* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/

Since qtopia was renamed in qtextended you could find the snapshots on http://qtextended.org/downloads/snapshots/

* once dowloaded untar it
<pre>tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz</pre>
* make a "build" dir
<pre>
mkdir build
cd build
</pre>
* configure and make:
<pre>../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01
make
</pre>
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:
<pre>
make install
</pre>
will make a root directory into the ''build'' directory. There you can find an ''image'' that directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.

For compiling qt-extended 4.4.2, you may need to use the following commands:
<pre>
* cd build
* $QTOPIA_DEPOT_PATH/configure -device neo -verbose -build-qt -force-build-qt
* bin/qbuild image
</pre>

This forces building qt as well which resolved problems with the qbuild test using all the system ram.

== Booting into Qtopia ==

Now shutdown the FreeRunner

shutdown -h now

Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])

* Press and hold Power button
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.
* A boot menu will appear.
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.

Qtopia should now boot.

'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run

umount /dev/mmcblk0p2
fsck.ext3.e2fsprogs /dev/mmcblk0p2

This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.

== Internationalization ==

Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.

Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].

== Suspend /Resume ==
It seems that suspend/resume only works when the FreeRunner has been connected to a powersource (only a few seconds if sufficient). If you boot from battery, it will never suspend until you have plugged it in at least for a couple of seconds.

== Bugs ==

See [http://trolltech.org/developer/task-tracker/index_html?method=front Trolltech's tracker] ([http://trolltech.org/developer/task-tracker/index_html?method=advsearch&searchstr=&bugs=on&sugs=on&product=2&functionalarea=&versionfound=&versionfixed=&priority=-1&status=0&resolution=-1 Qtopia Tracker]).

Bug reports should be sent to qt-bugs@trolltech.com or by web form at http://trolltech.com/bugreport-form.

== Bugs in 4.4.1 ==
* Boot and Shutdown Splash will not work because splash-write was not compiled into Busybox
* Timezone & time on latest Qt 4.4.1
* The first item in a list is missing the top half

[[Category:Qtopia]]

Qtopia / Qt Extended on FreeRunner

2008-12-25T03:53:55Z

Michaelshiloh: /* Get the latest version of Qtopia */

{{Languages|Qtopia_on_FreeRunner}}

This page provides instructions on how to install Qtopia/Qt Extended (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.

{|align=right
|__TOC__
|}

== Current status ==

On 31 October 2008, Trolltech released the [http://qtextended.org/modules/mydownloads/visit.php?lid=98 Qtopia ROM flash image containing the rootfs] for the Openmoko Neo FreeRunner (gta02) containing the Qtopia 4.4.2 release (GPL version). This runs on the [http://qtextended.org/modules/mydownloads/visit.php?lid=91 mwebster ROM flash image containing the kernel]. At release time, 4.4.2 & current mwester's kernel mismatched, please clarify the previous sentence. Hypnotize has released [http://lists.openmoko.org/pipermail/community/2008-November/035245.html Qt Extended 4.4.2 images for the Neo FreeRunner] that work better.

This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does have a webkit based web browser and an GPS "Mapping Demo" application.

There are other third-party GPS applications available:
* [http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner xgps]
* [http://www.linux4.be/fr/roadmap.html RoadMap (experimental)]

([[TangoGPS]] does not work on QtExtended, because it depends upon an Xserver)

You can find all the Qtopia images [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 here] (including Qtextended/Qtopia 4.4 for FreeRunner and Neo1973!)

=== What is in the latest release (QtExtended 4.4.2)? ===
Qtopia 4.4 has been released with the name of [http://doc.trolltech.com/qtextended4.4/release-4-4-2.html QtExtended 4.4].
* a [http://n2.nabble.com/qtopia-update-tp832851p832888.html browser] based on webkit
* [http://n2.nabble.com/-qtopia--rotate-screen--tp841805p841841.html screen rotation in the settings application] (so no automatic rotation)
* [http://n2.nabble.com/Echo-issue-on-OM2008.08-potentially-solved-tp791642.html noise reduction]
* GPS api
* usb net/storage switching
* Gtalk support
* [http://n2.nabble.com/forum/Permalink.jtp?root=841805&post=1083388&page=y better support for non-english languages in the keyboard]

== Option 1: Flashing Qtopia to FreeRunner ==

Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]

== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==

Installation Requirements:

# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)

=== Preparing the SD card ===

See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the "Formatting the SD Card" steps, return here and execute the following:

<pre>
mount /dev/mmcblk0p1 /media/card
mkdir /media/card/boot

mkdir /media/mmcblk0p2
mount /dev/mmcblk0p2 /media/mmcblk0p2
</pre>

This will set you up properly for the installation of the root filesystem and the kernel in the steps below.

=== Installing Qtopia ===

==== Unpacking the Qtopia Root Filesystem Image ====

Download the Qtopia FLASH image from [[Latest Images#Qtopia images]] to your Linux box and extract its contents:

tar xzf qtopia-4.3.2-gta02-flash-*.tgz

You should now have two files:
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2
Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]]. However, in the mount command, substitute the image filename for "/dev/mtdblock0".

==== Creating a compressed tarball ====

Next, tar up the root filesystem:

# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .

Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted. Note the space and the period after the mountpoint.

==== Installing Root Filesystem ====

Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:

scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/

Log in to your FreeRunner and unpack the root filesystem:

<pre>
cd /media/mmcblk0p2
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm -f /media/mmcblk0p2/boot/*
</pre>

'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.

==== Installing Kernel ====

From your Linux box, rename <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> to <tt>uImage.bin</tt> and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the <tt>/media/card</tt> directory as well. There is plenty of room on the first partition to have <tt>uImage.bin</tt> in both locations.

<pre>
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin
scp uImage.bin root@192.168.0.202:/media/card/boot/
scp uImage.bin root@192.168.0.202:/media/card/
</pre>

==== Pointing Qtopia to the SD Card ====

Lorn Potter on the mailing lists pointed this out:

Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card.

You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd /dev node, to be able to run it this way

Another user's solution to this is the following:

Edit this file: /opt/Qtopia/etc/default/Trolltech/Storage.conf
And change the [MountPoint0] section so it resembles this:
<pre>
[MountPoint0]
Name[] = SD Card
Path=/dev/mmcblk0p1
Removable = 0
Applications = 0
Documents = 0
ContentDatabase = 0
</pre>

=== Simplified complete procedure using Ubuntu computer and microSD to USB adapter ===

This procedure was developed with:

* Ubuntu 8.10
* SanDisk microSD to USB adapter
* Qt Extended 4.4.2 2008/10/31

==== Prepare microSD card ====

Create an 8 MB partition for the kernel and use the remaining space for the root file system.

Insert microSD card into adapter, and plug adapter into Ubuntu computer. If any partitions on the microSD card mount automatically, unmount them.

CAUTION: Make sure you know which device your microSD card is. You don't want to perform these steps on your main hard disk!

<pre>
sudo umount /dev/sdb1

sudo fdisk /dev/sdb
</pre>

I assume you know how to use fdisk. Delete any existing partitions, then create two new partitions, the first of size +8M, the second using all remaining space. Set the file system type of the first partition to FAT16 (type '6'). Your partition table should look like this:

<pre>
/dev/sdb1 1 9 9040+ 6 FAT16
/dev/sdb2 10 984 982800 83 Linux
</pre>

Save your partition table and quit fdisk. Format the partitions appropriately:

<pre>
sudo mkfs.vfat /dev/sdb1
sudo mkfs.ext3 /dev/sdb2
</pre>

==== Get the latest version of Qtopia ====

Visit [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6:Qtopia] and get the appropriate file. The Qtopia ROM flash images contain both the file system and the kernel image:

<pre>
wget http://qtextended.org/modules/mydownloads/visit.php?lid=98
tar -zxvf qtextended-4.4.2-gta02-flash.tgz
</pre>

==== Copy the kernel image to the microSD card ====

First mount the first partition, which is the boot partition, of the microSD card:

<pre>
sudo mkdir /media/boot
sudo mount /dev/sdb1 /media/boot
</pre>

Depending on your version of U-Boot, the kernel image might be expected at the root of the boot partition, or in the /boot directory. Also, the image file name might be expected to have a .bin extension, or not. We create all four variations:

<pre>
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage
</pre>

Wait for data to be written to the microSD card and unmount the first partition:

<pre>
sync
umount /dev/sdb2
</pre>

==== Copy the jffs2 root file system to the microSD card ====

First we need to make a fake MTD device in RAM so that we can mount the jffs2 root file system:

<pre>
sudo modprobe mtd
sudo modprobe jffs2
sudo modprobe mtdram total_size=59024 # default is 4 MByte - set to max.
sudo modprobe mtdchar
sudo modprobe mtdblock
</pre>

Next we're going to copy onto this fake device. Make sure there are no other MTD devices on your computer and change the device numbers below as necessary:

<pre>
cat /proc/mtd
dev: size erasesize name
mtd0: 039a4000 00020000 "mtdram test device"
</pre>

Now copy the jffs2 file system to the fake MTD device:

<pre>
sudo dd if=qtextended-4.4.2-gta02-rootfs-10302135.jffs2 of=/dev/mtd0
</pre>

Create a mount point, mount the fake MTD device, and check that the contents seem right:

<pre>
sudo mkdir /mnt/tmp
sudo mount -t jffs2 /dev/mtdblock0 /mnt/tmp
ls /mnt/tmp
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Mount the second partition of the microSD card and copy the root file system to it:
copy root file system to sd card using tar

<pre>
sudo mkdir /media/rootfs
sudo mount /dev/sdb2 /media/rootfs
cd /mnt/tmp
sudo tar -cf - . | (cd /media/rootfs && sudo tar -xpvf -)
</pre>

Use "sync" to make sure that all data is written to the microSD card:

<pre>
sync
</pre>

Inspect contents of second partition:

<pre>
ls /media/rootfs
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Note: There was a report that some versions of U-Boot cannot find the kernel image file in the first partition if a kernel image exists in the second partition boot/ directory. I have not confirmed this but there is no need for it so it seems safest to delete it now:

<pre>
sudo rm -f /media/rootfs/boot/*
<pre>

Wait for data to be written to the microSD card and unmount the second partition:

<pre>
sync
umount /dev/sdb2
</pre>

==== Test Qtopia ====

Remove the microSD card from the USB adapter, install it in the Neo FreeRunner, boot into uBoot, and select the option to boot from microSD card.

== Option 3: updating from source ==

{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:

* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)
<pre>
cd /
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz
</pre>

* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/

Since qtopia was renamed in qtextended you could find the snapshots on http://qtextended.org/downloads/snapshots/

* once dowloaded untar it
<pre>tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz</pre>
* make a "build" dir
<pre>
mkdir build
cd build
</pre>
* configure and make:
<pre>../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01
make
</pre>
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:
<pre>
make install
</pre>
will make a root directory into the ''build'' directory. There you can find an ''image'' that directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.

For compiling qt-extended 4.4.2, you may need to use the following commands:
<pre>
* cd build
* $QTOPIA_DEPOT_PATH/configure -device neo -verbose -build-qt -force-build-qt
* bin/qbuild image
</pre>

This forces building qt as well which resolved problems with the qbuild test using all the system ram.

== Booting into Qtopia ==

Now shutdown the FreeRunner

shutdown -h now

Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])

* Press and hold Power button
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.
* A boot menu will appear.
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.

Qtopia should now boot.

'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run

umount /dev/mmcblk0p2
fsck.ext3.e2fsprogs /dev/mmcblk0p2

This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.

== Internationalization ==

Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.

Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].

== Suspend /Resume ==
It seems that suspend/resume only works when the FreeRunner has been connected to a powersource (only a few seconds if sufficient). If you boot from battery, it will never suspend until you have plugged it in at least for a couple of seconds.

== Bugs ==

See [http://trolltech.org/developer/task-tracker/index_html?method=front Trolltech's tracker] ([http://trolltech.org/developer/task-tracker/index_html?method=advsearch&searchstr=&bugs=on&sugs=on&product=2&functionalarea=&versionfound=&versionfixed=&priority=-1&status=0&resolution=-1 Qtopia Tracker]).

Bug reports should be sent to qt-bugs@trolltech.com or by web form at http://trolltech.com/bugreport-form.

== Bugs in 4.4.1 ==
* Boot and Shutdown Splash will not work because splash-write was not compiled into Busybox
* Timezone & time on latest Qt 4.4.1
* The first item in a list is missing the top half

[[Category:Qtopia]]

Qtopia / Qt Extended on FreeRunner

2008-12-25T03:42:26Z

Michaelshiloh: /* Prepare microSD card */

{{Languages|Qtopia_on_FreeRunner}}

This page provides instructions on how to install Qtopia/Qt Extended (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.

{|align=right
|__TOC__
|}

== Current status ==

On 31 October 2008, Trolltech released the [http://qtextended.org/modules/mydownloads/visit.php?lid=98 Qtopia ROM flash image containing the rootfs] for the Openmoko Neo FreeRunner (gta02) containing the Qtopia 4.4.2 release (GPL version). This runs on the [http://qtextended.org/modules/mydownloads/visit.php?lid=91 mwebster ROM flash image containing the kernel]. At release time, 4.4.2 & current mwester's kernel mismatched, please clarify the previous sentence. Hypnotize has released [http://lists.openmoko.org/pipermail/community/2008-November/035245.html Qt Extended 4.4.2 images for the Neo FreeRunner] that work better.

This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does have a webkit based web browser and an GPS "Mapping Demo" application.

There are other third-party GPS applications available:
* [http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner xgps]
* [http://www.linux4.be/fr/roadmap.html RoadMap (experimental)]

([[TangoGPS]] does not work on QtExtended, because it depends upon an Xserver)

You can find all the Qtopia images [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 here] (including Qtextended/Qtopia 4.4 for FreeRunner and Neo1973!)

=== What is in the latest release (QtExtended 4.4.2)? ===
Qtopia 4.4 has been released with the name of [http://doc.trolltech.com/qtextended4.4/release-4-4-2.html QtExtended 4.4].
* a [http://n2.nabble.com/qtopia-update-tp832851p832888.html browser] based on webkit
* [http://n2.nabble.com/-qtopia--rotate-screen--tp841805p841841.html screen rotation in the settings application] (so no automatic rotation)
* [http://n2.nabble.com/Echo-issue-on-OM2008.08-potentially-solved-tp791642.html noise reduction]
* GPS api
* usb net/storage switching
* Gtalk support
* [http://n2.nabble.com/forum/Permalink.jtp?root=841805&post=1083388&page=y better support for non-english languages in the keyboard]

== Option 1: Flashing Qtopia to FreeRunner ==

Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]

== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==

Installation Requirements:

# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)

=== Preparing the SD card ===

See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the "Formatting the SD Card" steps, return here and execute the following:

<pre>
mount /dev/mmcblk0p1 /media/card
mkdir /media/card/boot

mkdir /media/mmcblk0p2
mount /dev/mmcblk0p2 /media/mmcblk0p2
</pre>

This will set you up properly for the installation of the root filesystem and the kernel in the steps below.

=== Installing Qtopia ===

==== Unpacking the Qtopia Root Filesystem Image ====

Download the Qtopia FLASH image from [[Latest Images#Qtopia images]] to your Linux box and extract its contents:

tar xzf qtopia-4.3.2-gta02-flash-*.tgz

You should now have two files:
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2
Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]]. However, in the mount command, substitute the image filename for "/dev/mtdblock0".

==== Creating a compressed tarball ====

Next, tar up the root filesystem:

# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .

Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted. Note the space and the period after the mountpoint.

==== Installing Root Filesystem ====

Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:

scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/

Log in to your FreeRunner and unpack the root filesystem:

<pre>
cd /media/mmcblk0p2
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm -f /media/mmcblk0p2/boot/*
</pre>

'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.

==== Installing Kernel ====

From your Linux box, rename <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> to <tt>uImage.bin</tt> and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the <tt>/media/card</tt> directory as well. There is plenty of room on the first partition to have <tt>uImage.bin</tt> in both locations.

<pre>
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin
scp uImage.bin root@192.168.0.202:/media/card/boot/
scp uImage.bin root@192.168.0.202:/media/card/
</pre>

==== Pointing Qtopia to the SD Card ====

Lorn Potter on the mailing lists pointed this out:

Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card.

You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd /dev node, to be able to run it this way

Another user's solution to this is the following:

Edit this file: /opt/Qtopia/etc/default/Trolltech/Storage.conf
And change the [MountPoint0] section so it resembles this:
<pre>
[MountPoint0]
Name[] = SD Card
Path=/dev/mmcblk0p1
Removable = 0
Applications = 0
Documents = 0
ContentDatabase = 0
</pre>

=== Simplified complete procedure using Ubuntu computer and microSD to USB adapter ===

This procedure was developed with:

* Ubuntu 8.10
* SanDisk microSD to USB adapter
* Qt Extended 4.4.2 2008/10/31

==== Prepare microSD card ====

Create an 8 MB partition for the kernel and use the remaining space for the root file system.

Insert microSD card into adapter, and plug adapter into Ubuntu computer. If any partitions on the microSD card mount automatically, unmount them.

CAUTION: Make sure you know which device your microSD card is. You don't want to perform these steps on your main hard disk!

<pre>
sudo umount /dev/sdb1

sudo fdisk /dev/sdb
</pre>

I assume you know how to use fdisk. Delete any existing partitions, then create two new partitions, the first of size +8M, the second using all remaining space. Set the file system type of the first partition to FAT16 (type '6'). Your partition table should look like this:

<pre>
/dev/sdb1 1 9 9040+ 6 FAT16
/dev/sdb2 10 984 982800 83 Linux
</pre>

Save your partition table and quit fdisk. Format the partitions appropriately:

<pre>
sudo mkfs.vfat /dev/sdb1
sudo mkfs.ext3 /dev/sdb2
</pre>

==== Get the latest version of Qtopia ====

Visit [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6:Qtopia] and get the appropriate file. The Qtopia ROM flash images contain both the file system and the kernel image:

<pre>
wget http://qtextended.org/modules/mydownloads/visit.php?lid=98
tar -zxvf qtextended-4.4.2-gta02-flash.tgz
cd qtextended-4.4.2-gta02-flash
</pre>

==== Copy the kernel image to the microSD card ====

First mount the first partition, which is the boot partition, of the microSD card:

<pre>
sudo mkdir /media/boot
sudo mount /dev/sdb1 /media/boot
</pre>

Depending on your version of U-Boot, the kernel image might be expected at the root of the boot partition, or in the /boot directory. Also, the image file name might be expected to have a .bin extension, or not. We create all four variations:

<pre>
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage
</pre>

Wait for data to be written to the microSD card and unmount the first partition:

<pre>
sync
umount /dev/sdb2
</pre>

==== Copy the jffs2 root file system to the microSD card ====

First we need to make a fake MTD device in RAM so that we can mount the jffs2 root file system:

<pre>
sudo modprobe mtd
sudo modprobe jffs2
sudo modprobe mtdram total_size=59024 # default is 4 MByte - set to max.
sudo modprobe mtdchar
sudo modprobe mtdblock
</pre>

Next we're going to copy onto this fake device. Make sure there are no other MTD devices on your computer and change the device numbers below as necessary:

<pre>
cat /proc/mtd
dev: size erasesize name
mtd0: 039a4000 00020000 "mtdram test device"
</pre>

Now copy the jffs2 file system to the fake MTD device:

<pre>
sudo dd if=qtextended-4.4.2-gta02-rootfs-10302135.jffs2 of=/dev/mtd0
</pre>

Create a mount point, mount the fake MTD device, and check that the contents seem right:

<pre>
sudo mkdir /mnt/tmp
sudo mount -t jffs2 /dev/mtdblock0 /mnt/tmp
ls /mnt/tmp
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Mount the second partition of the microSD card and copy the root file system to it:
copy root file system to sd card using tar

<pre>
sudo mkdir /media/rootfs
sudo mount /dev/sdb2 /media/rootfs
cd /mnt/tmp
sudo tar -cf - . | (cd /media/rootfs && sudo tar -xpvf -)
</pre>

Use "sync" to make sure that all data is written to the microSD card:

<pre>
sync
</pre>

Inspect contents of second partition:

<pre>
ls /media/rootfs
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Note: There was a report that some versions of U-Boot cannot find the kernel image file in the first partition if a kernel image exists in the second partition boot/ directory. I have not confirmed this but there is no need for it so it seems safest to delete it now:

<pre>
sudo rm -f /media/rootfs/boot/*
<pre>

Wait for data to be written to the microSD card and unmount the second partition:

<pre>
sync
umount /dev/sdb2
</pre>

==== Test Qtopia ====

Remove the microSD card from the USB adapter, install it in the Neo FreeRunner, boot into uBoot, and select the option to boot from microSD card.

== Option 3: updating from source ==

{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:

* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)
<pre>
cd /
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz
</pre>

* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/

Since qtopia was renamed in qtextended you could find the snapshots on http://qtextended.org/downloads/snapshots/

* once dowloaded untar it
<pre>tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz</pre>
* make a "build" dir
<pre>
mkdir build
cd build
</pre>
* configure and make:
<pre>../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01
make
</pre>
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:
<pre>
make install
</pre>
will make a root directory into the ''build'' directory. There you can find an ''image'' that directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.

For compiling qt-extended 4.4.2, you may need to use the following commands:
<pre>
* cd build
* $QTOPIA_DEPOT_PATH/configure -device neo -verbose -build-qt -force-build-qt
* bin/qbuild image
</pre>

This forces building qt as well which resolved problems with the qbuild test using all the system ram.

== Booting into Qtopia ==

Now shutdown the FreeRunner

shutdown -h now

Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])

* Press and hold Power button
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.
* A boot menu will appear.
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.

Qtopia should now boot.

'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run

umount /dev/mmcblk0p2
fsck.ext3.e2fsprogs /dev/mmcblk0p2

This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.

== Internationalization ==

Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.

Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].

== Suspend /Resume ==
It seems that suspend/resume only works when the FreeRunner has been connected to a powersource (only a few seconds if sufficient). If you boot from battery, it will never suspend until you have plugged it in at least for a couple of seconds.

== Bugs ==

See [http://trolltech.org/developer/task-tracker/index_html?method=front Trolltech's tracker] ([http://trolltech.org/developer/task-tracker/index_html?method=advsearch&searchstr=&bugs=on&sugs=on&product=2&functionalarea=&versionfound=&versionfixed=&priority=-1&status=0&resolution=-1 Qtopia Tracker]).

Bug reports should be sent to qt-bugs@trolltech.com or by web form at http://trolltech.com/bugreport-form.

== Bugs in 4.4.1 ==
* Boot and Shutdown Splash will not work because splash-write was not compiled into Busybox
* Timezone & time on latest Qt 4.4.1
* The first item in a list is missing the top half

[[Category:Qtopia]]

Qtopia / Qt Extended on FreeRunner

2008-12-25T03:06:26Z

Michaelshiloh: /* Simplified complete procedure using Ubuntu desktop and micro SD to USB adapter */

{{Languages|Qtopia_on_FreeRunner}}

This page provides instructions on how to install Qtopia/Qt Extended (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.

{|align=right
|__TOC__
|}

== Current status ==

On 31 October 2008, Trolltech released the [http://qtextended.org/modules/mydownloads/visit.php?lid=98 Qtopia ROM flash image containing the rootfs] for the Openmoko Neo FreeRunner (gta02) containing the Qtopia 4.4.2 release (GPL version). This runs on the [http://qtextended.org/modules/mydownloads/visit.php?lid=91 mwebster ROM flash image containing the kernel]. At release time, 4.4.2 & current mwester's kernel mismatched, please clarify the previous sentence. Hypnotize has released [http://lists.openmoko.org/pipermail/community/2008-November/035245.html Qt Extended 4.4.2 images for the Neo FreeRunner] that work better.

This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does have a webkit based web browser and an GPS "Mapping Demo" application.

There are other third-party GPS applications available:
* [http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner xgps]
* [http://www.linux4.be/fr/roadmap.html RoadMap (experimental)]

([[TangoGPS]] does not work on QtExtended, because it depends upon an Xserver)

You can find all the Qtopia images [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 here] (including Qtextended/Qtopia 4.4 for FreeRunner and Neo1973!)

=== What is in the latest release (QtExtended 4.4.2)? ===
Qtopia 4.4 has been released with the name of [http://doc.trolltech.com/qtextended4.4/release-4-4-2.html QtExtended 4.4].
* a [http://n2.nabble.com/qtopia-update-tp832851p832888.html browser] based on webkit
* [http://n2.nabble.com/-qtopia--rotate-screen--tp841805p841841.html screen rotation in the settings application] (so no automatic rotation)
* [http://n2.nabble.com/Echo-issue-on-OM2008.08-potentially-solved-tp791642.html noise reduction]
* GPS api
* usb net/storage switching
* Gtalk support
* [http://n2.nabble.com/forum/Permalink.jtp?root=841805&post=1083388&page=y better support for non-english languages in the keyboard]

== Option 1: Flashing Qtopia to FreeRunner ==

Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]

== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==

Installation Requirements:

# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)

=== Preparing the SD card ===

See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the "Formatting the SD Card" steps, return here and execute the following:

<pre>
mount /dev/mmcblk0p1 /media/card
mkdir /media/card/boot

mkdir /media/mmcblk0p2
mount /dev/mmcblk0p2 /media/mmcblk0p2
</pre>

This will set you up properly for the installation of the root filesystem and the kernel in the steps below.

=== Installing Qtopia ===

==== Unpacking the Qtopia Root Filesystem Image ====

Download the Qtopia FLASH image from [[Latest Images#Qtopia images]] to your Linux box and extract its contents:

tar xzf qtopia-4.3.2-gta02-flash-*.tgz

You should now have two files:
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2
Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]]. However, in the mount command, substitute the image filename for "/dev/mtdblock0".

==== Creating a compressed tarball ====

Next, tar up the root filesystem:

# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .

Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted. Note the space and the period after the mountpoint.

==== Installing Root Filesystem ====

Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:

scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/

Log in to your FreeRunner and unpack the root filesystem:

<pre>
cd /media/mmcblk0p2
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm -f /media/mmcblk0p2/boot/*
</pre>

'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.

==== Installing Kernel ====

From your Linux box, rename <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> to <tt>uImage.bin</tt> and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the <tt>/media/card</tt> directory as well. There is plenty of room on the first partition to have <tt>uImage.bin</tt> in both locations.

<pre>
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin
scp uImage.bin root@192.168.0.202:/media/card/boot/
scp uImage.bin root@192.168.0.202:/media/card/
</pre>

==== Pointing Qtopia to the SD Card ====

Lorn Potter on the mailing lists pointed this out:

Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card.

You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd /dev node, to be able to run it this way

Another user's solution to this is the following:

Edit this file: /opt/Qtopia/etc/default/Trolltech/Storage.conf
And change the [MountPoint0] section so it resembles this:
<pre>
[MountPoint0]
Name[] = SD Card
Path=/dev/mmcblk0p1
Removable = 0
Applications = 0
Documents = 0
ContentDatabase = 0
</pre>

=== Simplified complete procedure using Ubuntu computer and microSD to USB adapter ===

This procedure was developed with:

* Ubuntu 8.10
* SanDisk microSD to USB adapter
* Qt Extended 4.4.2 2008/10/31

==== Prepare microSD card ====

Create an 8 MB partition for the kernel and use the remaining space for the root file system.

Insert microSD card into adapter, and plug adapter into Ubuntu computer. If the microSD card mounts automatically, unmount it.

CAUTION: Make sure you know which device your microSD card is. You don't want to perform these steps on your main hard disk!

<pre>
sudo umount /dev/sdb1

sudo fdisk /dev/sdb
</pre>

I assume you know how to use fdisk. Delete any existing partitions, then create two new partitions, the first of size +8M, the second using all remaining space. Set the file system type of the first partition to FAT16 (type '6'). Your partition table should look like this:

<pre>
/dev/sdb1 1 9 9040+ 6 FAT16
/dev/sdb2 10 984 982800 83 Linux
</pre>

Save your partition table and quit fdisk. Format the partitions appropriately:

<pre>
sudo mkfs.vfat /dev/sdb1
sudo mkfs.ext3 /dev/sdb2
</pre>

==== Get the latest version of Qtopia ====

Visit [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6:Qtopia] and get the appropriate file. The Qtopia ROM flash images contain both the file system and the kernel image:

<pre>
wget http://qtextended.org/modules/mydownloads/visit.php?lid=98
tar -zxvf qtextended-4.4.2-gta02-flash.tgz
cd qtextended-4.4.2-gta02-flash
</pre>

==== Copy the kernel image to the microSD card ====

First mount the first partition, which is the boot partition, of the microSD card:

<pre>
sudo mkdir /media/boot
sudo mount /dev/sdb1 /media/boot
</pre>

Depending on your version of U-Boot, the kernel image might be expected at the root of the boot partition, or in the /boot directory. Also, the image file name might be expected to have a .bin extension, or not. We create all four variations:

<pre>
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage.bin
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage
</pre>

Wait for data to be written to the microSD card and unmount the first partition:

<pre>
sync
umount /dev/sdb2
</pre>

==== Copy the jffs2 root file system to the microSD card ====

First we need to make a fake MTD device in RAM so that we can mount the jffs2 root file system:

<pre>
sudo modprobe mtd
sudo modprobe jffs2
sudo modprobe mtdram total_size=59024 # default is 4 MByte - set to max.
sudo modprobe mtdchar
sudo modprobe mtdblock
</pre>

Next we're going to copy onto this fake device. Make sure there are no other MTD devices on your computer and change the device numbers below as necessary:

<pre>
cat /proc/mtd
dev: size erasesize name
mtd0: 039a4000 00020000 "mtdram test device"
</pre>

Now copy the jffs2 file system to the fake MTD device:

<pre>
sudo dd if=qtextended-4.4.2-gta02-rootfs-10302135.jffs2 of=/dev/mtd0
</pre>

Create a mount point, mount the fake MTD device, and check that the contents seem right:

<pre>
sudo mkdir /mnt/tmp
sudo mount -t jffs2 /dev/mtdblock0 /mnt/tmp
ls /mnt/tmp
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Mount the second partition of the microSD card and copy the root file system to it:
copy root file system to sd card using tar

<pre>
sudo mkdir /media/rootfs
sudo mount /dev/sdb2 /media/rootfs
cd /mnt/tmp
sudo tar -cf - . | (cd /media/rootfs && sudo tar -xpvf -)
</pre>

Use "sync" to make sure that all data is written to the microSD card:

<pre>
sync
</pre>

Inspect contents of second partition:

<pre>
ls /media/rootfs
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/
boot/ etc/ lib/ mnt/ proc/ sys/ usr/
</pre>

Note: There was a report that some versions of U-Boot cannot find the kernel image file in the first partition if a kernel image exists in the second partition boot/ directory. I have not confirmed this but there is no need for it so it seems safest to delete it now:

<pre>
sudo rm -f /media/rootfs/boot/*
<pre>

Wait for data to be written to the microSD card and unmount the second partition:

<pre>
sync
umount /dev/sdb2
</pre>

==== Test Qtopia ====

Remove the microSD card from the USB adapter, install it in the Neo FreeRunner, boot into uBoot, and select the option to boot from microSD card.

== Option 3: updating from source ==

{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:

* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)
<pre>
cd /
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz
</pre>

* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/

Since qtopia was renamed in qtextended you could find the snapshots on http://qtextended.org/downloads/snapshots/

* once dowloaded untar it
<pre>tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz</pre>
* make a "build" dir
<pre>
mkdir build
cd build
</pre>
* configure and make:
<pre>../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01
make
</pre>
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:
<pre>
make install
</pre>
will make a root directory into the ''build'' directory. There you can find an ''image'' that directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.

For compiling qt-extended 4.4.2, you may need to use the following commands:
<pre>
* cd build
* $QTOPIA_DEPOT_PATH/configure -device neo -verbose -build-qt -force-build-qt
* bin/qbuild image
</pre>

This forces building qt as well which resolved problems with the qbuild test using all the system ram.

== Booting into Qtopia ==

Now shutdown the FreeRunner

shutdown -h now

Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])

* Press and hold Power button
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.
* A boot menu will appear.
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.

Qtopia should now boot.

'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run

umount /dev/mmcblk0p2
fsck.ext3.e2fsprogs /dev/mmcblk0p2

This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.

== Internationalization ==

Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.

Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].

== Suspend /Resume ==
It seems that suspend/resume only works when the FreeRunner has been connected to a powersource (only a few seconds if sufficient). If you boot from battery, it will never suspend until you have plugged it in at least for a couple of seconds.

== Bugs ==

See [http://trolltech.org/developer/task-tracker/index_html?method=front Trolltech's tracker] ([http://trolltech.org/developer/task-tracker/index_html?method=advsearch&searchstr=&bugs=on&sugs=on&product=2&functionalarea=&versionfound=&versionfixed=&priority=-1&status=0&resolution=-1 Qtopia Tracker]).

Bug reports should be sent to qt-bugs@trolltech.com or by web form at http://trolltech.com/bugreport-form.

== Bugs in 4.4.1 ==
* Boot and Shutdown Splash will not work because splash-write was not compiled into Busybox
* Timezone & time on latest Qt 4.4.1
* The first item in a list is missing the top half

[[Category:Qtopia]]

Qtopia / Qt Extended on FreeRunner

2008-12-25T02:14:41Z

Michaelshiloh: added section

{{Languages|Qtopia_on_FreeRunner}}

This page provides instructions on how to install Qtopia/Qt Extended (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.

{|align=right
|__TOC__
|}

== Current status ==

On 31 October 2008, Trolltech released the [http://qtextended.org/modules/mydownloads/visit.php?lid=98 Qtopia ROM flash image containing the rootfs] for the Openmoko Neo FreeRunner (gta02) containing the Qtopia 4.4.2 release (GPL version). This runs on the [http://qtextended.org/modules/mydownloads/visit.php?lid=91 mwebster ROM flash image containing the kernel]. At release time, 4.4.2 & current mwester's kernel mismatched, please clarify the previous sentence. Hypnotize has released [http://lists.openmoko.org/pipermail/community/2008-November/035245.html Qt Extended 4.4.2 images for the Neo FreeRunner] that work better.

This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does have a webkit based web browser and an GPS "Mapping Demo" application.

There are other third-party GPS applications available:
* [http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner xgps]
* [http://www.linux4.be/fr/roadmap.html RoadMap (experimental)]

([[TangoGPS]] does not work on QtExtended, because it depends upon an Xserver)

You can find all the Qtopia images [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 here] (including Qtextended/Qtopia 4.4 for FreeRunner and Neo1973!)

=== What is in the latest release (QtExtended 4.4.2)? ===
Qtopia 4.4 has been released with the name of [http://doc.trolltech.com/qtextended4.4/release-4-4-2.html QtExtended 4.4].
* a [http://n2.nabble.com/qtopia-update-tp832851p832888.html browser] based on webkit
* [http://n2.nabble.com/-qtopia--rotate-screen--tp841805p841841.html screen rotation in the settings application] (so no automatic rotation)
* [http://n2.nabble.com/Echo-issue-on-OM2008.08-potentially-solved-tp791642.html noise reduction]
* GPS api
* usb net/storage switching
* Gtalk support
* [http://n2.nabble.com/forum/Permalink.jtp?root=841805&post=1083388&page=y better support for non-english languages in the keyboard]

== Option 1: Flashing Qtopia to FreeRunner ==

Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]

== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==

Installation Requirements:

# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)

=== Preparing the SD card ===

See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the "Formatting the SD Card" steps, return here and execute the following:

<pre>
mount /dev/mmcblk0p1 /media/card
mkdir /media/card/boot

mkdir /media/mmcblk0p2
mount /dev/mmcblk0p2 /media/mmcblk0p2
</pre>

This will set you up properly for the installation of the root filesystem and the kernel in the steps below.

=== Installing Qtopia ===

==== Unpacking the Qtopia Root Filesystem Image ====

Download the Qtopia FLASH image from [[Latest Images#Qtopia images]] to your Linux box and extract its contents:

tar xzf qtopia-4.3.2-gta02-flash-*.tgz

You should now have two files:
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2
Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]]. However, in the mount command, substitute the image filename for "/dev/mtdblock0".

==== Creating a compressed tarball ====

Next, tar up the root filesystem:

# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .

Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted. Note the space and the period after the mountpoint.

==== Installing Root Filesystem ====

Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:

scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/

Log in to your FreeRunner and unpack the root filesystem:

<pre>
cd /media/mmcblk0p2
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm -f /media/mmcblk0p2/boot/*
</pre>

'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.

==== Installing Kernel ====

From your Linux box, rename <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> to <tt>uImage.bin</tt> and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the <tt>/media/card</tt> directory as well. There is plenty of room on the first partition to have <tt>uImage.bin</tt> in both locations.

<pre>
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin
scp uImage.bin root@192.168.0.202:/media/card/boot/
scp uImage.bin root@192.168.0.202:/media/card/
</pre>

==== Pointing Qtopia to the SD Card ====

Lorn Potter on the mailing lists pointed this out:

Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card.

You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd /dev node, to be able to run it this way

Another user's solution to this is the following:

Edit this file: /opt/Qtopia/etc/default/Trolltech/Storage.conf
And change the [MountPoint0] section so it resembles this:
<pre>
[MountPoint0]
Name[] = SD Card
Path=/dev/mmcblk0p1
Removable = 0
Applications = 0
Documents = 0
ContentDatabase = 0
</pre>

=== Simplified complete procedure using Ubuntu desktop and micro SD to USB adapter ===

== Option 3: updating from source ==

{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:

* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)
<pre>
cd /
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz
</pre>

* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/

Since qtopia was renamed in qtextended you could find the snapshots on http://qtextended.org/downloads/snapshots/

* once dowloaded untar it
<pre>tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz</pre>
* make a "build" dir
<pre>
mkdir build
cd build
</pre>
* configure and make:
<pre>../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01
make
</pre>
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:
<pre>
make install
</pre>
will make a root directory into the ''build'' directory. There you can find an ''image'' that directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.

For compiling qt-extended 4.4.2, you may need to use the following commands:
<pre>
* cd build
* $QTOPIA_DEPOT_PATH/configure -device neo -verbose -build-qt -force-build-qt
* bin/qbuild image
</pre>

This forces building qt as well which resolved problems with the qbuild test using all the system ram.

== Booting into Qtopia ==

Now shutdown the FreeRunner

shutdown -h now

Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])

* Press and hold Power button
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.
* A boot menu will appear.
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.

Qtopia should now boot.

'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run

umount /dev/mmcblk0p2
fsck.ext3.e2fsprogs /dev/mmcblk0p2

This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.

== Internationalization ==

Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.

Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].

== Suspend /Resume ==
It seems that suspend/resume only works when the FreeRunner has been connected to a powersource (only a few seconds if sufficient). If you boot from battery, it will never suspend until you have plugged it in at least for a couple of seconds.

== Bugs ==

See [http://trolltech.org/developer/task-tracker/index_html?method=front Trolltech's tracker] ([http://trolltech.org/developer/task-tracker/index_html?method=advsearch&searchstr=&bugs=on&sugs=on&product=2&functionalarea=&versionfound=&versionfixed=&priority=-1&status=0&resolution=-1 Qtopia Tracker]).

Bug reports should be sent to qt-bugs@trolltech.com or by web form at http://trolltech.com/bugreport-form.

== Bugs in 4.4.1 ==
* Boot and Shutdown Splash will not work because splash-write was not compiled into Busybox
* Timezone & time on latest Qt 4.4.1
* The first item in a list is missing the top half

[[Category:Qtopia]]

File:Nokia-charging-stand.jpg

2008-10-14T18:28:32Z

Michaelshiloh:

Charger for Nokia BL-5C. There are several important points to note:

1. This is just a charging stand and does not include a charger
2. No one has actually tried using this

[[Category:Battery]]

Neo FreeRunner Battery

2008-10-12T16:34:21Z

Michaelshiloh: /* GTA02 1200 mAh Smart Battery */

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

*Internally, uses the SANYO 1200mAh cell (note that the Sanyo cell by itself does not have the Coulomb-counter and thus can not be used as a replacement for the Neo FreeRunner battery)
*Battery Technical information: [http://people.openmoko.org/tony_tu/GTA02/hardware/GTA02/CT-GTA02.pdf Detailed Battery Information]

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

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

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

== Known Issues ==

=== Make sure your battery never discharges completely. ===

This is an issue because the internal charging circuitry can not be turned on until the FreeRunner has booted, and booting through USB power alone does not work.

==== What to do if your battery has become completely discharged ====

See the workarounds [[Neo_FreeRunner_Hardware_Issues#Can.27t_boot_with_discharged_or_missing_battery|here]].

==== More tricks ====

''Q: Does anyone know WHY it don't charge when it is off? My logic says that it is very important to have the option charge the battery when it is flat.''

A: I can't give you a simple answer. Charging is controlled by the PCF50633
chip, based on configuration values that are written to it by u-boot,
Linux, and userspace programs. Some of these settings are preserved
across a power-cycle (the PCF50633 has a small backup battery that's
also used to keep the RTC running) so the behavior at startup depends on
the software that you used during your last session.

Another complication is that some Freerunners are capable of starting up
without a battery while others are not (possibly due to different
capacitor values on the internal power rails).

I can give a few hints:
* The current (Sep. 2nd, 2008) u-boot has a bug that means it will not properly charge from the wall charger. Try a USB cable into a PC instead.
* Try booting through NOR u-boot instead (hold aux and then power) with both the wall charger or a 500mA USB connection, then try booting Linux.
* Try to boot into the NAND u-boot menu (hold power and then aux) and then select "power off". This may leave the device in a state were it will charge. Wait 15 minutes and then try to boot Linux.
* If the device shuts off during one of the above attempts, let it sit for a few minutes and then try that same item once again

Kudos to Mike Montour on the
[http://lists.openmoko.org/pipermail/community/2008-September/029243.html Community mailing list].

== Compatible Replacement Batteries ==

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

{| border="1" cellpadding="4" cellspacing="0"
!Battery Model
!Capacity (mAh)
!Charge info reported
!Notes
|-
|NOKIA BL-4
|
|no
|
|-
|NOKIA BL-4C
|750
|no
|Slightly thinner than original.
|-
|NOKIA BL-5B
|760/890
|
|
|-
|NOKIA BL-5C
|950
|no
|
|-
|NOKIA BL-6C
|1070
|no
|
|-
|NOKIA BR-6C
|?
|no
|
|}

== Alien Charging of Battery ==

Nokia devices (phones and stand-alone chargers) usually will not charge
non-Nokia batteries, most likely because they can't be sure they have
the correct charging parameters (and of course Nokia isn't interested in supporting use of alien batteries with their phones).

Most after-market or no-name brands of Nokia-compatible chargers don't
test the make of the battery, most likely because adding the capability
to perform this test would add to the cost of the charger and limit it's universal character (that's not the interest of second source manufacturers).

Thus:
* You can use a Nokia or Nokia-compatible BL-4C, BL-5C, or BL-6C in the Neo
* You can charge the Neo battery in a Nokia-compatible charger that is not Nokia branded
* You can NOT charge the Neo battery in a Nokia branded phone or charger

For more information about USB battery chargers that can be used with the Neo FreeRunner see
{{main|USB charger}}

== DIY external battery pack from a Minty case ==

'''Mintyboost:'''

Charge from a couple of AA batteries: [http://www.ladyada.net/make/mintyboost/ Minty Boost!], [http://www.millions.ca/~stacy/mintyboost/ report on a Neo FreeRunner application].

Adding the 47k resistor to the minty boost so that the Freerunner fast charges at 1A is a poor idea for a couple reasons, the biggest one being that the minty boost can't supply 1A the max is 600mA. as far as I know, there is no magic resistor to identify a 500mA charger to the Freerunner, it depends on USB host telling it that it can provide 500mA. Second, the ID pin is in the USB micro connector, so you would either need to put a micro connector on your minty boost (with the correct resistor installed) or use a hacked cable.

Even if the Linear Technology step up voltage converter is supposed to be able to do 600mA, the AA cells seem to have a problem with supplying 500mA. They get a little toasty :-). One powerpack built using D cells doesn't seem to have any issues with supplying 500mA.

[[Category:Battery]]
[[Category:Neo FreeRunner Hardware]]

FreeRunner/Buttons and LEDs

2008-10-12T00:06:12Z

Michaelshiloh: /* Blink LEDs by user-definable beat */

This is the Software specification for the Openmoko Neo FreeRunner Button and LEDs.

{{InProgress}}

=Taxonomy=

==What's currently implemented==
/sys/devices/platform/gta02-led.0/leds/gta02-aux:red/
/sys/devices/platform/gta02-led.0/leds/gta02-power:blue/
/sys/devices/platform/gta02-led.0/leds/gta02-power:orange/
Those are all userspace directories for controlling the LEDs. echo 0 > brightness will turn the LED off. echo 1 > brightness will turn it on.
trigger currently does nothing.

==Buttons==
* AUX = Button on the left side of the device, upper area
* POWER = Button on the right side of the device, center area (right below the USB socket)

==Leds==
{| border=1 cellspacing=0 cellpadding=5
| EVENT
|style="background:#FF0000;color:white;"| '''red'''
| behind AUX button
|-
| HEARTBEAT
|style="background:#FF8040;color:white;"| '''orange'''
| behind POWER button
|-
| WIRELESS / BLUETOOTH
|style="background:#0000FF;color:white;"| '''blue'''
| behind POWER button
|-
| MIXING TWO LEDS
|style="background:#80409F;color:white;"| '''purple'''
| behind POWER button if turning on the blue and the orang buttons together
|}

==Modes==
* OFF = Device has no power or has been shutdown
* ON = Device is fully powered
* ON+CHARGING = Device is fully powered and has been connected to a USB host or Openmoko charger.
* LOCK = Device is fully powered, but has screen lock displayed
* SUSPEND = Device has been suspended to low-power mode

=Basic Button Usage=

This is grouped by mode:

==Mode: OFF==

* To switch the device on: Press and hold POWER until the boot logo appears.
* To enter the "normal" (NAND) boot menu: Press and hold POWER, one second later press and hold AUX.
* To enter the "rescue" (NOR) boot menu: Press and hold AUX, then press and hold POWER.

==Mode: ON==

* To suspend the device: Press POWER.
* To shut down the device: Press and hold POWER for 4 seconds. If the device hangs, press and hold POWER for 8 seconds. If it still hangs, remove the battery and disconnect from USB.
* To go to the home screen: Press AUX.
* To display the profile screen: Press and hold AUX until it appears.

==Mode: SUSPEND==

* To wakeup the device: Press POWER.

=Basic LED Usage=

LEDs are very useful in broadcasting valuable basic status information to the user in a way that the user does not have to unlock the device, enable the screen or turning the screen saver off and subsequently search the screen for basic status information.

''This is grouped by mode:''

==Mode: OFF==

* All LEDs will be turned off.

==Mode: ON==

* HEARTBEAT will emit a short blink every 4 seconds.
* If Bluetooth is powered on, WIRELESS will emit a short blink every 2 seconds.
* If Wifi is powered on, WIRELESS will emit a long blink every 2 seconds.
* If Bluetooth and Wifi are powered on, WIRELESS will be lit continuosly.

==Mode: ON+CHARGING==

''Same as ON, with the exception of''
* HEARTBEAT will increase blinking as the charge level of the battery increases.
* HEARTBEAT will be continuosly lit, if the battery has been fully charged.

==Mode: SUSPEND==

* All LEDs will be turned off.

=Advanced Button/LED Usage=

* In ON-Mode, EVENT will blink every 2 seconds if there's an event that needs your attention.
* The more events, the faster EVENT will blink.
* Pressing AUX will acknowledge the event with the topmost priority and display it to you.
* EVENT will stop to blink once all events have been acknowledged.

=A first rules implementation=
A C implementation of these rules has been [http://lists.openmoko.org/pipermail/openmoko-devel/2008-July/003458.html done by smurfy - phil] and is available at http://www.smurfy.de/files/neo/openmoko-led-v1.tar.gz

= Implementations of other LED behaviors =

== Blink LEDs to a user-definable rhythm ==

A Python Script For Blinking Leds By Beats. This script reads beats from a file and blinks FreeRunners LEDs accordingly.

File format is human readable text, consisting of a simple sequence of integer quartet (4 numbers). The first number representing status of blue power-led, second means status of orange power-led and third means status of red aux-led. 0=OFF, 1=ON. (If blue=1 and orange=1 then power=lila. This has nothing to do with this python script or this file format.) The last number represents the duration in milliseconds to hold that situation of leds. Any non digit characters in the file count as a separators between numbers, but are otherwise ignored.

It requires packages python-core and python-re from opkg.
==== Led blinker ====

#!/usr/bin/python
"""Led Blinker Player

Usage: python leds.py [filename]
"""
import sys
import time
import re

def loadFromTextFile(filename):
infile = open(filename)
contents = infile.read()
return re.findall("(\d+)\D*(\d+)\D*(\d+)\D*(\d+)", contents)

def playNote(blue_value, orange_value, red_value, duration):
blue.write(str(blue_value) + "\n")
orange.write(str(orange_value) + "\n")
red.write(str(red_value) + "\n")
time.sleep(float(duration) / 1000.0)

def playFile(filename):
global blue, orange, red
notes = loadFromTextFile(filename)
blue = open("/sys/class/leds/gta02-power:blue/brightness", "w", 1)
orange = open("/sys/class/leds/gta02-power:orange/brightness", "w", 1)
red = open("/sys/class/leds/gta02-aux:red/brightness", "w", 1)

for first,second,third, duration in notes:
playNote(first,second,third,duration)

playNote(0, 0, 0, 0)
blue.close()
orange.close()
red.close()

if __name__ == "__main__":
playFile(sys.argv[1])

==== Example Beat ====
The following is an example "fireworks"-file that can be used to test the led blinker.

1 0 0 100
1 0 1 100
1 1 0 100
0 1 0 100
0 1 1 100
0 0 1 100
1 1 1 100
1 0 0 100
1 0 1 100
1 1 0 100
0 1 0 100
0 1 1 100
0 0 1 100
1 1 1 100
1 0 0 100
1 0 1 100
1 1 0 100
0 1 0 100
0 1 1 100
0 0 1 100
1 1 1 100

== Charge State and Wi-Fi transfer ==

Seba has written a script called ledd which indicates charging state and transferring data over
wifi on the LEDs. It is available [http://openmoko.opendevice.org/~dos/ledd here].

== Power Status ==

This Perl Script
uses the blue and orange LEDs under the power button to show battery power status.

Install perl using "opkg install perl" to use this script. The script will indicate high battery with blue, medium battery by purple (blue + orange), and low battery by orange. Adjust values for your needs.

You can have it autostart by saving the script as /etc/init.d/lights.pl 
then creating a shell script /etc/init.d/startlights.sh with just one line:
/etc/init.d/lights.pl &
and then create a symlink to it to auto start by running
ln -s /etc/init.d/startlights.sh /etc/rc5.d/S15startlights

Don't forget to "chmod +x" all those scripts :)

lights.pl:

#!/usr/bin/perl
my $high_thresh = 75;
my $low_thresh = 30;
while(1) {
my $command = `apm`;
if ($command =~ m/battery .*: (\d*)%/) {
print("Value: " . $1 . "\n");
}
if($1 < $low_thresh) {
print("Low Battery\n");
$command = `echo 1 > /sys/devices/platform/gta02-led.0/leds/gta02-power:orange/brightness`;
$command = `echo 0 > /sys/devices/platform/gta02-led.0/leds/gta02-power:blue/brightness`;
}
if($1 > $high_thresh) {
print("High Battery\n");
$command = `echo 1 > /sys/devices/platform/gta02-led.0/leds/gta02-power:blue/brightness`;
$command = `echo 0 > /sys/devices/platform/gta02-led.0/leds/gta02-power:orange/brightness`;
}
if(($1 <= $high_thresh) && ($1 >= $low_thresh)){
print("Mid Battery\n");
$command = `echo 1 > /sys/devices/platform/gta02-led.0/leds/gta02-power:blue/brightness`;
$command = `echo 1 > /sys/devices/platform/gta02-led.0/leds/gta02-power:orange/brightness`;
}
sleep(15);
}

-nvanfossen

[[Category:Neo FreeRunner Hardware]]

FreeRunner/Buttons and LEDs

2008-10-12T00:05:35Z

Michaelshiloh: /* Led Power Status Perl Script */

This is the Software specification for the Openmoko Neo FreeRunner Button and LEDs.

{{InProgress}}

=Taxonomy=

==What's currently implemented==
/sys/devices/platform/gta02-led.0/leds/gta02-aux:red/
/sys/devices/platform/gta02-led.0/leds/gta02-power:blue/
/sys/devices/platform/gta02-led.0/leds/gta02-power:orange/
Those are all userspace directories for controlling the LEDs. echo 0 > brightness will turn the LED off. echo 1 > brightness will turn it on.
trigger currently does nothing.

==Buttons==
* AUX = Button on the left side of the device, upper area
* POWER = Button on the right side of the device, center area (right below the USB socket)

==Leds==
{| border=1 cellspacing=0 cellpadding=5
| EVENT
|style="background:#FF0000;color:white;"| '''red'''
| behind AUX button
|-
| HEARTBEAT
|style="background:#FF8040;color:white;"| '''orange'''
| behind POWER button
|-
| WIRELESS / BLUETOOTH
|style="background:#0000FF;color:white;"| '''blue'''
| behind POWER button
|-
| MIXING TWO LEDS
|style="background:#80409F;color:white;"| '''purple'''
| behind POWER button if turning on the blue and the orang buttons together
|}

==Modes==
* OFF = Device has no power or has been shutdown
* ON = Device is fully powered
* ON+CHARGING = Device is fully powered and has been connected to a USB host or Openmoko charger.
* LOCK = Device is fully powered, but has screen lock displayed
* SUSPEND = Device has been suspended to low-power mode

=Basic Button Usage=

This is grouped by mode:

==Mode: OFF==

* To switch the device on: Press and hold POWER until the boot logo appears.
* To enter the "normal" (NAND) boot menu: Press and hold POWER, one second later press and hold AUX.
* To enter the "rescue" (NOR) boot menu: Press and hold AUX, then press and hold POWER.

==Mode: ON==

* To suspend the device: Press POWER.
* To shut down the device: Press and hold POWER for 4 seconds. If the device hangs, press and hold POWER for 8 seconds. If it still hangs, remove the battery and disconnect from USB.
* To go to the home screen: Press AUX.
* To display the profile screen: Press and hold AUX until it appears.

==Mode: SUSPEND==

* To wakeup the device: Press POWER.

=Basic LED Usage=

LEDs are very useful in broadcasting valuable basic status information to the user in a way that the user does not have to unlock the device, enable the screen or turning the screen saver off and subsequently search the screen for basic status information.

''This is grouped by mode:''

==Mode: OFF==

* All LEDs will be turned off.

==Mode: ON==

* HEARTBEAT will emit a short blink every 4 seconds.
* If Bluetooth is powered on, WIRELESS will emit a short blink every 2 seconds.
* If Wifi is powered on, WIRELESS will emit a long blink every 2 seconds.
* If Bluetooth and Wifi are powered on, WIRELESS will be lit continuosly.

==Mode: ON+CHARGING==

''Same as ON, with the exception of''
* HEARTBEAT will increase blinking as the charge level of the battery increases.
* HEARTBEAT will be continuosly lit, if the battery has been fully charged.

==Mode: SUSPEND==

* All LEDs will be turned off.

=Advanced Button/LED Usage=

* In ON-Mode, EVENT will blink every 2 seconds if there's an event that needs your attention.
* The more events, the faster EVENT will blink.
* Pressing AUX will acknowledge the event with the topmost priority and display it to you.
* EVENT will stop to blink once all events have been acknowledged.

=A first rules implementation=
A C implementation of these rules has been [http://lists.openmoko.org/pipermail/openmoko-devel/2008-July/003458.html done by smurfy - phil] and is available at http://www.smurfy.de/files/neo/openmoko-led-v1.tar.gz

= Implementations of other LED behaviors =

== Blink LEDs by user-definable beat ==

A Python Script For Blinking Leds By Beats. This script reads beats from a file and blinks FreeRunners LEDs accordingly.

File format is human readable text, consisting of a simple sequence of integer quartet (4 numbers). The first number representing status of blue power-led, second means status of orange power-led and third means status of red aux-led. 0=OFF, 1=ON. (If blue=1 and orange=1 then power=lila. This has nothing to do with this python script or this file format.) The last number represents the duration in milliseconds to hold that situation of leds. Any non digit characters in the file count as a separators between numbers, but are otherwise ignored.

It requires packages python-core and python-re from opkg.
==== Led blinker ====

#!/usr/bin/python
"""Led Blinker Player

Usage: python leds.py [filename]
"""
import sys
import time
import re

def loadFromTextFile(filename):
infile = open(filename)
contents = infile.read()
return re.findall("(\d+)\D*(\d+)\D*(\d+)\D*(\d+)", contents)

def playNote(blue_value, orange_value, red_value, duration):
blue.write(str(blue_value) + "\n")
orange.write(str(orange_value) + "\n")
red.write(str(red_value) + "\n")
time.sleep(float(duration) / 1000.0)

def playFile(filename):
global blue, orange, red
notes = loadFromTextFile(filename)
blue = open("/sys/class/leds/gta02-power:blue/brightness", "w", 1)
orange = open("/sys/class/leds/gta02-power:orange/brightness", "w", 1)
red = open("/sys/class/leds/gta02-aux:red/brightness", "w", 1)

for first,second,third, duration in notes:
playNote(first,second,third,duration)

playNote(0, 0, 0, 0)
blue.close()
orange.close()
red.close()

if __name__ == "__main__":
playFile(sys.argv[1])

==== Example Beat ====
The following is an example "fireworks"-file that can be used to test the led blinker.

1 0 0 100
1 0 1 100
1 1 0 100
0 1 0 100
0 1 1 100
0 0 1 100
1 1 1 100
1 0 0 100
1 0 1 100
1 1 0 100
0 1 0 100
0 1 1 100
0 0 1 100
1 1 1 100
1 0 0 100
1 0 1 100
1 1 0 100
0 1 0 100
0 1 1 100
0 0 1 100
1 1 1 100

== Charge State and Wi-Fi transfer ==

Seba has written a script called ledd which indicates charging state and transferring data over
wifi on the LEDs. It is available [http://openmoko.opendevice.org/~dos/ledd here].

== Power Status ==

This Perl Script
uses the blue and orange LEDs under the power button to show battery power status.

Install perl using "opkg install perl" to use this script. The script will indicate high battery with blue, medium battery by purple (blue + orange), and low battery by orange. Adjust values for your needs.

You can have it autostart by saving the script as /etc/init.d/lights.pl 
then creating a shell script /etc/init.d/startlights.sh with just one line:
/etc/init.d/lights.pl &
and then create a symlink to it to auto start by running
ln -s /etc/init.d/startlights.sh /etc/rc5.d/S15startlights

Don't forget to "chmod +x" all those scripts :)

lights.pl:

#!/usr/bin/perl
my $high_thresh = 75;
my $low_thresh = 30;
while(1) {
my $command = `apm`;
if ($command =~ m/battery .*: (\d*)%/) {
print("Value: " . $1 . "\n");
}
if($1 < $low_thresh) {
print("Low Battery\n");
$command = `echo 1 > /sys/devices/platform/gta02-led.0/leds/gta02-power:orange/brightness`;
$command = `echo 0 > /sys/devices/platform/gta02-led.0/leds/gta02-power:blue/brightness`;
}
if($1 > $high_thresh) {
print("High Battery\n");
$command = `echo 1 > /sys/devices/platform/gta02-led.0/leds/gta02-power:blue/brightness`;
$command = `echo 0 > /sys/devices/platform/gta02-led.0/leds/gta02-power:orange/brightness`;
}
if(($1 <= $high_thresh) && ($1 >= $low_thresh)){
print("Mid Battery\n");
$command = `echo 1 > /sys/devices/platform/gta02-led.0/leds/gta02-power:blue/brightness`;
$command = `echo 1 > /sys/devices/platform/gta02-led.0/leds/gta02-power:orange/brightness`;
}
sleep(15);
}

-nvanfossen

[[Category:Neo FreeRunner Hardware]]

FreeRunner/Buttons and LEDs

2008-10-12T00:03:10Z

Michaelshiloh: /* Python Script For Blinking Leds By Beats */

This is the Software specification for the Openmoko Neo FreeRunner Button and LEDs.

{{InProgress}}

=Taxonomy=

==What's currently implemented==
/sys/devices/platform/gta02-led.0/leds/gta02-aux:red/
/sys/devices/platform/gta02-led.0/leds/gta02-power:blue/
/sys/devices/platform/gta02-led.0/leds/gta02-power:orange/
Those are all userspace directories for controlling the LEDs. echo 0 > brightness will turn the LED off. echo 1 > brightness will turn it on.
trigger currently does nothing.

==Buttons==
* AUX = Button on the left side of the device, upper area
* POWER = Button on the right side of the device, center area (right below the USB socket)

==Leds==
{| border=1 cellspacing=0 cellpadding=5
| EVENT
|style="background:#FF0000;color:white;"| '''red'''
| behind AUX button
|-
| HEARTBEAT
|style="background:#FF8040;color:white;"| '''orange'''
| behind POWER button
|-
| WIRELESS / BLUETOOTH
|style="background:#0000FF;color:white;"| '''blue'''
| behind POWER button
|-
| MIXING TWO LEDS
|style="background:#80409F;color:white;"| '''purple'''
| behind POWER button if turning on the blue and the orang buttons together
|}

==Modes==
* OFF = Device has no power or has been shutdown
* ON = Device is fully powered
* ON+CHARGING = Device is fully powered and has been connected to a USB host or Openmoko charger.
* LOCK = Device is fully powered, but has screen lock displayed
* SUSPEND = Device has been suspended to low-power mode

=Basic Button Usage=

This is grouped by mode:

==Mode: OFF==

* To switch the device on: Press and hold POWER until the boot logo appears.
* To enter the "normal" (NAND) boot menu: Press and hold POWER, one second later press and hold AUX.
* To enter the "rescue" (NOR) boot menu: Press and hold AUX, then press and hold POWER.

==Mode: ON==

* To suspend the device: Press POWER.
* To shut down the device: Press and hold POWER for 4 seconds. If the device hangs, press and hold POWER for 8 seconds. If it still hangs, remove the battery and disconnect from USB.
* To go to the home screen: Press AUX.
* To display the profile screen: Press and hold AUX until it appears.

==Mode: SUSPEND==

* To wakeup the device: Press POWER.

=Basic LED Usage=

LEDs are very useful in broadcasting valuable basic status information to the user in a way that the user does not have to unlock the device, enable the screen or turning the screen saver off and subsequently search the screen for basic status information.

''This is grouped by mode:''

==Mode: OFF==

* All LEDs will be turned off.

==Mode: ON==

* HEARTBEAT will emit a short blink every 4 seconds.
* If Bluetooth is powered on, WIRELESS will emit a short blink every 2 seconds.
* If Wifi is powered on, WIRELESS will emit a long blink every 2 seconds.
* If Bluetooth and Wifi are powered on, WIRELESS will be lit continuosly.

==Mode: ON+CHARGING==

''Same as ON, with the exception of''
* HEARTBEAT will increase blinking as the charge level of the battery increases.
* HEARTBEAT will be continuosly lit, if the battery has been fully charged.

==Mode: SUSPEND==

* All LEDs will be turned off.

=Advanced Button/LED Usage=

* In ON-Mode, EVENT will blink every 2 seconds if there's an event that needs your attention.
* The more events, the faster EVENT will blink.
* Pressing AUX will acknowledge the event with the topmost priority and display it to you.
* EVENT will stop to blink once all events have been acknowledged.

=A first rules implementation=
A C implementation of these rules has been [http://lists.openmoko.org/pipermail/openmoko-devel/2008-July/003458.html done by smurfy - phil] and is available at http://www.smurfy.de/files/neo/openmoko-led-v1.tar.gz

= Implementations of other LED behaviors =

== Blink LEDs by user-definable beat ==

A Python Script For Blinking Leds By Beats. This script reads beats from a file and blinks FreeRunners LEDs accordingly.

File format is human readable text, consisting of a simple sequence of integer quartet (4 numbers). The first number representing status of blue power-led, second means status of orange power-led and third means status of red aux-led. 0=OFF, 1=ON. (If blue=1 and orange=1 then power=lila. This has nothing to do with this python script or this file format.) The last number represents the duration in milliseconds to hold that situation of leds. Any non digit characters in the file count as a separators between numbers, but are otherwise ignored.

It requires packages python-core and python-re from opkg.
==== Led blinker ====

#!/usr/bin/python
"""Led Blinker Player

Usage: python leds.py [filename]
"""
import sys
import time
import re

def loadFromTextFile(filename):
infile = open(filename)
contents = infile.read()
return re.findall("(\d+)\D*(\d+)\D*(\d+)\D*(\d+)", contents)

def playNote(blue_value, orange_value, red_value, duration):
blue.write(str(blue_value) + "\n")
orange.write(str(orange_value) + "\n")
red.write(str(red_value) + "\n")
time.sleep(float(duration) / 1000.0)

def playFile(filename):
global blue, orange, red
notes = loadFromTextFile(filename)
blue = open("/sys/class/leds/gta02-power:blue/brightness", "w", 1)
orange = open("/sys/class/leds/gta02-power:orange/brightness", "w", 1)
red = open("/sys/class/leds/gta02-aux:red/brightness", "w", 1)

for first,second,third, duration in notes:
playNote(first,second,third,duration)

playNote(0, 0, 0, 0)
blue.close()
orange.close()
red.close()

if __name__ == "__main__":
playFile(sys.argv[1])

==== Example Beat ====
The following is an example "fireworks"-file that can be used to test the led blinker.

1 0 0 100
1 0 1 100
1 1 0 100
0 1 0 100
0 1 1 100
0 0 1 100
1 1 1 100
1 0 0 100
1 0 1 100
1 1 0 100
0 1 0 100
0 1 1 100
0 0 1 100
1 1 1 100
1 0 0 100
1 0 1 100
1 1 0 100
0 1 0 100
0 1 1 100
0 0 1 100
1 1 1 100

== Charge State and Wi-Fi transfer ==

Seba has written a script called ledd which indicates charging state and transferring data over
wifi on the LEDs. It is available [http://openmoko.opendevice.org/~dos/ledd here].

=Led Power Status Perl Script=

Use the blue and orange LED's under the power button to show battery power status. Install perl using "opkg install perl" to use this script. The script will indicate high battery with blue, medium battery by purple (blue + orange), and low battery by orange. Adjust values for your needs.

You can have it autostart by saving the script as /etc/init.d/lights.pl 
then creating a shell script /etc/init.d/startlights.sh with just one line:
/etc/init.d/lights.pl &
and then create a symlink to it to auto start by running
ln -s /etc/init.d/startlights.sh /etc/rc5.d/S15startlights

Don't forget to "chmod +x" all those scripts :)

lights.pl:

#!/usr/bin/perl
my $high_thresh = 75;
my $low_thresh = 30;
while(1) {
my $command = `apm`;
if ($command =~ m/battery .*: (\d*)%/) {
print("Value: " . $1 . "\n");
}
if($1 < $low_thresh) {
print("Low Battery\n");
$command = `echo 1 > /sys/devices/platform/gta02-led.0/leds/gta02-power:orange/brightness`;
$command = `echo 0 > /sys/devices/platform/gta02-led.0/leds/gta02-power:blue/brightness`;
}
if($1 > $high_thresh) {
print("High Battery\n");
$command = `echo 1 > /sys/devices/platform/gta02-led.0/leds/gta02-power:blue/brightness`;
$command = `echo 0 > /sys/devices/platform/gta02-led.0/leds/gta02-power:orange/brightness`;
}
if(($1 <= $high_thresh) && ($1 >= $low_thresh)){
print("Mid Battery\n");
$command = `echo 1 > /sys/devices/platform/gta02-led.0/leds/gta02-power:blue/brightness`;
$command = `echo 1 > /sys/devices/platform/gta02-led.0/leds/gta02-power:orange/brightness`;
}
sleep(15);
}

-nvanfossen

[[Category:Neo FreeRunner Hardware]]

FAQ

2008-10-11T23:53:39Z

Michaelshiloh: /* What can I do with the Neo FreeRunner? */

{{Languages|FAQ}}

== Getting Started with your Neo FreeRunner == 

=== I just received my Neo FreeRunner. Where should I start?===

See [[Getting_Started_with_your_Neo_FreeRunner|Getting Started with your Neo FreeRunner]]

=== I have a problem or a question. Where should I go? ===

First place to check is this FAQ.

If your question isn't answered here, you should search the archives of the [http://lists.openmoko.org/mailman/listinfo/community community] or [http://lists.openmoko.org/mailman/listinfo/support support] mailing lists

Next, try a larger Google search.

If you still haven't found the answer to your question, post it on the appropriate list, [http://lists.openmoko.org/mailman/listinfo/community community] or [http://lists.openmoko.org/mailman/listinfo/support support].

Provide detailed information about what you are trying to find out, and use
the Subject line to summarize your question. More tips to asking effective
questions can be found
[[http://www.catb.org/~esr/faqs/smart-questions.html|here]]

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

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

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

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

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

Right [[Download|here]].

==Openmoko==

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

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

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

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

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

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

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

Browse the wiki, and help improve it.

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

Start or join a local group near you.

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

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

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

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

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

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

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

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

The Openmoko software is not yet ready for everyday use.

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

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

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

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

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

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

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

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

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

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

=== Purchasing / Shipping / Versions ===

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

http://www.openmoko.com. We sell both directly and through a growing list of distributors.

If you buy directly from the Openmoko webshop you will pay USD $399 for the [[Neo FreeRunner]], USD $99 for the debug board. You can also purchase boxes of 10 FreeRunners at a price of USD $369 each. If you don't have a need for 10 units, you can join an existing or form a new group at [[Group_sales]].

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

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

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

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

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

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

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

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

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

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

:cat /proc/cpuinfo

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

== Neo FreeRunner Known Issues==

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

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

=== Firmware and hardware issues ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Hardware and Usage-related Questions==

=== Booting ===

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

See [[Booting_the_Neo_FreeRunner|here]]

=== Battery and Battery Charging===

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

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

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

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

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

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

See [[USB_host#Providing_power_to_run_and_charge_the_Neo_while_in_host_mode|here]]

===Wireless Connectivity===

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

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

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

The following pages contain very useful information:

* [[Gsmd|GSM Daemon]]

* [[GSM|General GSM page]]

* [[Hardware:AT_Commands|AT commands]]

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

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

See [[Neo FreeRunner Wifi]]

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

See [[GTA02 GPS]]

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

See [[GPS Problems]].

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

See [[Manually_using_Bluetooth]]

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

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

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

=== USB ===

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

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

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

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

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

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

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

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

To switch back to unpowered device mode just run:

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

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

=== Display ===

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

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

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

{{Note|This probably differs for each distribution? Need to insert, or link to, relevant info for each. --[[User:Eddsouza|eddsouza]] 09:29, 7 September 2008 (UTC)}}

Look at [[Today/2007.2#Adjust_UI_components_at_runtime]].

=== Storage ===

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

See [[Supported_microSD_cards|here]]

===System-level information===

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

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

(TBA: List of signals)

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

(TBA: List of signals)

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

Yes

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

See [[GTA02_sysfs]]

=== Inputs ===

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

See [[Switching Keyboards]]

==== How do I get a QWERTY layout software keyboard?====

See [[Switching Keyboards]]

=== Miscellaneous ===

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

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

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

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

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

==Software==

===General Questions===

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

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

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

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

====Can the software do/connect to/... ====

Reviews of the latest "bleeding edge" daily builds of the Openmoko software stack can be seen [[Snapshot_review|here]]

At the moment, the answer to many other questions is "no". The phone is at the moment a small Linux box with a touchscreen, a working dialer and some prototype apps. Most do not function in any way that would be suitable for end-users. If you want to add a feature or application request, then look over the existing [[Applications]] and either add one, or add a feature request to the applications page.

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

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

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

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

===Distributions===

====What is the stock distribution image that comes on the Neo FreeRunner?====

The 2007.2 distribution - see [[Distributions#2007.2| 2007.2 factory default software image]]

=====Are there any known issues with the factory-installed 2007.2 image on the Neo FreeRunner?=====

Yes, see [[Om_2007.2#Known_Issues|2007.2 Known Issues]]

===== Where can I download and reinstall the factory default image? =====

See [[Flashing_the_Neo_FreeRunner|Flashing the Neo FreeRunner]]

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

See [[Distributions|Distributions]]

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

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

 

====Where do I get the latest version of the official Openmoko image, 2008.8 (also known as ASU)?====

See [[Download#Om_2008.8_images_.28ASU.29| download Om 2008.8 images]]

===== Why are the buttons in TangoGPS too large? The zoom out is missing! =====

There is no GTK engine or theme installed with the ASU build. Fortunately, this is easy to fix!

At a terminal:
:<tt># opkg install moko-gtk-theme moko-gtk-engine</tt>
:<tt># ln -s /usr/share/themes/Moko/gtk-2.0/gtkrc /home/root/.gtkrc-2.0</tt>

Now you have pretty colors and widgets, but the font is too big. Edit <tt>/usr/share/themes/Moko/gtk-2.0/gtkrc</tt> in your favorite text editor and add the following line:
:<tt>gtk-font-name = "Sans 4"</tt>

To use the openmoko icon theme, install it with:
:<tt># opkg install openmoko-icon-theme-standard2</tt>

and enable it editing the <tt>/usr/share/themes/Moko/gtk-2.0/gtkrc</tt> adding the line:
:<tt>gtk-icon-theme-name="openmoko-standard"</tt>

You shouldn't even need to restart the device, although you will need to restart any GTK-based programs.

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

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

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

See [[Debian#Installation|Debian Installation]]

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

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

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

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

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

#!/bin/sh

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

=== Applications ===

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

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

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

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

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

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

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

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

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

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

=== Package Management===

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

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

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

See [[Opkg|here]]

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

See [[Opkg#Error_Codes|here]]

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

It's possible now, see [http://tropfacile.info/?/Linux/28-Openmoko-Opkg-Autocompletion-With-Packages-Names The opkg autocompletion]

===Development===

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

See [[Toolchain]].

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

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

=====QEMU=====

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

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

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

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

=====Xoo=====

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

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

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

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

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

Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].

=====Xephyr=====

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

export DISPLAY=":0.0"

and then run

xdpyinfo

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

== Distribution Customization ==

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

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

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

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

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

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

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

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

==Misc==

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

Please reply UNDER post.

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

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

site:openmoko.org text

For example, to search for accelerometer:

site:openmoko.org accelerometer

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

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

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

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

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

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

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

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

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

==Neo1973 Hardware==

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

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

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

Use provided keyboard app.

Use Bluetooth keyboard.

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

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

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

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

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

=== USB ===

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

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

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

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

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

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

The FreeRunner has the same processor as the Neo1973.

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

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

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

[[Category:Application Developer]]
[[Category:Basic End User]]
[[Category:FAQ]]

FAQ

2008-10-09T22:17:16Z

Michaelshiloh: /* How do I connect a USB memory-stick etc? */

{{Languages|FAQ}}

== Getting Started with your Neo FreeRunner == 

=== I just received my Neo FreeRunner. Where should I start?===

See [[Getting_Started_with_your_Neo_FreeRunner|Getting Started with your Neo FreeRunner]]

=== I have a problem or a question. Where should I go? ===

First place to check is this FAQ.

If your question isn't answered here, you should search the archives of the [http://lists.openmoko.org/mailman/listinfo/community community] or [http://lists.openmoko.org/mailman/listinfo/support support] mailing lists

Next, try a larger Google search.

If you still haven't found the answer to your question, post it on the appropriate list, [http://lists.openmoko.org/mailman/listinfo/community community] or [http://lists.openmoko.org/mailman/listinfo/support support].

Provide detailed information about what you are trying to find out, and use
the Subject line to summarize your question. More tips to asking effective
questions can be found
[[http://www.catb.org/~esr/faqs/smart-questions.html|here]]

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

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

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

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

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

Right [[Download|here]].

==Openmoko==

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

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

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

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

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

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

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

Browse the wiki, and help improve it.

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

Start or join a local group near you.

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

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

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

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

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

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

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

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

The Openmoko software is not yet ready for everyday use.

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

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

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

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

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

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

=== Purchasing / Shipping / Versions ===

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

http://www.openmoko.com. We sell both directly and through a growing list of distributors.

If you buy directly from the Openmoko webshop you will pay USD $399 for the [[Neo FreeRunner]], USD $99 for the debug board. You can also purchase boxes of 10 FreeRunners at a price of USD $369 each. If you don't have a need for 10 units, you can join an existing or form a new group at [[Group_sales]].

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

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

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

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

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

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

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

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

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

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

:cat /proc/cpuinfo

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

== Neo FreeRunner Known Issues==

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

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

=== Firmware and hardware issues ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Hardware and Usage-related Questions==

=== Booting ===

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

See [[Booting_the_Neo_FreeRunner|here]]

=== Battery and Battery Charging===

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

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

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

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

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

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

See [[USB_host#Providing_power_to_run_and_charge_the_Neo_while_in_host_mode|here]]

===Wireless Connectivity===

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

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

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

The following pages contain very useful information:

* [[Gsmd|GSM Daemon]]

* [[GSM|General GSM page]]

* [[Hardware:AT_Commands|AT commands]]

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

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

See [[Neo FreeRunner Wifi]]

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

See [[GTA02 GPS]]

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

See [[GPS Problems]].

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

See [[Manually_using_Bluetooth]]

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

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

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

=== USB ===

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

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

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

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

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

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

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

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

To switch back to unpowered device mode just run:

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

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

=== Display ===

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

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

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

{{Note|This probably differs for each distribution? Need to insert, or link to, relevant info for each. --[[User:Eddsouza|eddsouza]] 09:29, 7 September 2008 (UTC)}}

Look at [[Today/2007.2#Adjust_UI_components_at_runtime]].

=== Storage ===

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

See [[Supported_microSD_cards|here]]

===System-level information===

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

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

(TBA: List of signals)

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

(TBA: List of signals)

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

Yes

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

See [[GTA02_sysfs]]

=== Inputs ===

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

See [[Switching Keyboards]]

==== How do I get a QWERTY layout software keyboard?====

See [[Switching Keyboards]]

=== Miscellaneous ===

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

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

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

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

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

==Software==

===General Questions===

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

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

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

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

====Can the software do/connect to/... ====

Reviews of the latest "bleeding edge" daily builds of the Openmoko software stack can be seen [[Snapshot_review|here]]

At the moment, the answer to many other questions is "no". The phone is at the moment a small Linux box with a touchscreen, a working dialer and some prototype apps. Most do not function in any way that would be suitable for end-users. If you want to add a feature or application request, then look over the existing [[Applications]] and either add one, or add a feature request to the applications page.

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

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

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

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

===Distributions===

====What is the stock distribution image that comes on the Neo FreeRunner?====

The 2007.2 distribution - see [[Distributions#2007.2| 2007.2 factory default software image]]

=====Are there any known issues with the factory-installed 2007.2 image on the Neo FreeRunner?=====

Yes, see [[Om_2007.2#Known_Issues|2007.2 Known Issues]]

===== Where can I download and reinstall the factory default image? =====

See [[Flashing_the_Neo_FreeRunner|Flashing the Neo FreeRunner]]

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

See [[Distributions|Distributions]]

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

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

 

====Where do I get the latest version of the official Openmoko image, 2008.8 (also known as ASU)?====

See [[Download#Om_2008.8_images_.28ASU.29| download Om 2008.8 images]]

===== Why are the buttons in TangoGPS too large? The zoom out is missing! =====

There is no GTK engine or theme installed with the ASU build. Fortunately, this is easy to fix!

At a terminal:
:<tt># opkg install moko-gtk-theme moko-gtk-engine</tt>
:<tt># ln -s /usr/share/themes/Moko/gtk-2.0/gtkrc /home/root/.gtkrc-2.0</tt>

Now you have pretty colors and widgets, but the font is too big. Edit <tt>/usr/share/themes/Moko/gtk-2.0/gtkrc</tt> in your favorite text editor and add the following line:
:<tt>gtk-font-name = "Sans 4"</tt>

To use the openmoko icon theme, install it with:
:<tt># opkg install openmoko-icon-theme-standard2</tt>

and enable it editing the <tt>/usr/share/themes/Moko/gtk-2.0/gtkrc</tt> adding the line:
:<tt>gtk-icon-theme-name="openmoko-standard"</tt>

You shouldn't even need to restart the device, although you will need to restart any GTK-based programs.

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

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

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

See [[Debian#Installation|Debian Installation]]

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

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

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

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

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

#!/bin/sh

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

=== Applications ===

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

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

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

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

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

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

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

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

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

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

=== Package Management===

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

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

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

See [[Opkg|here]]

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

See [[Opkg#Error_Codes|here]]

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

It's possible now, see [http://tropfacile.info/?/Linux/28-Openmoko-Opkg-Autocompletion-With-Packages-Names The opkg autocompletion]

===Development===

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

See [[Toolchain]].

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

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

=====QEMU=====

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

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

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

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

=====Xoo=====

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

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

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

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

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

Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].

=====Xephyr=====

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

export DISPLAY=":0.0"

and then run

xdpyinfo

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

== Distribution Customization ==

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

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

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

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

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

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

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

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

==Misc==

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

Please reply UNDER post.

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

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

site:openmoko.org text

For example, to search for accelerometer:

site:openmoko.org accelerometer

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

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

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

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

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

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

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

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

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

==Neo1973 Hardware==

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

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

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

Use provided keyboard app.

Use Bluetooth keyboard.

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

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

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

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

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

=== USB ===

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

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

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

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

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

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

The FreeRunner has the same processor as the Neo1973.

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

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

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

[[Category:Application Developer]]
[[Category:Basic End User]]
[[Category:FAQ]]

FAQ

2008-10-09T22:16:50Z

Michaelshiloh: /* How do I connect a USB memory-stick etc? */

{{Languages|FAQ}}

== Getting Started with your Neo FreeRunner == 

=== I just received my Neo FreeRunner. Where should I start?===

See [[Getting_Started_with_your_Neo_FreeRunner|Getting Started with your Neo FreeRunner]]

=== I have a problem or a question. Where should I go? ===

First place to check is this FAQ.

If your question isn't answered here, you should search the archives of the [http://lists.openmoko.org/mailman/listinfo/community community] or [http://lists.openmoko.org/mailman/listinfo/support support] mailing lists

Next, try a larger Google search.

If you still haven't found the answer to your question, post it on the appropriate list, [http://lists.openmoko.org/mailman/listinfo/community community] or [http://lists.openmoko.org/mailman/listinfo/support support].

Provide detailed information about what you are trying to find out, and use
the Subject line to summarize your question. More tips to asking effective
questions can be found
[[http://www.catb.org/~esr/faqs/smart-questions.html|here]]

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

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

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

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

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

Right [[Download|here]].

==Openmoko==

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

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

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

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

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

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

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

Browse the wiki, and help improve it.

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

Start or join a local group near you.

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

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

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

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

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

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

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

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

The Openmoko software is not yet ready for everyday use.

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

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

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

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

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

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

=== Purchasing / Shipping / Versions ===

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

http://www.openmoko.com. We sell both directly and through a growing list of distributors.

If you buy directly from the Openmoko webshop you will pay USD $399 for the [[Neo FreeRunner]], USD $99 for the debug board. You can also purchase boxes of 10 FreeRunners at a price of USD $369 each. If you don't have a need for 10 units, you can join an existing or form a new group at [[Group_sales]].

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

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

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

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

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

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

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

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

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

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

:cat /proc/cpuinfo

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

== Neo FreeRunner Known Issues==

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

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

=== Firmware and hardware issues ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Hardware and Usage-related Questions==

=== Booting ===

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

See [[Booting_the_Neo_FreeRunner|here]]

=== Battery and Battery Charging===

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

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

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

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

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

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

See [[USB_host#Providing_power_to_run_and_charge_the_Neo_while_in_host_mode|here]]

===Wireless Connectivity===

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

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

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

The following pages contain very useful information:

* [[Gsmd|GSM Daemon]]

* [[GSM|General GSM page]]

* [[Hardware:AT_Commands|AT commands]]

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

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

See [[Neo FreeRunner Wifi]]

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

See [[GTA02 GPS]]

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

See [[GPS Problems]].

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

See [[Manually_using_Bluetooth]]

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

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

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

=== USB ===

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

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

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

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

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

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

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

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

To switch back to unpowered device mode just run:

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

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

=== Display ===

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

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

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

{{Note|This probably differs for each distribution? Need to insert, or link to, relevant info for each. --[[User:Eddsouza|eddsouza]] 09:29, 7 September 2008 (UTC)}}

Look at [[Today/2007.2#Adjust_UI_components_at_runtime]].

=== Storage ===

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

See [[Supported_microSD_cards|here]]

===System-level information===

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

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

(TBA: List of signals)

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

(TBA: List of signals)

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

Yes

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

See [[GTA02_sysfs]]

=== Inputs ===

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

See [[Switching Keyboards]]

==== How do I get a QWERTY layout software keyboard?====

See [[Switching Keyboards]]

=== Miscellaneous ===

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

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

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

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

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

==Software==

===General Questions===

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

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

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

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

====Can the software do/connect to/... ====

Reviews of the latest "bleeding edge" daily builds of the Openmoko software stack can be seen [[Snapshot_review|here]]

At the moment, the answer to many other questions is "no". The phone is at the moment a small Linux box with a touchscreen, a working dialer and some prototype apps. Most do not function in any way that would be suitable for end-users. If you want to add a feature or application request, then look over the existing [[Applications]] and either add one, or add a feature request to the applications page.

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

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

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

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

===Distributions===

====What is the stock distribution image that comes on the Neo FreeRunner?====

The 2007.2 distribution - see [[Distributions#2007.2| 2007.2 factory default software image]]

=====Are there any known issues with the factory-installed 2007.2 image on the Neo FreeRunner?=====

Yes, see [[Om_2007.2#Known_Issues|2007.2 Known Issues]]

===== Where can I download and reinstall the factory default image? =====

See [[Flashing_the_Neo_FreeRunner|Flashing the Neo FreeRunner]]

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

See [[Distributions|Distributions]]

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

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

 

====Where do I get the latest version of the official Openmoko image, 2008.8 (also known as ASU)?====

See [[Download#Om_2008.8_images_.28ASU.29| download Om 2008.8 images]]

===== Why are the buttons in TangoGPS too large? The zoom out is missing! =====

There is no GTK engine or theme installed with the ASU build. Fortunately, this is easy to fix!

At a terminal:
:<tt># opkg install moko-gtk-theme moko-gtk-engine</tt>
:<tt># ln -s /usr/share/themes/Moko/gtk-2.0/gtkrc /home/root/.gtkrc-2.0</tt>

Now you have pretty colors and widgets, but the font is too big. Edit <tt>/usr/share/themes/Moko/gtk-2.0/gtkrc</tt> in your favorite text editor and add the following line:
:<tt>gtk-font-name = "Sans 4"</tt>

To use the openmoko icon theme, install it with:
:<tt># opkg install openmoko-icon-theme-standard2</tt>

and enable it editing the <tt>/usr/share/themes/Moko/gtk-2.0/gtkrc</tt> adding the line:
:<tt>gtk-icon-theme-name="openmoko-standard"</tt>

You shouldn't even need to restart the device, although you will need to restart any GTK-based programs.

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

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

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

See [[Debian#Installation|Debian Installation]]

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

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

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

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

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

#!/bin/sh

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

=== Applications ===

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

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

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

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

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

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

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

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

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

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

=== Package Management===

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

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

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

See [[Opkg|here]]

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

See [[Opkg#Error_Codes|here]]

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

It's possible now, see [http://tropfacile.info/?/Linux/28-Openmoko-Opkg-Autocompletion-With-Packages-Names The opkg autocompletion]

===Development===

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

See [[Toolchain]].

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

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

=====QEMU=====

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

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

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

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

=====Xoo=====

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

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

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

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

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

Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].

=====Xephyr=====

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

export DISPLAY=":0.0"

and then run

xdpyinfo

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

== Distribution Customization ==

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

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

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

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

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

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

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

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

==Misc==

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

Please reply UNDER post.

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

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

site:openmoko.org text

For example, to search for accelerometer:

site:openmoko.org accelerometer

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

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

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

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

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

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

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

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

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

==Neo1973 Hardware==

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

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

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

Use provided keyboard app.

Use Bluetooth keyboard.

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

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

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

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

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

=== USB ===

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

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

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

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

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

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

The FreeRunner has the same processor as the Neo1973.

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

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

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

[[Category:Application Developer]]
[[Category:Basic End User]]
[[Category:FAQ]]

USB host

2008-10-09T22:15:18Z

Michaelshiloh: /* Power Concerns */

{{Languages|USB host}}
The mini-USB port on both the Neo 1973 and the Neo FreeRunner supports both USB host and USB device. This opens up a range of possibilities, such as adding USB cameras and USB input devices.

=== Selecting USB host modes ===

By default, the mini-USB port is in device mode. To tell the Neo that it is logically a host¹):

echo "host" > /sys/devices/platform/s3c2410-ohci/usb_mode

Independent of the logical mode of the USB port, the Neo FreeRunner can provide 5 volt USB power to an attached USB device. To enable this (not available on Neo 1973):

echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Note: You may want to run <code>ifconfig usb0 down</code> prior to switching to USB host mode, as the Neo's USB networking may not like having its USB port disappear. You'll probably want to ssh into your Neo over WiFi or Bluetooth before starting all of this, alternatively use an on screen keyboard.

Note that in full USB host mode the FreeRunner will power the external device. To avoid draining the battery use a powered USB hub, then on the FreeRunner enable logical host mode:

~ - echo host > /sys/devices/platform/s3c2410-ohci/usb_mode

but NOT electrical host mode

~ - echo 0 > /sys/devices/platform/neo1973-pm-host.0/hostmode

Note that powered USB hubs do not send power upstream, that is, into the host. If you wish to power or charge the FreeRunner, you will need a [[Specialized USB cables|special USB cable]].

¹)Debian note: You'll need the ohci-hcd module:
modprobe ohci-hcd

==== Returning from USB host mode to USB device mode ====

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

=== Returning to USB device mode ===
After doing whatever is needed to safely remove your device and unplugging it you can remove the provision of 5 volt power and return to device mode.

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

You can now safely restart USB networking.

====USB-Mode-Script====
These simple script is useful to switch the USB-Modes:
#!/bin/sh
grep -q 'host' /sys/devices/platform/s3c2410-ohci/usb_mode
if [ $? -eq 0 ]
then
echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode
echo "device" > /sys/devices/platform/s3c2410-ohci/usb_mode
echo USB-Port is in device-mode now.
else
ifconfig usb0 down
echo "host" > /sys/devices/platform/s3c2410-ohci/usb_mode
echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode
echo USB-Port is in host-mode now.
fi
Put it on screen for easy access.

=== Providing power to connected USB devices while in host mode ===

Normally, USB host ports provide power to any connected USB device.

Available power in host mode is the full maximum of 500mA according to USB-specifications on the Neo FreeRunner, and no power is available in host mode on the Neo 1973. If your USB device respects USB-standards and consumes not more than 500mA, you may connect it directly to your Neo FreeRunner.

To provide power to USB devices attached to your Neo 1973, or to provide power to your Neo FreeRunner while USB-device connected, you can provide power by using a (modified [for powering FreeRunner]) powered USB hub (see below), or by manually injecting power into the attached USB device (and Neo FreeRunner) via one of the [[specialized_USB_cables]].

=== Powered USB hubs known to work with the Neo ===

(please add any known to work)

=== Providing power to run and charge the Neo while in host mode ===

A slightly separate issue is power to run and charge the Neo (both types) itself. When the USB port is in device mode, the Neo FreeRunner/1973 can be powered and recharged via the USB port, but when in standard host mode, the Neo FreeRunner is set to provide power and does not charge. Fortunately, control of the direction of power (in or out) is independent of the personality of the USB port (host or device):

To recap, the direction of power can be controlled:

Set to 0 (default), no power is provided at the USB port, charging is enabled, and host 15K pulldowns are removed from D+ and D-:

echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Set to 1, provides up to 500mA USB power at the USB port (FreeRunner only), disables charging from USB, and applies 15K pulldowns to USB D+ and D-:

echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Next, power must somehow be injected. An unmodified powered USB hub only provides power to the connected devices, but not to the connected host, so the only solution here is to modify a USB-hub¹) or to create a custom cable which will inject power into the host. See [[specialized_USB_cables]] for some examples.

Finally, there is the question of charge rate. The charging logic in the Neo will only charge at 100mA by default. Charging at 500mA will take place only if the charging device responds appropriatly to USB negotiation to increase power consumption. Charging at 1000mA will only take place if the Neo detects the appropriate resistor on the ID pins.

You can manually set the charge rate. See [[Forcing_fast_charge_mode]]

¹) often it's sufficient to short a diode in USB-hub to feed power to the host-connector too.
# Edit 05 Oct. 2008 : Not being able to find any diode on my ([[User:Henrikz|Henrikz]]) USB Hub (Brand: Equip, Type: 4 port, aluminum) I simply connected +5V (pin 1) from one of the downstream ports to pin 1 of the upstream port.

=== Power Concerns ===
You'll need to force the Neo to go into fast charge mode, since it can't do its usual power negotiation over USB.

echo -n "fast_cccv" > /sys/devices/platform/s3c2410-i2c/i2c-adapter/i2c-0/0-0008/chgmode

(Also this should be done by kernel when seeing 47K at ID-pin)

=== Working Examples ===

==== Connecting a USB-Stick ====
[[Image:connecting-usb-stick-1.jpg|thumb|left]]
I found this adapter, it has 2 Type A jacks, rather cheap (about 5 €).
 

[[Image:connecting-usb-stick-2.jpg|thumb|left]]
I borrowed the cable from a card reader, it has the same pinout like the cable that comes with the Neo.
 

[[Image:connecting-usb-stick-3.jpg|thumb|left]]
With the above commands I could mount the memory stick.
 

[[Image:connecting-usb-stick-4.jpg|thumb|left]]
 

[[Category:Neo1973 Hardware]]
[[Category:Neo FreeRunner Hardware]]
[[Category:USB]]

USB host

2008-10-09T22:12:11Z

Michaelshiloh: /* Selecting USB host modes */

{{Languages|USB host}}
The mini-USB port on both the Neo 1973 and the Neo FreeRunner supports both USB host and USB device. This opens up a range of possibilities, such as adding USB cameras and USB input devices.

=== Selecting USB host modes ===

By default, the mini-USB port is in device mode. To tell the Neo that it is logically a host¹):

echo "host" > /sys/devices/platform/s3c2410-ohci/usb_mode

Independent of the logical mode of the USB port, the Neo FreeRunner can provide 5 volt USB power to an attached USB device. To enable this (not available on Neo 1973):

echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Note: You may want to run <code>ifconfig usb0 down</code> prior to switching to USB host mode, as the Neo's USB networking may not like having its USB port disappear. You'll probably want to ssh into your Neo over WiFi or Bluetooth before starting all of this, alternatively use an on screen keyboard.

Note that in full USB host mode the FreeRunner will power the external device. To avoid draining the battery use a powered USB hub, then on the FreeRunner enable logical host mode:

~ - echo host > /sys/devices/platform/s3c2410-ohci/usb_mode

but NOT electrical host mode

~ - echo 0 > /sys/devices/platform/neo1973-pm-host.0/hostmode

Note that powered USB hubs do not send power upstream, that is, into the host. If you wish to power or charge the FreeRunner, you will need a [[Specialized USB cables|special USB cable]].

¹)Debian note: You'll need the ohci-hcd module:
modprobe ohci-hcd

==== Returning from USB host mode to USB device mode ====

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

=== Returning to USB device mode ===
After doing whatever is needed to safely remove your device and unplugging it you can remove the provision of 5 volt power and return to device mode.

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

You can now safely restart USB networking.

====USB-Mode-Script====
These simple script is useful to switch the USB-Modes:
#!/bin/sh
grep -q 'host' /sys/devices/platform/s3c2410-ohci/usb_mode
if [ $? -eq 0 ]
then
echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode
echo "device" > /sys/devices/platform/s3c2410-ohci/usb_mode
echo USB-Port is in device-mode now.
else
ifconfig usb0 down
echo "host" > /sys/devices/platform/s3c2410-ohci/usb_mode
echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode
echo USB-Port is in host-mode now.
fi
Put it on screen for easy access.

=== Providing power to connected USB devices while in host mode ===

Normally, USB host ports provide power to any connected USB device.

Available power in host mode is the full maximum of 500mA according to USB-specifications on the Neo FreeRunner, and no power is available in host mode on the Neo 1973. If your USB device respects USB-standards and consumes not more than 500mA, you may connect it directly to your Neo FreeRunner.

To provide power to USB devices attached to your Neo 1973, or to provide power to your Neo FreeRunner while USB-device connected, you can provide power by using a (modified [for powering FreeRunner]) powered USB hub (see below), or by manually injecting power into the attached USB device (and Neo FreeRunner) via one of the [[specialized_USB_cables]].

=== Powered USB hubs known to work with the Neo ===

(please add any known to work)

=== Providing power to run and charge the Neo while in host mode ===

A slightly separate issue is power to run and charge the Neo (both types) itself. When the USB port is in device mode, the Neo FreeRunner/1973 can be powered and recharged via the USB port, but when in standard host mode, the Neo FreeRunner is set to provide power and does not charge. Fortunately, control of the direction of power (in or out) is independent of the personality of the USB port (host or device):

To recap, the direction of power can be controlled:

Set to 0 (default), no power is provided at the USB port, charging is enabled, and host 15K pulldowns are removed from D+ and D-:

echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Set to 1, provides up to 500mA USB power at the USB port (FreeRunner only), disables charging from USB, and applies 15K pulldowns to USB D+ and D-:

echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Next, power must somehow be injected. An unmodified powered USB hub only provides power to the connected devices, but not to the connected host, so the only solution here is to modify a USB-hub¹) or to create a custom cable which will inject power into the host. See [[specialized_USB_cables]] for some examples.

Finally, there is the question of charge rate. The charging logic in the Neo will only charge at 100mA by default. Charging at 500mA will take place only if the charging device responds appropriatly to USB negotiation to increase power consumption. Charging at 1000mA will only take place if the Neo detects the appropriate resistor on the ID pins.

You can manually set the charge rate. See [[Forcing_fast_charge_mode]]

¹) often it's sufficient to short a diode in USB-hub to feed power to the host-connector too.
# Edit 05 Oct. 2008 : Not being able to find any diode on my ([[User:Henrikz|Henrikz]]) USB Hub (Brand: Equip, Type: 4 port, aluminum) I simply connected +5V (pin 1) from one of the downstream ports to pin 1 of the upstream port.

=== Power Concerns ===
You'll need to force the Neo to go into fast charge mode, since it can't do its usual power negotiation over USB.

echo -n "fast_cccv" > /sys/devices/platform/s3c2410-i2c/i2c-adapter/i2c-0/0-0008/chgmode

(Also this should be done by kernel when seeing 47K at ID-pin)

[[Category:Neo1973 Hardware]]
[[Category:Neo FreeRunner Hardware]]
[[Category:USB]]

FAQ

2008-10-09T15:33:20Z

Michaelshiloh: /* How do I get the WLAN (802.11, Wi-Fi, wireless network) working? */

{{Languages|FAQ}}

== Getting Started with your Neo FreeRunner == 

=== I just received my Neo FreeRunner. Where should I start?===

See [[Getting_Started_with_your_Neo_FreeRunner|Getting Started with your Neo FreeRunner]]

=== I have a problem or a question. Where should I go? ===

First place to check is this FAQ.

If your question isn't answered here, you should search the archives of the [http://lists.openmoko.org/mailman/listinfo/community community] or [http://lists.openmoko.org/mailman/listinfo/support support] mailing lists

Next, try a larger Google search.

If you still haven't found the answer to your question, post it on the appropriate list, [http://lists.openmoko.org/mailman/listinfo/community community] or [http://lists.openmoko.org/mailman/listinfo/support support].

Provide detailed information about what you are trying to find out, and use
the Subject line to summarize your question. More tips to asking effective
questions can be found
[[http://www.catb.org/~esr/faqs/smart-questions.html|here]]

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

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

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

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

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

Right [[Download|here]].

==Openmoko==

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

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

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

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

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

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

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

Browse the wiki, and help improve it.

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

Start or join a local group near you.

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

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

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

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

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

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

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

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

The Openmoko software is not yet ready for everyday use.

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

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

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

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

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

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

=== Purchasing / Shipping / Versions ===

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

http://www.openmoko.com. We sell both directly and through a growing list of distributors.

If you buy directly from the Openmoko webshop you will pay USD $399 for the [[Neo FreeRunner]], USD $99 for the debug board. You can also purchase boxes of 10 FreeRunners at a price of USD $369 each. If you don't have a need for 10 units, you can join an existing or form a new group at [[Group_sales]].

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

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

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

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

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

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

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

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

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

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

:cat /proc/cpuinfo

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

== Neo FreeRunner Known Issues==

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

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

=== Firmware and hardware issues ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Hardware and Usage-related Questions==

=== Booting ===

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

See [[Booting_the_Neo_FreeRunner|here]]

=== Battery and Battery Charging===

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

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

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

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

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

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

See [[USB_host#Providing_power_to_run_and_charge_the_Neo_while_in_host_mode|here]]

===Wireless Connectivity===

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

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

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

The following pages contain very useful information:

* [[Gsmd|GSM Daemon]]

* [[GSM|General GSM page]]

* [[Hardware:AT_Commands|AT commands]]

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

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

See [[Neo FreeRunner Wifi]]

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

See [[GTA02 GPS]]

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

See [[GPS Problems]].

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

See [[Manually_using_Bluetooth]]

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

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

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

=== USB ===

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

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

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

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

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

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

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

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

To switch back to unpowered device mode just run:

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

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

=== Display ===

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

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

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

{{Note|This probably differs for each distribution? Need to insert, or link to, relevant info for each. --[[User:Eddsouza|eddsouza]] 09:29, 7 September 2008 (UTC)}}

Look at [[Today/2007.2#Adjust_UI_components_at_runtime]].

=== Storage ===

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

See [[Supported_microSD_cards|here]]

===System-level information===

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

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

(TBA: List of signals)

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

(TBA: List of signals)

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

Yes

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

See [[GTA02_sysfs]]

=== Inputs ===

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

See [[Switching Keyboards]]

==== How do I get a QWERTY layout software keyboard?====

See [[Switching Keyboards]]

=== Miscellaneous ===

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

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

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

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

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

==Software==

===General Questions===

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

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

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

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

====Can the software do/connect to/... ====

Reviews of the latest "bleeding edge" daily builds of the Openmoko software stack can be seen [[Snapshot_review|here]]

At the moment, the answer to many other questions is "no". The phone is at the moment a small Linux box with a touchscreen, a working dialer and some prototype apps. Most do not function in any way that would be suitable for end-users. If you want to add a feature or application request, then look over the existing [[Applications]] and either add one, or add a feature request to the applications page.

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

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

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

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

===Distributions===

====What is the stock distribution image that comes on the Neo FreeRunner?====

The 2007.2 distribution - see [[Distributions#2007.2| 2007.2 factory default software image]]

=====Are there any known issues with the factory-installed 2007.2 image on the Neo FreeRunner?=====

Yes, see [[Om_2007.2#Known_Issues|2007.2 Known Issues]]

===== Where can I download and reinstall the factory default image? =====

See [[Flashing_the_Neo_FreeRunner|Flashing the Neo FreeRunner]]

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

See [[Distributions|Distributions]]

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

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

 

====Where do I get the latest version of the official Openmoko image, 2008.8 (also known as ASU)?====

See [[Download#Om_2008.8_images_.28ASU.29| download Om 2008.8 images]]

===== Why are the buttons in TangoGPS too large? The zoom out is missing! =====

There is no GTK engine or theme installed with the ASU build. Fortunately, this is easy to fix!

At a terminal:
:<tt># opkg install moko-gtk-theme moko-gtk-engine</tt>
:<tt># ln -s /usr/share/themes/Moko/gtk-2.0/gtkrc /home/root/.gtkrc-2.0</tt>

Now you have pretty colors and widgets, but the font is too big. Edit <tt>/usr/share/themes/Moko/gtk-2.0/gtkrc</tt> in your favorite text editor and add the following line:
:<tt>gtk-font-name = "Sans 4"</tt>

To use the openmoko icon theme, install it with:
:<tt># opkg install openmoko-icon-theme-standard2</tt>

and enable it editing the <tt>/usr/share/themes/Moko/gtk-2.0/gtkrc</tt> adding the line:
:<tt>gtk-icon-theme-name="openmoko-standard"</tt>

You shouldn't even need to restart the device, although you will need to restart any GTK-based programs.

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

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

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

See [[Debian#Installation|Debian Installation]]

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

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

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

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

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

#!/bin/sh

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

=== Applications ===

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

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

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

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

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

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

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

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

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

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

=== Package Management===

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

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

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

See [[Opkg|here]]

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

See [[Opkg#Error_Codes|here]]

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

It's possible now, see [http://tropfacile.info/?/Linux/28-Openmoko-Opkg-Autocompletion-With-Packages-Names The opkg autocompletion]

===Development===

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

See [[Toolchain]].

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

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

=====QEMU=====

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

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

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

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

=====Xoo=====

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

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

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

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

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

Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].

=====Xephyr=====

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

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

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

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

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

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

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

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

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

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

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

==== Does it support Ruby? ====

For Ruby 1.9, please refer to http://blog.sparkymat.net/2008/08/10/ruby-19-on-openmoko/

For Ruby 1.8.6, please refer to http://blog.wolfman.com/articles/2008/08/10/ruby-1-8-6-on-openmoko-freerunner

==== Does it support Python? ====

Yes, with some caveats. See [[Python]] for more information.

====How do I dump details about X11 configuration and extensions? ====

Run the command xdpyinfo. Generally, you would do this via an SSH session to the phone, so you may need to first

export DISPLAY=":0.0"

and then run

xdpyinfo

For an example invocation, see [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].

== Distribution Customization ==

{{Note| Suggestion: this should be split off into a separate page, since many of the questions below aren't really overview-level but specialized; a question like "How do I customize a distribution?" could be added to the Software - Distributions part, linking to the new page. --[[User:Eddsouza|eddsouza]] 07:35, 7 September 2008 (UTC)}}

=== Compilation & packaging ===
==== What is the 'overlay' approach to bitbake development? ====
:You can create a local overlay for the bitbake build chain and develop in the overlay as described in [[Application_Development_Crash_Course| Application Development Crash Course]].

==== Which .bb files are related with the Openmoko? ====
==== Are there any configuration files for Openmoko? ====
==== How can I port an application written with autotools to Openmoko? ====
After you source the [[Toolchain|Openmoko toolchain]] variables, the Openmoko processor compiler becomes the default compiler. You can compile any GNU - like project just typing ''./configure --host i686'' and then ''make'' - it will produce libraries and executables as expected. Just these executables will not run on your i686 host - they will run on Openmoko ARM processor. Use scp to upload the executables to your phone.

==== How can I add an application written with autotools to the openmoko tree? ====

==== How can I make changes in the openmoko applications? ====
==== How can I submit my changes? ====
==== Can I use the mokomakefile in the development process? How? ====

:Yes, [[MokoMakefile]] can be used in the development process. See [[MokoMakefile#Developing_with_MokoMakefile| Developing with MokoMakefile]].

==== What's the way to include/exclude a newly added package to/from the final rootfs? ====
==== Where do the final ipk & binary files reside? ====
:ipk files are in
./build/tmp/deploy/glibc/ipk/
:binary images are in
./build/tmp/deploy/glibc/images/fic-gta01/

==== How can I add an application to the applications list? ====
==== How can I assign an image to my new application to be seen in the applications list? ====
The Openmoko project tree contains the folder 'data' where you can put any 128*128 icon. You need to mention the icon in two places in this folder:
* Makefile.am must contain the line dist_appicon_DATA = <icon_name>.png
* The <application_name>.desktop file that must be in this folder should contain the Icon=<icon_name> (without file type).

==Misc==

===On the lists on lists.openmoko.org, should replies be added above or below the original text? ===

Please reply UNDER post.

===How can I find out if a question or topic has already been discussed on the mailing lists? ===

By searching the mailing list archives. For example, using Google searches:

site:openmoko.org text

For example, to search for accelerometer:

site:openmoko.org accelerometer

If you only want to read the "official" mails from FIC people or from Openmoko people:

site:openmoko.org text "at fic.com.tw"
site:openmoko.org text "at openmoko.org"

For example to search for "release date" from FIC people:

site:openmoko.org "release date" "at fic.com.tw"

Alternatively you can use the [http://www.google.com/coop/cse?cx=018430699993342716089%3Aszsaurhronw custom Openmoko search engine] that is using [http://www.google.com/coop/ Google Co-op].

===how many dead pixels may the LCM have before calling it defect? ===

The answer for the display used in GTA01 and GTA02 is '2'

=== how many visits does this wiki have? ===
See this [[Wiki_statistic_numbers|wiki's statistics]] page.

=Historical=
The Neo1973 was last available in Febuary 2008.

==Neo1973 Hardware==

===What are the hardware specifications of Neo 1973 ? ===

See page [[Neo1973_Hardware]] and category [[:Category:Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]]

===How do I input text? ===

Use provided keyboard app.

Use Bluetooth keyboard.

For more methods and ideas see [[Wishlist:Text_Input]].

===Can I record calls and/or play audio files in calls? ===

Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing an [[Answering Machine]] is possible. Also using text->speech should be possible or modifying outgoing voice. Currently there is no software bundled in phone to do this.
There are only 2 A/D inputs and three D/A outputs (one dedicated to the earpiece). This means that stereo audio playback cannot happen at the same time as the [[Answering Machine]] functionality, amongst other things. See the audio page. [[Neo1973_Audio_Subsystem|Neo1973 Audio Subsystem]]

===What is the battery life? ===

There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].

=== USB ===

====What can I do with the USB port on the Neo? ====
Charge the phone, communicate with it over USB-serial, or USB-networking.

Plug external devices, such as wifi, cameras, or mass-storage devices.

====What can't I do with the USB? ====

The only limitation on current hardware seems to be no usb 2.0 support, which means slower communication with 2.0 devices.

====Why is only USB 1.1 provided? ====

The processor has USB 1.1 built in. One with USB2 built in would have been more expensive, and might not be open.

The FreeRunner has the same processor as the Neo1973.

====What are the details of the USB port on the Neo? How does it compare to USB On-The-Go? ====

The Neo will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just
an AB socket, but also electrical and software components which cannot be provide by the S3C2410.

You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).

[[Category:Application Developer]]
[[Category:Basic End User]]
[[Category:FAQ]]

Neo FreeRunner Wifi

2008-10-09T15:29:26Z

Michaelshiloh: /* Other sample wpa_supplicant.conf files */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

=== wpa_supplicant.conf ===

==== wpa_supplicant.conf explained ====
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

==== Sample wpa_supplicant.conf ====

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

==== Other working sample wpa_supplicant.conf files ====

Tom Yates documents his success [http://www.teaparty.net/technotes/openmoko-2.html#Wifi here]

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using iwconfig manually ===

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Known Issues ==

=== GUI doesn't work in all cases ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use
[[Neo_FreeRunner_Wifi#Using_iwconfig_manually|iwconfig manually]].

=== iwconfig doesn't work in all cases ===

Note that for some reason our iwconfig requires a more constrained format than the generic iwconfig. See
[[Neo_FreeRunner_Wifi#Using_iwconfig_manually| using iwconfig manually]].

=== Anecdotal solutions ===

These solutions worked for some people:

==== Disable power management ====

Some APs apparently get upset by power managed devices, and the Freerunner enables power management of the wifi by default to preserve battery. One user's wrt54g certainly gets upset from time to time if he connect with the FreeRunner, sometimes refusing to talk to _anything_ over wifi afterwards until rebooted.

==== Modified script ====

"I changed the script a little:

Exec=xterm -e "ifconfig eth0 down \
iwconfig eth0 txpower off channel 0 \
while killall wpa_supplicant; do echo 'Killing wpa_sup'; done \
killall udhcpc \
wpa_supplicant -i eth0 -c /etc/wpa_supplicant/wpa_supplicant.conf -D wext -B \
sleep 10; udhcpc"

Now it is working every time.
I am using 2008.latest (081004) and a linksys WAP54G accesspoint,

==== Use a different channel ====

"Could not get it to work properly on channel 11, so I set my accesspoint to channel 1."

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T23:24:26Z

Michaelshiloh: /* iwconfig doesn't work in all cases */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

=== wpa_supplicant.conf ===

==== wpa_supplicant.conf explained ====
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

==== Sample wpa_supplicant.conf ====

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

==== Other sample wpa_supplicant.conf files ====

Tom Yates documents his success [http://www.teaparty.net/technotes/openmoko-2.html#Wifi here]

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using iwconfig manually ===

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Known Issues ==

=== GUI doesn't work in all cases ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use
[[Neo_FreeRunner_Wifi#Using_iwconfig_manually|iwconfig manually]].

=== iwconfig doesn't work in all cases ===

Note that for some reason our iwconfig requires a more constrained format than the generic iwconfig. See
[[Neo_FreeRunner_Wifi#Using_iwconfig_manually| using iwconfig manually]].

=== Anecdotal solutions ===

These solutions worked for some people:

==== Disable power management ====

Some APs apparently get upset by power managed devices, and the Freerunner enables power management of the wifi by default to preserve battery. One user's wrt54g certainly gets upset from time to time if he connect with the FreeRunner, sometimes refusing to talk to _anything_ over wifi afterwards until rebooted.

==== Modified script ====

"I changed the script a little:

Exec=xterm -e "ifconfig eth0 down \
iwconfig eth0 txpower off channel 0 \
while killall wpa_supplicant; do echo 'Killing wpa_sup'; done \
killall udhcpc \
wpa_supplicant -i eth0 -c /etc/wpa_supplicant/wpa_supplicant.conf -D wext -B \
sleep 10; udhcpc"

Now it is working every time.
I am using 2008.latest (081004) and a linksys WAP54G accesspoint,

==== Use a different channel ====

"Could not get it to work properly on channel 11, so I set my accesspoint to channel 1."

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T23:24:05Z

Michaelshiloh: /* GUI doesn't work in all cases */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

=== wpa_supplicant.conf ===

==== wpa_supplicant.conf explained ====
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

==== Sample wpa_supplicant.conf ====

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

==== Other sample wpa_supplicant.conf files ====

Tom Yates documents his success [http://www.teaparty.net/technotes/openmoko-2.html#Wifi here]

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using iwconfig manually ===

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Known Issues ==

=== GUI doesn't work in all cases ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use
[[Neo_FreeRunner_Wifi#Using_iwconfig_manually|iwconfig manually]].

=== iwconfig doesn't work in all cases ===

Note that for some reason our iwconfig requires a more constrained format than the generic iwconfig. See
[[Neo_FreeRunner_Wifi#Using_wpa_supplicant_manually| using iwconfig manually]].

=== Anecdotal solutions ===

These solutions worked for some people:

==== Disable power management ====

Some APs apparently get upset by power managed devices, and the Freerunner enables power management of the wifi by default to preserve battery. One user's wrt54g certainly gets upset from time to time if he connect with the FreeRunner, sometimes refusing to talk to _anything_ over wifi afterwards until rebooted.

==== Modified script ====

"I changed the script a little:

Exec=xterm -e "ifconfig eth0 down \
iwconfig eth0 txpower off channel 0 \
while killall wpa_supplicant; do echo 'Killing wpa_sup'; done \
killall udhcpc \
wpa_supplicant -i eth0 -c /etc/wpa_supplicant/wpa_supplicant.conf -D wext -B \
sleep 10; udhcpc"

Now it is working every time.
I am using 2008.latest (081004) and a linksys WAP54G accesspoint,

==== Use a different channel ====

"Could not get it to work properly on channel 11, so I set my accesspoint to channel 1."

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T23:23:28Z

Michaelshiloh: /* GUI doesn't work in all cases */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

=== wpa_supplicant.conf ===

==== wpa_supplicant.conf explained ====
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

==== Sample wpa_supplicant.conf ====

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

==== Other sample wpa_supplicant.conf files ====

Tom Yates documents his success [http://www.teaparty.net/technotes/openmoko-2.html#Wifi here]

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using iwconfig manually ===

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Known Issues ==

=== GUI doesn't work in all cases ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use
[[Neo_FreeRunner_Wifi#Using_wpa_supplicant_manually|iwconfig manually]].

=== iwconfig doesn't work in all cases ===

Note that for some reason our iwconfig requires a more constrained format than the generic iwconfig. See
[[Neo_FreeRunner_Wifi#Using_wpa_supplicant_manually| using iwconfig manually]].

=== Anecdotal solutions ===

These solutions worked for some people:

==== Disable power management ====

Some APs apparently get upset by power managed devices, and the Freerunner enables power management of the wifi by default to preserve battery. One user's wrt54g certainly gets upset from time to time if he connect with the FreeRunner, sometimes refusing to talk to _anything_ over wifi afterwards until rebooted.

==== Modified script ====

"I changed the script a little:

Exec=xterm -e "ifconfig eth0 down \
iwconfig eth0 txpower off channel 0 \
while killall wpa_supplicant; do echo 'Killing wpa_sup'; done \
killall udhcpc \
wpa_supplicant -i eth0 -c /etc/wpa_supplicant/wpa_supplicant.conf -D wext -B \
sleep 10; udhcpc"

Now it is working every time.
I am using 2008.latest (081004) and a linksys WAP54G accesspoint,

==== Use a different channel ====

"Could not get it to work properly on channel 11, so I set my accesspoint to channel 1."

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T23:22:01Z

Michaelshiloh: /* GUI doesn't work in all cases */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

=== wpa_supplicant.conf ===

==== wpa_supplicant.conf explained ====
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

==== Sample wpa_supplicant.conf ====

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

==== Other sample wpa_supplicant.conf files ====

Tom Yates documents his success [http://www.teaparty.net/technotes/openmoko-2.html#Wifi here]

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using iwconfig manually ===

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Known Issues ==

=== GUI doesn't work in all cases ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use
[[Neo_FreeRunner_Wifi#Using_wpa_supplicant_manually|iwconfig manually]].

=== Anecdotal solutions ===

These solutions worked for some people:

==== Disable power management ====

Some APs apparently get upset by power managed devices, and the Freerunner enables power management of the wifi by default to preserve battery. One user's wrt54g certainly gets upset from time to time if he connect with the FreeRunner, sometimes refusing to talk to _anything_ over wifi afterwards until rebooted.

==== Modified script ====

"I changed the script a little:

Exec=xterm -e "ifconfig eth0 down \
iwconfig eth0 txpower off channel 0 \
while killall wpa_supplicant; do echo 'Killing wpa_sup'; done \
killall udhcpc \
wpa_supplicant -i eth0 -c /etc/wpa_supplicant/wpa_supplicant.conf -D wext -B \
sleep 10; udhcpc"

Now it is working every time.
I am using 2008.latest (081004) and a linksys WAP54G accesspoint,

==== Use a different channel ====

"Could not get it to work properly on channel 11, so I set my accesspoint to channel 1."

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T23:20:37Z

Michaelshiloh: /* Known Issues with GUI */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

=== wpa_supplicant.conf ===

==== wpa_supplicant.conf explained ====
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

==== Sample wpa_supplicant.conf ====

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

==== Other sample wpa_supplicant.conf files ====

Tom Yates documents his success [http://www.teaparty.net/technotes/openmoko-2.html#Wifi here]

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using iwconfig manually ===

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Known Issues ==

=== GUI doesn't work in all cases ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

=== Anecdotal solutions ===

These solutions worked for some people:

==== Disable power management ====

Some APs apparently get upset by power managed devices, and the Freerunner enables power management of the wifi by default to preserve battery. One user's wrt54g certainly gets upset from time to time if he connect with the FreeRunner, sometimes refusing to talk to _anything_ over wifi afterwards until rebooted.

==== Modified script ====

"I changed the script a little:

Exec=xterm -e "ifconfig eth0 down \
iwconfig eth0 txpower off channel 0 \
while killall wpa_supplicant; do echo 'Killing wpa_sup'; done \
killall udhcpc \
wpa_supplicant -i eth0 -c /etc/wpa_supplicant/wpa_supplicant.conf -D wext -B \
sleep 10; udhcpc"

Now it is working every time.
I am using 2008.latest (081004) and a linksys WAP54G accesspoint,

==== Use a different channel ====

"Could not get it to work properly on channel 11, so I set my accesspoint to channel 1."

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T23:19:37Z

Michaelshiloh: /* WEP */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

=== wpa_supplicant.conf ===

==== wpa_supplicant.conf explained ====
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

==== Sample wpa_supplicant.conf ====

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

==== Other sample wpa_supplicant.conf files ====

Tom Yates documents his success [http://www.teaparty.net/technotes/openmoko-2.html#Wifi here]

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using iwconfig manually ===

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Known Issues ==

=== Known Issues with GUI ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

=== Anecdotal solutions ===

These solutions worked for some people:

==== Disable power management ====

Some APs apparently get upset by power managed devices, and the Freerunner enables power management of the wifi by default to preserve battery. One user's wrt54g certainly gets upset from time to time if he connect with the FreeRunner, sometimes refusing to talk to _anything_ over wifi afterwards until rebooted.

==== Modified script ====

"I changed the script a little:

Exec=xterm -e "ifconfig eth0 down \
iwconfig eth0 txpower off channel 0 \
while killall wpa_supplicant; do echo 'Killing wpa_sup'; done \
killall udhcpc \
wpa_supplicant -i eth0 -c /etc/wpa_supplicant/wpa_supplicant.conf -D wext -B \
sleep 10; udhcpc"

Now it is working every time.
I am using 2008.latest (081004) and a linksys WAP54G accesspoint,

==== Use a different channel ====

"Could not get it to work properly on channel 11, so I set my accesspoint to channel 1."

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T23:18:55Z

Michaelshiloh: /* Using iwconfig manually */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

=== wpa_supplicant.conf ===

==== wpa_supplicant.conf explained ====
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

==== Sample wpa_supplicant.conf ====

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

==== Other sample wpa_supplicant.conf files ====

Tom Yates documents his success [http://www.teaparty.net/technotes/openmoko-2.html#Wifi here]

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Known Issues ==

=== Known Issues with GUI ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

=== Anecdotal solutions ===

These solutions worked for some people:

==== Disable power management ====

Some APs apparently get upset by power managed devices, and the Freerunner enables power management of the wifi by default to preserve battery. One user's wrt54g certainly gets upset from time to time if he connect with the FreeRunner, sometimes refusing to talk to _anything_ over wifi afterwards until rebooted.

==== Modified script ====

"I changed the script a little:

Exec=xterm -e "ifconfig eth0 down \
iwconfig eth0 txpower off channel 0 \
while killall wpa_supplicant; do echo 'Killing wpa_sup'; done \
killall udhcpc \
wpa_supplicant -i eth0 -c /etc/wpa_supplicant/wpa_supplicant.conf -D wext -B \
sleep 10; udhcpc"

Now it is working every time.
I am using 2008.latest (081004) and a linksys WAP54G accesspoint,

==== Use a different channel ====

"Could not get it to work properly on channel 11, so I set my accesspoint to channel 1."

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T23:18:18Z

Michaelshiloh: /* Known Issues with GUI */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

=== wpa_supplicant.conf ===

==== wpa_supplicant.conf explained ====
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

==== Sample wpa_supplicant.conf ====

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

==== Other sample wpa_supplicant.conf files ====

Tom Yates documents his success [http://www.teaparty.net/technotes/openmoko-2.html#Wifi here]

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Known Issues ==

=== Known Issues with GUI ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

==== Using iwconfig manually ====

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

=== Anecdotal solutions ===

These solutions worked for some people:

==== Disable power management ====

Some APs apparently get upset by power managed devices, and the Freerunner enables power management of the wifi by default to preserve battery. One user's wrt54g certainly gets upset from time to time if he connect with the FreeRunner, sometimes refusing to talk to _anything_ over wifi afterwards until rebooted.

==== Modified script ====

"I changed the script a little:

Exec=xterm -e "ifconfig eth0 down \
iwconfig eth0 txpower off channel 0 \
while killall wpa_supplicant; do echo 'Killing wpa_sup'; done \
killall udhcpc \
wpa_supplicant -i eth0 -c /etc/wpa_supplicant/wpa_supplicant.conf -D wext -B \
sleep 10; udhcpc"

Now it is working every time.
I am using 2008.latest (081004) and a linksys WAP54G accesspoint,

==== Use a different channel ====

"Could not get it to work properly on channel 11, so I set my accesspoint to channel 1."

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Battery

2008-10-08T23:12:49Z

Michaelshiloh: /* What to do if your battery has become completely discharged */

{{Neo FreeRunner Menu}}
=== GTA02 1200 mAh Smart Battery ===

*Using SANYO 1200mAh cell
*Battery Technical information: [http://people.openmoko.org/tony_tu/GTA02/hardware/GTA02/CT-GTA02.pdf Detailed Battery Information]

* 1200mAh Smart Battery with Coulomb-counter and protection circuit
* The Smart Battery keeps track of maximum and current capacity for precise prediction of remaining battery power and time until shutdown, based on actual power dissipation.

For more information, see the GTA01 battery info at [[Neo1973 Battery]]

=== Notes about expected battery life ===
Battery life is a work in progress. The power saving software is in a very rudimentary state. At the moment 12h is about the most (note though a [http://lists.openmoko.org/pipermail/community/2008-July/020339.html recent result of at least 21h], mostly in suspend, with multiple short wakeups, on the predecessor device GTA01). A week standby and 6 hours talk, 20 hours mp3 might be attainable when power saving software is complete.

== Known Issues ==

=== Make sure your battery never discharges completely. ===

This is an issue because the internal charging circuitry can not be turned on until the FreeRunner has booted, and booting through USB power alone does not work.

==== What to do if your battery has become completely discharged ====

See the workarounds [[Neo_FreeRunner_Hardware_Issues#Can.27t_boot_with_discharged_or_missing_battery|here]].

==== More tricks ====

''Q: Does anyone know WHY it don't charge when it is off? My logic says that it is very important to have the option charge the battery when it is flat.''

A: I can't give you a simple answer. Charging is controlled by the PCF50633
chip, based on configuration values that are written to it by u-boot,
Linux, and userspace programs. Some of these settings are preserved
across a power-cycle (the PCF50633 has a small backup battery that's
also used to keep the RTC running) so the behavior at startup depends on
the software that you used during your last session.

Another complication is that some Freerunners are capable of starting up
without a battery while others are not (possibly due to different
capacitor values on the internal power rails).

I can give a few hints:
* The current (Sep. 2nd, 2008) u-boot has a bug that means it will not properly charge from the wall charger. Try a USB cable into a PC instead.
* Try booting through NOR u-boot instead (hold aux and then power) with both the wall charger or a 500mA USB connection, then try booting Linux.
* Try to boot into the NAND u-boot menu (hold power and then aux) and then select "power off". This may leave the device in a state were it will charge. Wait 15 minutes and then try to boot Linux.
* If the device shuts off during one of the above attempts, let it sit for a few minutes and then try that same item once again

Kudos to Mike Montour on the
[http://lists.openmoko.org/pipermail/community/2008-September/029243.html Community mailing list].

== Compatible Replacement Batteries ==

Other known FreeRunner-compatible batteries include the BL-series (BL-4X, BL-5X) from Nokia, and their third-party equivalents.
These may not work to revive a device and may not report charge information.
It is probably a good idea to check that your battery is not greater than the stock battery's voltage of 3.7V (the above suggests that 4.5VDC should be fine) unless you know what you are doing.

{| border="1" cellpadding="4" cellspacing="0"
!Battery Model
!Capacity (mAh)
!Charge info reported
!Notes
|-
|NOKIA BL-4
|
|no
|
|-
|NOKIA BL-4C
|750
|no
|Slightly thinner than original.
|-
|NOKIA BL-5B
|760/890
|
|
|-
|NOKIA BL-5C
|950
|no
|
|-
|NOKIA BL-6C
|1070
|no
|
|-
|NOKIA BR-6C
|?
|no
|
|}

== Alien Charging of Battery ==

Nokia devices (phones and stand-alone chargers) usually will not charge
non-Nokia batteries, most likely because they can't be sure they have
the correct charging parameters (and of course Nokia isn't interested in supporting use of alien batteries with their phones).

Most after-market or no-name brands of Nokia-compatible chargers don't
test the make of the battery, most likely because adding the capability
to perform this test would add to the cost of the charger and limit it's universal character (that's not the interest of second source manufacturers).

Thus:
* You can use a Nokia or Nokia-compatible BL-4C, BL-5C, or BL-6C in the Neo
* You can charge the Neo battery in a Nokia-compatible charger that is not Nokia branded
* You can NOT charge the Neo battery in a Nokia branded phone or charger

For more information about USB battery chargers that can be used with the Neo FreeRunner see
{{main|USB charger}}

== DIY external battery pack from a Minty case ==

'''Mintyboost:'''

Charge from a couple of AA batteries: [http://www.ladyada.net/make/mintyboost/ Minty Boost!], [http://www.millions.ca/~stacy/mintyboost/ report on a Neo FreeRunner application].

Adding the 47k resistor to the minty boost so that the Freerunner fast charges at 1A is a poor idea for a couple reasons, the biggest one being that the minty boost can't supply 1A the max is 600mA. as far as I know, there is no magic resistor to identify a 500mA charger to the Freerunner, it depends on USB host telling it that it can provide 500mA. Second, the ID pin is in the USB micro connector, so you would either need to put a micro connector on your minty boost (with the correct resistor installed) or use a hacked cable.

Even if the Linear Technology step up voltage converter is supposed to be able to do 600mA, the AA cells seem to have a problem with supplying 500mA. They get a little toasty :-). One powerpack built using D cells doesn't seem to have any issues with supplying 500mA.

[[Category:Battery]]
[[Category:Neo FreeRunner Hardware]]

Neo FreeRunner Battery

2008-10-08T23:11:04Z

Michaelshiloh: /* Make sure your battery never discharges completely. */

{{Neo FreeRunner Menu}}
=== GTA02 1200 mAh Smart Battery ===

*Using SANYO 1200mAh cell
*Battery Technical information: [http://people.openmoko.org/tony_tu/GTA02/hardware/GTA02/CT-GTA02.pdf Detailed Battery Information]

* 1200mAh Smart Battery with Coulomb-counter and protection circuit
* The Smart Battery keeps track of maximum and current capacity for precise prediction of remaining battery power and time until shutdown, based on actual power dissipation.

For more information, see the GTA01 battery info at [[Neo1973 Battery]]

=== Notes about expected battery life ===
Battery life is a work in progress. The power saving software is in a very rudimentary state. At the moment 12h is about the most (note though a [http://lists.openmoko.org/pipermail/community/2008-July/020339.html recent result of at least 21h], mostly in suspend, with multiple short wakeups, on the predecessor device GTA01). A week standby and 6 hours talk, 20 hours mp3 might be attainable when power saving software is complete.

== Known Issues ==

=== Make sure your battery never discharges completely. ===

This is an issue because the internal charging circuitry can not be turned on until the FreeRunner has booted, and booting through USB power alone does not work.

==== What to do if your battery has become completely discharged ====

See the workarounds for [[Neo_FreeRunner_Hardware_Issues#PMU.2FCharger_Issue|PMU/Charger Issue]]

==== More tricks ====

''Q: Does anyone know WHY it don't charge when it is off? My logic says that it is very important to have the option charge the battery when it is flat.''

A: I can't give you a simple answer. Charging is controlled by the PCF50633
chip, based on configuration values that are written to it by u-boot,
Linux, and userspace programs. Some of these settings are preserved
across a power-cycle (the PCF50633 has a small backup battery that's
also used to keep the RTC running) so the behavior at startup depends on
the software that you used during your last session.

Another complication is that some Freerunners are capable of starting up
without a battery while others are not (possibly due to different
capacitor values on the internal power rails).

I can give a few hints:
* The current (Sep. 2nd, 2008) u-boot has a bug that means it will not properly charge from the wall charger. Try a USB cable into a PC instead.
* Try booting through NOR u-boot instead (hold aux and then power) with both the wall charger or a 500mA USB connection, then try booting Linux.
* Try to boot into the NAND u-boot menu (hold power and then aux) and then select "power off". This may leave the device in a state were it will charge. Wait 15 minutes and then try to boot Linux.
* If the device shuts off during one of the above attempts, let it sit for a few minutes and then try that same item once again

Kudos to Mike Montour on the
[http://lists.openmoko.org/pipermail/community/2008-September/029243.html Community mailing list].

== Compatible Replacement Batteries ==

Other known FreeRunner-compatible batteries include the BL-series (BL-4X, BL-5X) from Nokia, and their third-party equivalents.
These may not work to revive a device and may not report charge information.
It is probably a good idea to check that your battery is not greater than the stock battery's voltage of 3.7V (the above suggests that 4.5VDC should be fine) unless you know what you are doing.

{| border="1" cellpadding="4" cellspacing="0"
!Battery Model
!Capacity (mAh)
!Charge info reported
!Notes
|-
|NOKIA BL-4
|
|no
|
|-
|NOKIA BL-4C
|750
|no
|Slightly thinner than original.
|-
|NOKIA BL-5B
|760/890
|
|
|-
|NOKIA BL-5C
|950
|no
|
|-
|NOKIA BL-6C
|1070
|no
|
|-
|NOKIA BR-6C
|?
|no
|
|}

== Alien Charging of Battery ==

Nokia devices (phones and stand-alone chargers) usually will not charge
non-Nokia batteries, most likely because they can't be sure they have
the correct charging parameters (and of course Nokia isn't interested in supporting use of alien batteries with their phones).

Most after-market or no-name brands of Nokia-compatible chargers don't
test the make of the battery, most likely because adding the capability
to perform this test would add to the cost of the charger and limit it's universal character (that's not the interest of second source manufacturers).

Thus:
* You can use a Nokia or Nokia-compatible BL-4C, BL-5C, or BL-6C in the Neo
* You can charge the Neo battery in a Nokia-compatible charger that is not Nokia branded
* You can NOT charge the Neo battery in a Nokia branded phone or charger

For more information about USB battery chargers that can be used with the Neo FreeRunner see
{{main|USB charger}}

== DIY external battery pack from a Minty case ==

'''Mintyboost:'''

Charge from a couple of AA batteries: [http://www.ladyada.net/make/mintyboost/ Minty Boost!], [http://www.millions.ca/~stacy/mintyboost/ report on a Neo FreeRunner application].

Adding the 47k resistor to the minty boost so that the Freerunner fast charges at 1A is a poor idea for a couple reasons, the biggest one being that the minty boost can't supply 1A the max is 600mA. as far as I know, there is no magic resistor to identify a 500mA charger to the Freerunner, it depends on USB host telling it that it can provide 500mA. Second, the ID pin is in the USB micro connector, so you would either need to put a micro connector on your minty boost (with the correct resistor installed) or use a hacked cable.

Even if the Linear Technology step up voltage converter is supposed to be able to do 600mA, the AA cells seem to have a problem with supplying 500mA. They get a little toasty :-). One powerpack built using D cells doesn't seem to have any issues with supplying 500mA.

[[Category:Battery]]
[[Category:Neo FreeRunner Hardware]]

Openmoko Local Groups

2008-10-08T23:09:11Z

Michaelshiloh:

'''Openmoko Local Groups...'''

* can be used for developers to meet and get to know each other
* can be used for developing
* may provide the room for real-life discussions away from mailinglists/wiki
* can support early support handling their GTA01Bv4 and exchange experiences
* fasten the community's cohesion
* give motivation

Note that the list below is manually maintained. To make sure you don't miss a group, please check the [[:Category:Openmoko_Local_Groups|Openmoko local groups category]] too. If you happen to find any missing groups, please add them here.

Note the list below was created during the Neo 1973 era. When the Neo FreeRunner came out, a different type of local group came into existence, as a result of discounts available with volume purchases. To find these local groups visit [[group sales|here]]

== Africa ==
* South Africa
**[[Openmoko_Local_Groups: Cape Town|Cape Town]]

== America ==

* Brasil
** [[Openmoko_Local_Groups: Belo Horizonte|Belo Horizonte]]

* Canada
** Alberta
*** [[Openmoko_Local_Groups: Calgary|Calgary]]
*** [[Openmoko_Local_Groups: Edmonton|Edmonton]]
*** [[Openmoko_Local_Groups: Pincher Creek|Pincher Creek]]
** British Columbia
*** [[Openmoko Local Groups: Victoria|Victoria]]
*** [[Openmoko_Local_Groups: Vancouver|Vancouver]]
** Ontario
*** [[Openmoko_Local_Groups: Ottawa|Ottawa]]
*** [[Openmoko_Local_Groups: Toronto|Toronto]]
** Quebec
*** [[Openmoko_Local_Groups: Montreal|Montreal]]

* Colombia
** [[Openmoko_Local_Groups: Bogota|Bogotá]]

* México
** [[Openmoko_Local_Groups: Monterrey|Monterrey]]

* USA
** Alabama
*** [[Openmoko_Local_Groups: Alabama|Alabama]]
** Arizona
*** [[Openmoko_Local_Groups: Arizona|Arizona]]
** Arkansas
*** [[Openmoko_Local_Groups: Arkansas|Arkansas]]
** California
*** [[Openmoko_Local_Groups: San Diego|San Diego]]
*** [[Openmoko_Local_Groups: San Francisco|San Francisco]]
*** [[Openmoko_Local_Groups: Sacramento|Sacramento]]
*** [[Openmoko_Local_Groups: Los Angeles|Los Angeles]]
*** [[Openmoko_Local_Groups: Santa Barbara|Santa Barbara]]
** Colorado
*** [[Openmoko_Local_Groups: Colorado Springs|Colorado Springs]]
*** [[Openmoko_Local_Groups: Denver|Denver]]
** District of Columbia
*** [[Openmoko_Local_Groups: Washington DC Metro | Washington DC Metro]]
** Florida
*** [[Openmoko_Local_Groups: Central Florida | Central Florida]]
** Georgia
*** [[Openmoko_Local_Groups: Atlanta | Atlanta]]
** Illinois
*** [[Openmoko_Local_Groups: Chicago|Chicago]]
** Indiana
*** [[Openmoko_Local_Groups: Bloomington|Bloomington]]
** Iowa
*** [[Openmoko_Local_Groups: Iowa-Ames | Iowa-Ames]]
** Massachusetts
*** [[Openmoko_Local_groups: Boston|Boston]]
** Michigan
*** [[Openmoko_Local_Groups: Detroit|Detroit]]
** Missouri
*** [[Openmoko_Local_Groups: St. Louis|St. Louis]]
** New Jersey
*** [[Openmoko_Local_Groups: Stevens Institute of Technology, Hoboken NJ | Stevens Institute of Technology, Hoboken NJ ]]
** New York
*** [[Openmoko_Local_Groups: NYC Metro | NYC Metro]]
** North Carolina
*** [[Openmoko Local_Groups: Charlotte | Charlotte]]
** North Dakota
*** [[Openmoko_Local_Groups: Fargo]]
** Ohio
*** [[Openmoko_Local_Groups: Cleveland|Cleveland]]
** Oregon
*** [[Openmoko_Local_Groups: Eugene|Eugene]]
*** [[Openmoko_Local_Groups: Portland|Portland]]
** Pennsylvania
*** [[Openmoko_Local_Groups: Pittsburgh|Pittsburgh]]
** Texas
*** [[Openmoko_Local_Groups: North Texas|North Texas]]
*** [[Openmoko_Local_Groups: Central Texas|Central Texas]]
*** [[Openmoko_Local_Groups: East Texas|East Texas]]
** Utah
*** [[Openmoko_Local_Groups: Salt Lake|Salt Lake]]
** Virginia
*** [[Openmoko_Local_Groups: Virginia|Virginia]]
** Washington
*** [[Openmoko_Local_Groups: Washington|Pacific Northwest]]

* Uruguay
** [[Openmoko_Local_Groups: Montevideo|Montevideo]]

* [[Openmoko Local Groups: Venezuela|Venezuela]]
** [[Openmoko_Local_Groups: Caracas|Caracas]]

== Asia ==
* Pakistan
** [[Openmoko_Local_Groups: Islamabad|Islamabad]]
* India
** [[Openmoko_Local_Groups: Bangalore|Bangalore]]
** [[Openmoko_Local_Groups: Delhi|Delhi]]
** [[Openmoko_Local_Groups: Hyderabad|Hyderabad]]
* Singapore
** [[Openmoko_Local_Groups: Singapore|Singapore]]
* Kazakhstan
** [[Openmoko_Local_Groups: Karaganda|Karaganda]]
* China
** [[Openmoko_Local_Groups: China|China]]
* Taiwan
** [[Openmoko_Local_Groups: Taiwan|Taiwan]]

== Europe ==

* Austria
** [[Openmoko_Local_Groups: Vienna|Vienna]]
** [[Openmoko_Local_Groups: Innsbruck|Innsbruck]]

* [[Openmoko_Local_Groups: Belgium|Belgium]]
** [[Openmoko_local_Groups: Antwerp|Antwerp]]
** [[Openmoko_local_Groups:_Brussels|Brussels]]

* [[Openmoko_Local_Groups:_Denmark|Denmark]]
** [[Openmoko_Local_Groups: Copenhagen|Copenhagen]]
** [[Openmoko_Local_Groups: Aalborg|Aalborg]]

*[[Openmoko_Local_Groups: Estonia|Estonia]]
** [[Openmoko_Local_Groups: Kuressaare|Kuressaare]]

* [[Openmoko_Local_Groups: Finland|Finland]]
** [[Openmoko_Local_Groups: Helsinki|Helsinki]]

* [[Openmoko_Local_Groups: France|France]]
** [[Openmoko_Local_Groups: Grenoble|Grenoble]]
** [[Openmoko_Local_Groups: Lyon|Lyon]]
** [[Openmoko_Local_Groups: Paris|Paris]]
** [[Openmoko_Local_Groups: Rennes|Rennes]]
** [[Openmoko_Local_Groups: Toulouse|Toulouse]]
** [[Openmoko Local Groups: Alsace|Alsace]]

* Germany
** [[Openmoko_Local_Groups: Aachen|Aachen]]
** [[Openmoko_Local_Groups: Berlin|Berlin]]
** [[Openmoko_Local_Groups: Braunschweig|Braunschweig]]
** [[Openmoko_Local_Groups: Dortmund|Dortmund]]
** [[Openmoko_Local_Groups: Dresden|Dresden]]
** [[Openmoko_Local_Groups: Duesseldorf|Duesseldorf]]
** [[Openmoko_Local_Groups: Erlangen-Nuernberg|Erlangen-Nuernberg]]
** [[Openmoko_Local_Groups: Frankfurt Main|Frankfurt Main]]
** [[Openmoko_Local_Groups: Freiburg im Breisgau|Freiburg im Breisgau]]
** [[Openmoko_Local_Groups: Hamburg|Hamburg]]
** [[Openmoko_Local_Groups: OWL|OWL]]
** [[Openmoko_Local_Groups: Ingolstadt|Ingolstadt]]
** [[Openmoko_Local_Groups: Munich|München]]
** [[Openmoko_Local_Groups: Trier|Trier]]
** [[Openmoko_Local_Groups: Ulm|Ulm]]
** [[Openmoko_Local_Groups: Rülzheim|Rülzheim]]

* Greece
** [[Openmoko_Local_Groups: Athens|Athens]]

* Iceland
** [[Openmoko_Local_Groups: Reykjavík|Reykjavík]]

* Italy
** [[Openmoko_Local_Groups: Milan|Milan]]
** [[Openmoko_Local_Groups: Turin|Turin]]

* [[Openmoko_Local_Groups:_Netherlands|Netherlands]]
** [[Openmoko_Local_Groups: Amsterdam|Amsterdam]]
** [[Openmoko_Local_Groups: Den Haag|Den Haag/The Hague]]
** [[Openmoko_Local_Groups: Eindhoven|Eindhoven]]
** [[Openmoko_Local_Groups: Ede|Ede]]

* [[Openmoko_Local_Groups:_Norway|Norway]]
** [[Openmoko_Local_Groups:_Oslo|Oslo]]
** [[Openmoko_Local_Groups: Trondheim|Trondheim]]

* Poland
** [[Openmoko_Local_Groups: Warsaw|Warsaw]]
** [[Openmoko_Local_Groups: Szczecin|Szczecin]]

* [[Openmoko_Local_Groups:_Portugal|Portugal]]
** [[Openmoko_Local_Groups: Braga|Braga]]

* Romania
** [[Openmoko_Local_Groups: Bucharest|Bucharest]]

* [[Openmoko Local Groups: Russia|Russia]]
** [[Openmoko_Local_Groups: Moscow|Moscow]]
** [[Openmoko_Local_Groups: Saint-Petersburg|Saint-Petersburg]]

* Slovakia
** [[Openmoko_Local_Groups: Bratislava|Bratislava]]

* [[Openmoko_Local_Groups:_Spain|Spain]]
** [[Openmoko_Local_Groups: Madrid|Madrid]]
** [[Openmoko_Local_Groups: Tenerife|Santa Cruz de Tenerife]]
** [[Openmoko_Local_Groups: Baleares|Islas Baleares]]

* Sweden
** [[Openmoko_Local_Groups: Gothenburg|Gothenburg]]
** [[Openmoko_Local_Groups: Linkoping|Linköping]]
** [[Openmoko_Local_Groups: Stockholm|Stockholm]]
** [[Openmoko_Local_Groups: Umea|Umeå]]

* [[Openmoko_Local_Groups: Switzerland|Switzerland]]
** [[Openmoko_Local_Groups: Bern|Bern]]

* UK
** England
*** [[Openmoko_Local_Groups: Birmingham|Birmingham]]
*** [[Openmoko_Local_Groups: Cambridge|Cambridge]]
*** [[Openmoko_Local_Groups: London|London]]
*** [[Openmoko_Local_Groups: Manchester|Manchester]]
*** [[Openmoko_Local_Groups: East Midlands|East Midlands]]
** Scotland
*** [[Openmoko_Local_Groups: Fife|Fife]]
*** [[Openmoko_Local_Groups: Edinburgh|Edinburgh]]

* Ukraine
** [[Openmoko_Local_Groups: Lugansk|Lugansk]]

== Oceania ==

* Australia
** [[Openmoko_Local_Groups: Adelaide|Adelaide]]
** [[Openmoko_Local_Groups: Canberra|Canberra]]
** [[Openmoko_Local_Groups: Melbourne|Melbourne]]
** [[Openmoko_Local_Groups: Perth|Perth]]
** [[Openmoko_Local_Groups: Sydney|Sydney]]

* New Zealand
** [[Openmoko_Local_Groups: Auckland|Auckland]]
** [[Openmoko_Local_Groups: Wellington|Wellington]]
** [[Openmoko_Local_Groups: Christchurch|Christchurch]]

== How to edit local group lists ==

{|border="1"
!
!Has Device
|-
|If you have a device, on your local group's page, please add:
|[[Image: Moko.jpg|center]]
<nowiki>[[Image: Moko.jpg|center]]</nowiki>
|-
!
!Has Debug Board
|-
|If you have a debug board, please add:
|[[Image: MokoBox.jpg|center]]
<nowiki>[[Image: MokoBox.jpg|center]]</nowiki>
|}

Such as with [[Openmoko_Local_Groups:_Singapore | Singapore]] or [[Openmoko_Local_Groups:_San_Francisco | San Francisco]]

[[Category:Community]]
[[Category:Openmoko Local Groups]]

Neo FreeRunner Wifi

2008-10-08T22:57:08Z

Michaelshiloh: /* Disable power management */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

=== wpa_supplicant.conf ===

==== wpa_supplicant.conf explained ====
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

==== Sample wpa_supplicant.conf ====

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

==== Other sample wpa_supplicant.conf files ====

Tom Yates documents his success [http://www.teaparty.net/technotes/openmoko-2.html#Wifi here]

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Known Issues ==

=== Known Issues with GUI ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

=== Anecdotal solutions ===

These solutions worked for some people:

==== Disable power management ====

Some APs apparently get upset by power managed devices, and the Freerunner enables power management of the wifi by default to preserve battery. One user's wrt54g certainly gets upset from time to time if he connect with the FreeRunner, sometimes refusing to talk to _anything_ over wifi afterwards until rebooted.

==== Modified script ====

"I changed the script a little:

Exec=xterm -e "ifconfig eth0 down \
iwconfig eth0 txpower off channel 0 \
while killall wpa_supplicant; do echo 'Killing wpa_sup'; done \
killall udhcpc \
wpa_supplicant -i eth0 -c /etc/wpa_supplicant/wpa_supplicant.conf -D wext -B \
sleep 10; udhcpc"

Now it is working every time.
I am using 2008.latest (081004) and a linksys WAP54G accesspoint,

==== Use a different channel ====

"Could not get it to work properly on channel 11, so I set my accesspoint to channel 1."

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T22:51:52Z

Michaelshiloh: /* Using WEP and /etc/network/interfaces */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

=== wpa_supplicant.conf ===

==== wpa_supplicant.conf explained ====
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

==== Sample wpa_supplicant.conf ====

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

==== Other sample wpa_supplicant.conf files ====

Tom Yates documents his success [http://www.teaparty.net/technotes/openmoko-2.html#Wifi here]

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Known Issues ==

=== Known Issues with GUI ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

=== Anecdotal solutions ===

These solutions worked for some people:

==== Disable power management ====

Some APs apparently get upset by power managed devices, and the Freerunner enables power management of the wifi by default to preserve battery. One user's wrt54g certainly gets upset from time to time if he connect with the FreeRunner, sometimes refusing to talk to _anything_ over wifi afterwards until rebooted.

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T22:48:34Z

Michaelshiloh: /* Known Issues with GUI */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

=== wpa_supplicant.conf ===

==== wpa_supplicant.conf explained ====
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

==== Sample wpa_supplicant.conf ====

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

==== Other sample wpa_supplicant.conf files ====

Tom Yates documents his success [http://www.teaparty.net/technotes/openmoko-2.html#Wifi here]

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T22:36:05Z

Michaelshiloh: /* Sample wpa_supplicant.conf */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

=== Known Issues with GUI ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

=== wpa_supplicant.conf ===

==== wpa_supplicant.conf explained ====
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

==== Sample wpa_supplicant.conf ====

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

==== Other sample wpa_supplicant.conf files ====

Tom Yates documents his success [http://www.teaparty.net/technotes/openmoko-2.html#Wifi here]

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T22:31:40Z

Michaelshiloh: /* Sample wpa_supplicant.conf */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

=== Known Issues with GUI ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

=== Sample wpa_supplicant.conf ===

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

==== wpa_supplicant.conf explained ====
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T22:30:36Z

Michaelshiloh: /* Using WPA and /etc/network/interfaces */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

=== Known Issues with GUI ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

== Sample wpa_supplicant.conf ==

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

======wpa_supplicant.conf explained======
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T22:29:53Z

Michaelshiloh: /* Sample wpa_supplicant.conf */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

=== Known Issues with GUI ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T22:29:09Z

Michaelshiloh: /* WPA */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

=== Known Issues with GUI ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is an encryption method for securing your wireless network.

=== Using wpa_supplicant manually ===

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]].

Bring up your wireless connection:

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

=== Using WPA and /etc/network/interfaces ===

Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== Sample wpa_supplicant.conf ==

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

======wpa_supplicant.conf explained======
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T22:26:24Z

Michaelshiloh: /* Using wpa_supplicant manually */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

=== Known Issues with GUI ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

=== Using WPA and /etc/network/interfaces ===

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is a encryption method for securing your wireless network.
Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== Sample wpa_supplicant.conf ==

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

======wpa_supplicant.conf explained======
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T22:26:03Z

Michaelshiloh: /* Using WEP and /etc/network/interfaces */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

=== Known Issues with GUI ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

=== Using WPA and /etc/network/interfaces ===

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is a encryption method for securing your wireless network.
Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

== WEP ==

[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.

=== Using WEP and /etc/network/interfaces ===
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Using wpa_supplicant manually ==

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]]

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== Sample wpa_supplicant.conf ==

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

======wpa_supplicant.conf explained======
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T22:24:55Z

Michaelshiloh: /* Using WPA and /etc/network/interfaces */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

=== Known Issues with GUI ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== WPA ==

=== Using WPA and /etc/network/interfaces ===

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is a encryption method for securing your wireless network.
Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

== Using WEP and /etc/network/interfaces==
[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Using wpa_supplicant manually ==

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]]

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== Sample wpa_supplicant.conf ==

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

======wpa_supplicant.conf explained======
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T22:23:01Z

Michaelshiloh: /* Manual attempt */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

=== Known Issues with GUI ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== Using WPA and /etc/network/interfaces==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is a encryption method for securing your wireless network.
Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

== Using WEP and /etc/network/interfaces==
[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Using wpa_supplicant manually ==

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]]

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== Sample wpa_supplicant.conf ==

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

======wpa_supplicant.conf explained======
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

Neo FreeRunner Wifi

2008-10-08T22:17:13Z

Michaelshiloh: /* Using the GUI on 2008.8 */

{{Languages|Neo FreeRunner Menu}}

This page documents the [http://en.wikipedia.org/wiki/Wireless_networking wireless networking] solutions commonly known as [http://en.wikipedia.org/wiki/Wireless_LAN WLAN] or WiFi.

There are other ways to enable wireless communications on the Neo, including [[Bluetooth]]. For Bluetooth solutions, see [[How to use bluetooth to transfer data between Neo and Desk-top]] and [[Manually using Bluetooth]].

== Using the GUI on 2008.8 ==

In the Settings application on Om 2008.8, there's a "WiFi" item. It should work fairly well in stable-updated 2008.8 (even with WPA2).

If it says "WiFi unknown", you can delete the /etc/volatives.cache file and reboot. It should work after that.[http://docs.openmoko.org/trac/ticket/1734] After connecting using the GUI, you may also need to run "udhcpc eth0" manually in the terminal to get DNS entries added to your resolv.conf. You may also need to run "ifdown usb0" to remove the routing issue caused by having both interfaces up at the same time. Some users have reported that 802.11g modulation needs to be enabled on APs to allow the FreeRunner to connect (The hardware is suppose to support 802.11b/g).

Otherwise there's also [[lint-wifi]]. Refer to the section below, [[#Available Software|"Available Software"]] to find out what else might be available.

=== Known Issues with GUI ===

The GUI seems to have some issues that prevent it from working in all cases.

If a Wi-Fi connection can not be made with the GUI, open a shell and use iwconfig manually.

Note that for WEP our iwconfig requires a more specific format than generic iwconfig.

The canonical way of running iwconfig for WEP would be something like this:

# iwconfig eth0 key A4BEB3B8EC essid xyz

Two things are important here:

* the key must be in HEX. iwconfig will not do anything useful if the key is given as a string. [http://www.powerdog.com/wepkey.cgi Here] is a handy ASCII string to HEX converter.

* the ESSID must follow the key.

If an incorrect key was set, please stop all activity on the interface for at least two minutes (i.e., killall udhcpc and ifconfig eth0 down), then issue the correct iwconfig command and retry.

== How can I tell what Access Points (APs) are visible to me? ==

You can connect to wireless networks through wireless [http://en.wikipedia.org/wiki/Access_point| access points]. If you want to know the names of all the access points that are currently visible to you, you can perform a scan with this command:

root@om-gta02:~# '''iwlist eth0 scan'''

If anything is visible you will get a list that looks something like this:

eth0 Scan completed :
Cell 01 - Address: 00:16:B6:DE:77:58
ESSID:"StarvinMarvin"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=9/94 Signal level=-86 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2020000
Cell 02 - Address: 00:21:29:AA:10:97
ESSID:"CandT Network"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=39/94 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Extra:wpa_ie=dd1c0050f20101000050f20202000050f2040050f20201000050f2020000
Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
Cell 03 - Address: 00:14:95:1B:8E:B9
ESSID:"2WIRE852"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=5/94 Signal level=-90 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100
Cell 04 - Address: 00:E0:98:52:3D:78
ESSID:"smith"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=36/94 Signal level=-59 dBm Noise level=-95 dBm
Encryption key:on
Extra:bcn_int=100

If you want to connect to an unsecured network run:

udhcpc

== Using WPA and /etc/network/interfaces==

[http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access WPA] is a encryption method for securing your wireless network.
Once you have a [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]] file, add a line under the eth0 entry in /etc/network/interfaces:
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Save your changes and run:
# ifdown eth0 && ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

== Using WEP and /etc/network/interfaces==
[http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy WEP] is an encryption method for securing your wireless network. WEP is generally considered to be weak, you should use WPA instead if possible.
iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Save your changes and run:
# ifdown eth0 && ifup eth0

== Manual attempt ==

Create and edit a suitable [[GTA02_WLAN#Sample_wpa_supplicant.conf|/etc/wpa_supplicant/wpa_supplicant.conf]]

root@om-gta02:~# ifup eth0
root@om-gta02:~# wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
root@om-gta02:~# udhcpc eth0

== Wake up from wireless (wow)==

Wi-Fi module constantly drain currents after module power up, for wi-fi SIP phone or some application need long standby time, will need wake up from wireless function for power saving. There is a sleep mode that Ar6k supported for wake up from wireless.

http://svn.openmoko.org/trunk/src/target/AR6kSDK.build_sw.18/host/tools/wmiconfig

export ATH_CROSS_COMPILE_TYPE=arm-angstrom-linux-gnueabi-
make

Debian package:

wget http://meshy.org/~ato/debian/pool/main/w/wmiconfig/wmiconfig_0.0.18-1_armel.deb
dpkg -i wmiconfig_0.0.18-1_armel.deb

Basically, it's achieved via wmiconfig tool to issue IOCTL if we want
ar6k wifi module to generate interrupt to host controller. The procedure
to enable wakeup-on-wireless(wow) is listed here:

1. wmiconfig --sethostmode asleep /* to tell ar6k what host's current is */
2. wmiconfig --setwowmode enable /* enable wow function */
3. wmiconfig --addpattern 0 1 33 01 ff /* add packet filter pattern, this is the ICMP filter pattern */
4. apm -s
5. ping IP_of_Neo
6. The GPIO1 pin would be pulled up. The system would resume then.
7. wmiconfig --sethostmode awake /* The firmware of ar6k will pull low the GPIO1 pin */

--addwowpattern <list-id> <pattern-size> <pattern-offset> <pattern> <pattern-mask>

Here are some addwowpattern commands:

Protocol type=IP=0800
Protocol type in IP header=ICMP=01

- To filter for IP packets(offset 22)
wmiconfig --addwowpattern 0 2 22 0800 ffff
- To filter for ICMP packets (offset 33)
wmiconfig --addwowpattern 0 1 33 01 ff

== Sample wpa_supplicant.conf ==

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=your_hex_key
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

======wpa_supplicant.conf explained======
The highest priority is tried first then falls back to the next highest number.

priority=100 1st 
then 
priority=99 
<pre>

# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
network={
ssid="AP_ESSID"
psk="presharedkey"
priority=5
}

#try open AP regardless of its SSID.
# change root password before you go roaming around it could prove dangerous
network={
key_mgmt=NONE
priority=1 #try any open AP last
}
</pre>

A more in depth explanation can be found here: 
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

Note: Don't forget to make this script executable with "chmod +x <filename>"

== Route internet connection through Wifi rather than USB ==

Wifi is faster than USB, so it is a good idea to tell the FreeRunner to connect through it. Put the following in /etc/network/interfaces under eth0:

up route del default gw 192.168.0.200

This will remove your computer as the default gateway and use the wireless one when the interface is brought up. User nickd reports that sometimes it fails so he has had to put it in twice.

== ssh into FR over WiFi ==
dropbear, the ssh server, is configured to listen on the USB interface only. Wireless interfaces like wlan or bluetooth are disabled for security reasons (empty root password).

If you want to enable ssh over WiFi, change the /etc/default/dropbear from:

DROPBEAR_PORT=`ip addr list usb0 | awk 'BEGIN { FS="[ /]+" } /inet / { print $3 }'`:22

(which actually only prepends the usb0 ip address before the :22)

into:

DROPBEAR_PORT=22

* Be careful with this config file since it can close the only door into your phone.

* Set a root password!

== Available Software ==

Programs in development providing GUI interfaces to administer WiFi connections:

* [[Lint-wifi]]
* [[Mofi]]
* [[Camp-Wifi]]

== External links ==

* [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ WiFi on Linux]

[[Category:Neo FreeRunner Hardware]]
[[Category:Networking]]

FAQ

2008-10-08T22:04:05Z

Michaelshiloh: /* How do I get the WLAN working? */

{{Languages|FAQ}}

== Getting Started with your Neo FreeRunner == 

=== I just received my Neo FreeRunner. Where should I start?===

See [[Getting_Started_with_your_Neo_FreeRunner|Getting Started with your Neo FreeRunner]]

=== I have a problem or a question. Where should I go? ===

First place to check is this FAQ.

If your question isn't answered here, you should search the archives of the [http://lists.openmoko.org/mailman/listinfo/community community] or [http://lists.openmoko.org/mailman/listinfo/support support] mailing lists

Next, try a larger Google search.

If you still haven't found the answer to your question, post it on the appropriate list, [http://lists.openmoko.org/mailman/listinfo/community community] or [http://lists.openmoko.org/mailman/listinfo/support support].

Provide detailed information about what you are trying to find out, and use
the Subject line to summarize your question. More tips to asking effective
questions can be found
[[http://www.catb.org/~esr/faqs/smart-questions.html|here]]

If your question requires confidentiality, you are welcome to contact [mailto:michael@openmoko.org Michael Shiloh] directly.

You might also look for [[Openmoko_Local_Groups|local Openmoko users]] to find
some local support. A few minutes with a live person might solve a simple
misunderstanding that would take hours to understand via email. (If a local
club doesn't exist, this might be the perfect opportunity to start one!)

=== I'd like to develop a custom product or application based on Openmoko and/or the Neo FreeRunner. How should I proceed? ===

Send mail to michael@openmoko.org or to steve@openmoko.com

=== Where are the latest downloads? ===

Right [[Download|here]].

==Openmoko==

===What is Openmoko?===
Openmoko is two things:

Openmoko is a Linux distribution designed for open mobile computing platforms, such as, but not limited to, cellphones.

Openmoko is the company behind the Openmoko Linux distribution. Openmoko also manufactures mobile computing platforms, such as the Neo FreeRunner.

===What is the purpose of this project?===

By providing a completely open source Linux distribution, and by opening the schematics and CAD files, Openmoko's goal is to nurture explosive innovation (such as occurred with the Personal Computer) in the field of connected mobile computing, cellphones, and ubiquitous computing.

===How do I join the Openmoko project? ===

Join one or more of the mailing lists. A great place to start is the community list.

Browse the wiki, and help improve it.

Start or join an [[http://projects.openmoko.org/ Openmoko project]].

Start or join a local group near you.

===I'm not a programmer, but I have other skills. Can I still be of use? ===

Absolutely. If you're a visual artist, you can help us with icons and other visuals. Musicians can help contribute ringtones and other sounds. Marketing? Sales? Information visualization? Join the community mailing lists, introduce yourself, and you'll soon find a place to put your skills to good use.

== Neo FreeRunner - Introductory/Overview/Conceptual Information==

=== What is the [[Neo FreeRunner]]? ===

The [[Neo FreeRunner]] is an open cellphone designed for the Openmoko Linux distribution. By open we mean that (a) all chips have been chosen to allow their drivers to be completely open sourced and (b) the schematics and the plastic (CAD) files are available as well.

For more details, see [[Neo FreeRunner|Neo FreeRunner specifications]]

=== What can I do with the Neo FreeRunner? ===

The Neo FreeRunner is designed for everyday use by end users and for continued software development and improvements by the Openmoko team and the Openmoko community.

The Openmoko software is not yet ready for everyday use.

The question is almost what can you NOT do with this phone - eventually there will be a huge range of free software applications allowing both end users and developers to get much more out of this phone than a standard "locked" mobile phone using features like the integrated GPS, bluetooth, wifi and accelerometers.

=== What are the benefits of an "open" phone over a "closed" phone? ===

In a conventional closed phone, the handset maker and the mobile network operator work together to provide a service to you that best suits their business model. The capabilities of a modern smartphone equipped with GPS, Wifi and bluetooth are amazing yet unfortunately inaccessible: many features are "locked down" because they do not suit the network operator. Up until now it has been difficult to buy a phone on which you have freedom to install sofware which is not controlled by the network operators - Openmoko changes that!

A list of examples of "closed" behaviour has been started here - [[Problems of typical "closed" phones]]

=== What can we expect in future Neos? ===

Please join one of the [http://lists.openmoko.org mailing lists] to follow and participate in this discussion.

=== Purchasing / Shipping / Versions ===

==== Where can I buy the [[Neo FreeRunner]]? How much?====

http://www.openmoko.com. We sell both directly and through a growing list of distributors.

If you buy directly from the Openmoko webshop you will pay USD $399 for the [[Neo FreeRunner]], USD $99 for the debug board. You can also purchase boxes of 10 FreeRunners at a price of USD $369 each. If you don't have a need for 10 units, you can join an existing or form a new group at [[Group_sales]].

==== On what bands does the Neo FreeRunner operate? Will it work in my area? ====

* The Neo FreeRunner is a tri-band GSM phone. It is available in a 850/1800/1900MHz version for North America and a 900/1800/1900MHz version for the rest of the world.

==== Do I need the debug board? ====

With the Neo FreeRunner and NO debug board you can do:
* Kernel development
* Application development
* U-boot updates(equivalent to PC BIOS). Neo 1973 users should only use a tested image to avoid the possibility of bricking the Neo 1973. Neo FreeRunner users do not have this concern, as a bad u-boot can always be updated using the failsafe u-boot in NOR flash
* Kernel and/or rootfs updates using [[Dfu-util]].

With a debug board you can additionally do:
* Use JTAG to debug u-boot, device drivers, or the kernel
* Use the kernel console
* Neo 1973 users can unbrick their device if they flash a wrong or non-working u-boot image.
* Neo FreeRunner users can update u-boot in NOR flash

In summary, it is rare for a Neo FreeRunner user to require a debug board.

To emphasize, the debug board is '''not''' required in order to develop applications, system software, or even kernel or device drivers. The debug board is '''not''' required in order to gain access to the source code or the development tools.

==== Where do I ask a shipping related question? ====

Visit [http://www.openmoko.com/ openmoko.com]

=== How do I find out what version of hardware I have? ===

:cat /proc/cpuinfo

Search for the line that says "Revision". There will be 4 digits, of the form "0350". The '5' in this example indicates hardware revision 5.

== Neo FreeRunner Known Issues==

=== Software issues, distribution-wise ===

Issues relating to software are in the "known issues" section for each distribution. Navigate there via the distributions page - [[Distributions]].

=== Firmware and hardware issues ===

Issues relating to firmware and hardware are in [[Neo_FreeRunner_Hardware_Issues|Neo FreeRunner Hardware Issues]].

Note that some issues might involve a combination of hardware and software.

=== Selected, commonly-encountered issues ===

Some selected known issues that are commonly encountered and reported on mailing lists are described below.

==== My FreeRunner won't register with my cellphone network. What should I do?====

Please see [[Neo_FreeRunner_Hardware_Issues#Some_SIMs_Don.27t_Work|some SIMs don't work]].

==== SIM compatibility: It looks like my SIM card is not working; how do I run diagnostics? ====

Here is how to check: follow [[Manually_using_GSM]] until you get an OK prompt.

For more detailed documentation, please refer to [[FreeRunner_unable_to_work_with_3G_SIM_cards]] and [[Carriers]].

==== I read somewhere that a GSM firmware update is available to fix this problem====

The GSM firmware update is applicable only to the Neo 1973. Any fixes in the update are already implemented in the GSM firmware in the Neo FreeRunner.

==== Why won't the FreeRunner boot even with the charger connected? ====

See [[Neo_FreeRunner_Hardware_Issues#Can.27t_boot_with_discharged_or_missing_battery|Can't boot with discharged or missing battery]].

==== Flashing (dfu-util) -- dfu-util does not find the phone. ====

In brief, you need to boot the phone into the NAND or NOR u-boot menu before dfu-util will be able to connect. dfu-util uses the USB DFU (Universal Serial Bus Device Firmware Upgrade) protocol, which is only available at the u-boot menu, and '''not''' Ethernet over USB, which is what is available when the phone has booted fully.

Tip: If you're just trying out different distributions, you don't need to flash them with dfu-util; you can try out new distributions by putting them on the microSD card and booting from the card instead. If you'd like to do this instead of flashing, see [[Booting from SD]].

To get the u-boot menu:
# Press and hold the AUX button
# Press the Power button until the phone powers on and displays the boot menu
# Release both buttons
# Press and release AUX to move the lightbar, so that the menu will not time out and boot the phone).

Also see the wiki pages/sections:
* [[Booting the Neo FreeRunner]]
* [[Bootloader#Device Firmware Upgrade]]
* [[Flashing the Neo FreeRunner]]
* [[Dfu-util]]

==== Why do I experience poor audio quality or buzzing noises during calls?====
See [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#Poor_Audio_Quality this issue on the FreeRunner Hardware Issues page]

====Suspend/resume may corrupt SD card's partition table====

See [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#Suspend.2Fresume_corrupts_SD_card.27s_partition_table this issue on the FreeRunner Hardware Issues page]. See ticket [https://docs.openmoko.org/trac/ticket/1802 #1802].

==Hardware and Usage-related Questions==

=== Booting ===

==== How do I boot into U-boot? How do I select NAND or NOR FLASH? ====

See [[Booting_the_Neo_FreeRunner|here]]

=== Battery and Battery Charging===

==== What is the expected battery life? ====
See [[Neo FreeRunner (GTA02) Battery#Notes_about_expected_battery_life]] and more battery information in [[Neo_FreeRunner_(GTA02)_Battery]]

==== How do I enable fast charge mode for anything but the official mains charger? ====
See [[Forcing fast charge mode]].

==== Can the Neo FreeRunner charge when turned off? When suspended? ====

The Neo FreeRunner can '''not''' charge when turned off.

The Neo FreeRunner '''can''' charge when suspended.

==== Can the Neo charge and use devices on a USB hub at the same time? ====

See [[USB_host#Providing_power_to_run_and_charge_the_Neo_while_in_host_mode|here]]

===Wireless Connectivity===

====What kind of wireless connectivity does the FreeRunner have? ====

The FreeRunner has the following connectivity options:
* Tri-band GSM (850/1800/1900 MHz in North America, and 900/1800/1900 MHz, commonly referred to as "European tri-band", for other parts of the world). For a list of compatible service providers, see [[Neo1973 compatible cellphone providers]].
* GPRS Class12/CS4 2.5G (Not EDGE)
* Bluetooth 2.0 EDR
* WiFi: Atheros AR6K in [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]. (No 3G in year 2007 models)

==== GSM/GPRS information ====

The following pages contain very useful information:

* [[Gsmd|GSM Daemon]]

* [[GSM|General GSM page]]

* [[Hardware:AT_Commands|AT commands]]

* [http://freeyourphone.de/portal_v1/viewtopic.php?f=21&t=295#p2956 Useful script for GPRS]

==== How do I get the WLAN (802.11, Wi-Fi, wireless network) working? ====

See [[GTA02 WLAN]]

==== How do I get the GPS working? ====

See [[GTA02 GPS]]

==== It takes a long time (10min+) before the FreeRunner gets the first GPS data/readings ====

See [[GPS Problems]].

==== How do I get Bluetooth working manually? ====

See [[Manually_using_Bluetooth]]

==== How do I use an external Bluetooth keyboard with the FreeRunner ? ====
..TBA..

====Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ====

Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].

=== USB ===

==== How do I connect a USB memory-stick etc? ====

This requires an adapter Mini-B 5-pole => Type A jack or an adapter jack => jack. See [[Host Mode]] for more information.

====Once I have such an adapter, can I use it to connect 2 Neos to each other?====

This question is equivalent to '''How to connect two [Unix/Linux] computers via USB cable and what sort of special cable is needed?''' -> http://www.linuxquestions.org/questions/linux-general-1/connecting-two-computers-with-a-usb-cable-data-cable-411073

It should work if one Neo is set to Host mode and the other one set to Device mode. One Neo could give power to the USB-port it the other Neo's battery is low. ''(I have to verify this)''

==== How do I use an external USB keyboard with the FreeRunner ? ====

Run:
echo "host" > /sys/devices/platform/s3c2410-ohci/usb_mode
echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode

These commands will put the FreeRunner into powered USB host mode. After this, just plug in the keyboard and it'll work. Personally, I've made a .desktop file to switch into and out of host mode.

To switch back to unpowered device mode just run:

echo "device" > /sys/devices/platform/s3c2410-ohci/usb_mode
echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Finally you will need a
USB Type A Female to Female adapter. For more details see
[[Specialized_USB_cables#Attaching_the_Neo_.28acting_as_a_USB_host.29_to_a_USB_device|here]]

=== Display ===

==== Can the phone play VGA video? ====

No, it can do about 20 fps QVGA with software, and something beetween QVGA and VGA playing MPEG-4 using hardware (at resonable fps). Scaling is also done with GPU hardware.

==== How to change the background picture of the root window? ====

{{Note|This probably differs for each distribution? Need to insert, or link to, relevant info for each. --[[User:Eddsouza|eddsouza]] 09:29, 7 September 2008 (UTC)}}

Look at [[Today/2007.2#Adjust_UI_components_at_runtime]].

=== Storage ===

==== What microSDHC-cards are supported? ====

See [[Supported_microSD_cards|here]]

===System-level information===

==== What hardware signals are available?====

To simplify extending the hardware, various signals of interest are brought out via the JTAG connector and can be easily accessed with the debug board:

(TBA: List of signals)

Some additional signals that did not fit on the JTAG connector are brought out to solder pads:

(TBA: List of signals)

==== Is the JTAG interface that comes with GTA01 compatible with GTA02?====

Yes

==== How do I get low-level hardware-related functions, like power up device, dump register? ====

See [[GTA02_sysfs]]

=== Inputs ===

==== How can I type a '/' in the software keyboard? ====

See [[Switching Keyboards]]

==== How do I get a QWERTY layout software keyboard?====

See [[Switching Keyboards]]

=== Miscellaneous ===

====Will Openmoko "Just Work" with Mac OS X? ====

There has been some discussion of this on the mailing list. There is motivation, and there are interested developers.
Not being a Mac OS X user, I don't know enough
to summarize the discussion to answer this question. Can someone please fill in?

For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the Openmoko.

It is expected that (Bluetooth/UB) SyncML based interoperation for
contacts and events can easily be achieved by a patch
to the Apple iSync configuration tables.

There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of
PPC/x86/ARM universal binaries) on Openmoko devices: mySTEP.

==Software==

===General Questions===

====Is it completely free software/open source? ====

Yes. All software that runs on the main CPU and can be updated by the user is available in source.

Firmware in "black box" hardware modules that can not be modified by users is not available in source form. Effectively, these modules are "hardware only".

This allows, for example, that the driver for the GSM module be completely open sourced without violating any FCC rules.

====Can the software do/connect to/... ====

Reviews of the latest "bleeding edge" daily builds of the Openmoko software stack can be seen [[Snapshot_review|here]]

At the moment, the answer to many other questions is "no". The phone is at the moment a small Linux box with a touchscreen, a working dialer and some prototype apps. Most do not function in any way that would be suitable for end-users. If you want to add a feature or application request, then look over the existing [[Applications]] and either add one, or add a feature request to the applications page.

==== Does Openmoko run on any other hardware? ====

You can run it on your [[How_to_run_Openmoko_Apps_on_PC|PC]]. You may be able to run it on other [[Openmoko-supported_hardware | mobile platforms]]

==== Can Java applications from other mobile phones run on the FreeRunner? ====

I think a lot of work must still be done, but [[Java|this]] wiki page has some information

===Distributions===

====What is the stock distribution image that comes on the Neo FreeRunner?====

The 2007.2 distribution - see [[Distributions#2007.2| 2007.2 factory default software image]]

=====Are there any known issues with the factory-installed 2007.2 image on the Neo FreeRunner?=====

Yes, see [[Om_2007.2#Known_Issues|2007.2 Known Issues]]

===== Where can I download and reinstall the factory default image? =====

See [[Flashing_the_Neo_FreeRunner|Flashing the Neo FreeRunner]]

====What alternate distributions are available for the Neo FreeRunner?====

See [[Distributions|Distributions]]

==== How do I find out what image versions are in use on the phone? ====

You can run the commands given below on the phone (in an SSH session from your host PC, or in the Terminal application on the phone itself)
{| border="1" cellspacing="0" cellpadding="5" align="left"
! To find out
! Run
|-
| Kernel version that is currently running
|
uname -a
|-
| The version of the root filesystem that you are currently using
|
cat /etc/version
or
cat /etc/om-version
|-
| The versions of u-boot on the phone (The FreeRunner has one u-boot image in NOR memory, and one in NAND - see [[Booting the Neo FreeRunner]] for more information)
|
grep Bootloader /dev/mtdblock0 (yields the NOR u-boot version)
or
grep Bootloader /dev/mtdblock1 (yields the NAND u-boot version)
|}

 

====Where do I get the latest version of the official Openmoko image, 2008.8 (also known as ASU)?====

See [[Download#Om_2008.8_images_.28ASU.29| download Om 2008.8 images]]

===== Why are the buttons in TangoGPS too large? The zoom out is missing! =====

There is no GTK engine or theme installed with the ASU build. Fortunately, this is easy to fix!

At a terminal:
:<tt># opkg install moko-gtk-theme moko-gtk-engine</tt>
:<tt># ln -s /usr/share/themes/Moko/gtk-2.0/gtkrc /home/root/.gtkrc-2.0</tt>

Now you have pretty colors and widgets, but the font is too big. Edit <tt>/usr/share/themes/Moko/gtk-2.0/gtkrc</tt> in your favorite text editor and add the following line:
:<tt>gtk-font-name = "Sans 4"</tt>

To use the openmoko icon theme, install it with:
:<tt># opkg install openmoko-icon-theme-standard2</tt>

and enable it editing the <tt>/usr/share/themes/Moko/gtk-2.0/gtkrc</tt> adding the line:
:<tt>gtk-icon-theme-name="openmoko-standard"</tt>

You shouldn't even need to restart the device, although you will need to restart any GTK-based programs.

====Can the Neo FreeRunner dual boot? Multiple boot?====

Since the Neo FreeRunner can boot from the micro SD card, you can install and boot from as many distributions as will fit on your card. See [[Boot_from_sd_card|Booting from SD]].

====How do I install Debian on the Neo FreeRunner?====

See [[Debian#Installation|Debian Installation]]

=====Are there any known issues with Debian on the Neo FreeRunner?=====

See [[Debian#Known_Issues|Debian Known Issues]]

=====How do I replace the matchbox window manager with the xfce window manager?=====

Replace the matchbox-wm line in zhone-session with xfwm4 to start the xfce-wm.

Here's my (Fox Mulder) /usr/bin/zhone-session file which works with xfwm and matchbox keyboard popup:

#!/bin/sh

#zhone &
exec startxfce4 &
matchbox-keyboard-toggle &
#exec matchbox-window-manager -use_titlebar yes
exec xfwm4

=== Applications ===

====What software is on the phone?====

At the moment, almost no 'end-user' applications are present and working in a usable state.
It is possible to make and receive calls in some software revisions, this frequently breaks though.

====What software can be installed on the phone?====

Pretty much any that can be cross-compiled for the ARM architecture.

====Will it be possible to use popular VoIP applications such as Skype on the Openmoko platform? ====

Since it has WiFi the FreeRunner should be a good platform for VOIP use.

In either case please check for softphone apps ported to the Openmoko distribution at the [http://projects.openmoko.org/ projects] page. We need to focus efforts on free software. Not convincing non-free software companies to release binaries for our Neos.

====Will it be possible to use popular Instant Messaging applications such as MSN Messenger? ====

Very probably. MSN is closed source and will only run where Microsoft wants you to run it. But there are many Open Source IM clients, many of which have a plugin architecture and so support the use of more than one IM protocol, even simultaneously. One example is [[Pidgin]], formerly called GAIM. GPRS does induce a certain amount of latency but that should not be a problem for simple, text-oriented chat between parties. And the GTA02's WiFi will make it even better.

==== Does it support Flash so can I watch YouTube? ====
You don't really need Flash to watch YouTube videos, for example, if you want to watch www.youtube.com/watch?v=k9QLdK6pFCI just install mplayer and use this command:
mplayer http://ytpocket.com/getflv.php?id=k9QLdK6pFCI
or use this small script with the video URL as the first parametre:
#!/bin/sh
vid=`echo "$1" | sed 's/.*\?.*=$.*$/\1/'`
mplayer http://ytpocket.com/getflv.php?id=$vid

=== Package Management===

==== How do I install and manage software on Openmoko? ====

See [http://handhelds.org/moin/moin.cgi/Ipkg here]

==== What about opkg? ====

See [[Opkg|here]]

==== What is the meaning of the error codes from ipkg? ====

See [[Opkg#Error_Codes|here]]

==== Does opkg support packages autocompletion ? ====

It's possible now, see [http://tropfacile.info/?/Linux/28-Openmoko-Opkg-Autocompletion-With-Packages-Names The opkg autocompletion]

===Development===

====How can I compile programs for the Neo FreeRunner? ====

See [[Toolchain]].

====Is there an emulator available for Openmoko? ====

For a lot of testing and development work you can simply run Openmoko directly on your PC.

=====QEMU=====

QEMU can emulate the Neo 1973 and the Neo FreeRunner. The [[MokoMakefile]] has support for automatically building, flashing, and running [[Openmoko under QEMU|the Neo emulator]].

*Ubuntu users can follow the instructions in [[Automatic_emulation_in_Ubuntu]]

*Users of other Linux distributions can try the following:
:"make qemu” will build qemu-neo1973, download the latest official openmoko images, flash the images into the virtual NAND flash, and run the emulator.

See [[Qemu]] for more advanced information on running Openmoko in Qemu.

=====Xoo=====

[http://projects.o-hand.com/xoo Xoo]. Koen says: "Xoo should be enough for most applications people will develop, since most don't need access to the GSM uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".

Update: Stefan Schmidt has resized the [[Neo1973]] Mock-up and written a small description for xoo. In his words:

It's not really usable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.

http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2

Start with 'xoo --device /path/to/neo1973.xml'

Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].

=====Xephyr=====

Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):
Xephyr -screen 480x640 -nolisten tcp -ac :1 &
export DISPLAY=:1
export LD_LIBRARY_PATH=/usr/local/lib
matchbox-window-manager -display $DISPLAY -use_titlebar no \
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \
-use_cursor yes &
matchbox-panel --geometry=480x44 --end-applets=clock &
openmoko-footer &
openmoko-taskmanager &

====Where can I find some type of tutorial for a 'Hello, world' on Openmoko? ====

This should get you started:
* [[Building_a_hello_world_application]]
* http://www.gtk.org/documentation.html#Tutorials

====Can PalmOS apps applications be ported to run on Openmoko? ====

Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux
is decidedly non-trivial.

PalmOS apps are in general very hard to simply 'port'. Particularly well-designed programs may make it possible.

The ACCESS Linux Platform will include Garnet on Host (GHost), a PalmOS emulator that will support M6800 (68k) and ARM PalmOS applications. This part (GarnetVM and the .prc loader) will however be closed-source and likely under a restrictive license (fact confirmed by ACCESS Co. employees), making it rather unusable. In addition GarnetVM depends on Hiker and other packages.

It is possible that POSE, an emulator that simulates a Palm device on a Linux host could be used to allow 68k based applications to run. This emulator has been around a long time; one expects that it will also run on Openmoko, but this has to be considered a short-term bandaid rather than a long-term solution.

Hopefully emulation will be necessary only for M68000 code (pre-PalmOS 5) while native ARM programs can run natively under Linux, provided a proper set of PalmOS libraries and a .prc executable loader.

==== Does it support Java? ====
It will have eventually, if you help us to get it working. Some good places to keep track of would be [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] and [https://phoneme.dev.java.net/ PhoneME].

Project [[https://wiki.evolvis.org/jalimo/index.php/Jalimo Jalimo]] is a project aiming to provide a Java stack on mobile devices. There is a [https://wiki.evolvis.org/jalimo/index.php/Openmoko port of Jalimo] for Openmoko.
The [[Debian]] distribution supports CacaoVM and JamVM through apt-get. See [[Java]] for more infos.

==== Does it support Ruby? ====

For Ruby 1.9, please refer to http://blog.sparkymat.net/2008/08/10/ruby-19-on-openmoko/

For Ruby 1.8.6, please refer to http://blog.wolfman.com/articles/2008/08/10/ruby-1-8-6-on-openmoko-freerunner

==== Does it support Python? ====

Yes, with some caveats. See [[Python]] for more information.

====How do I dump details about X11 configuration and extensions? ====

Run the command xdpyinfo. Generally, you would do this via an SSH session to the phone, so you may need to first

export DISPLAY=":0.0"

and then run

xdpyinfo

For an example invocation, see [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].

== Distribution Customization ==

{{Note| Suggestion: this should be split off into a separate page, since many of the questions below aren't really overview-level but specialized; a question like "How do I customize a distribution?" could be added to the Software - Distributions part, linking to the new page. --[[User:Eddsouza|eddsouza]] 07:35, 7 September 2008 (UTC)}}

=== Compilation & packaging ===
==== What is the 'overlay' approach to bitbake development? ====
:You can create a local overlay for the bitbake build chain and develop in the overlay as described in [[Application_Development_Crash_Course| Application Development Crash Course]].

==== Which .bb files are related with the Openmoko? ====
==== Are there any configuration files for Openmoko? ====
==== How can I port an application written with autotools to Openmoko? ====
After you source the [[Toolchain|Openmoko toolchain]] variables, the Openmoko processor compiler becomes the default compiler. You can compile any GNU - like project just typing ''./configure --host i686'' and then ''make'' - it will produce libraries and executables as expected. Just these executables will not run on your i686 host - they will run on Openmoko ARM processor. Use scp to upload the executables to your phone.

==== How can I add an application written with autotools to the openmoko tree? ====

==== How can I make changes in the openmoko applications? ====
==== How can I submit my changes? ====
==== Can I use the mokomakefile in the development process? How? ====

:Yes, [[MokoMakefile]] can be used in the development process. See [[MokoMakefile#Developing_with_MokoMakefile| Developing with MokoMakefile]].

==== What's the way to include/exclude a newly added package to/from the final rootfs? ====
==== Where do the final ipk & binary files reside? ====
:ipk files are in
./build/tmp/deploy/glibc/ipk/
:binary images are in
./build/tmp/deploy/glibc/images/fic-gta01/

==== How can I add an application to the applications list? ====
==== How can I assign an image to my new application to be seen in the applications list? ====
The Openmoko project tree contains the folder 'data' where you can put any 128*128 icon. You need to mention the icon in two places in this folder:
* Makefile.am must contain the line dist_appicon_DATA = <icon_name>.png
* The <application_name>.desktop file that must be in this folder should contain the Icon=<icon_name> (without file type).

==Misc==

===On the lists on lists.openmoko.org, should replies be added above or below the original text? ===

Please reply UNDER post.

===How can I find out if a question or topic has already been discussed on the mailing lists? ===

By searching the mailing list archives. For example, using Google searches:

site:openmoko.org text

For example, to search for accelerometer:

site:openmoko.org accelerometer

If you only want to read the "official" mails from FIC people or from Openmoko people:

site:openmoko.org text "at fic.com.tw"
site:openmoko.org text "at openmoko.org"

For example to search for "release date" from FIC people:

site:openmoko.org "release date" "at fic.com.tw"

Alternatively you can use the [http://www.google.com/coop/cse?cx=018430699993342716089%3Aszsaurhronw custom Openmoko search engine] that is using [http://www.google.com/coop/ Google Co-op].

===how many dead pixels may the LCM have before calling it defect? ===

The answer for the display used in GTA01 and GTA02 is '2'

=== how many visits does this wiki have? ===
See this [[Wiki_statistic_numbers|wiki's statistics]] page.

=Historical=
The Neo1973 was last available in Febuary 2008.

==Neo1973 Hardware==

===What are the hardware specifications of Neo 1973 ? ===

See page [[Neo1973_Hardware]] and category [[:Category:Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]]

===How do I input text? ===

Use provided keyboard app.

Use Bluetooth keyboard.

For more methods and ideas see [[Wishlist:Text_Input]].

===Can I record calls and/or play audio files in calls? ===

Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing an [[Answering Machine]] is possible. Also using text->speech should be possible or modifying outgoing voice. Currently there is no software bundled in phone to do this.
There are only 2 A/D inputs and three D/A outputs (one dedicated to the earpiece). This means that stereo audio playback cannot happen at the same time as the [[Answering Machine]] functionality, amongst other things. See the audio page. [[Neo1973_Audio_Subsystem|Neo1973 Audio Subsystem]]

===What is the battery life? ===

There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].

=== USB ===

====What can I do with the USB port on the Neo? ====
Charge the phone, communicate with it over USB-serial, or USB-networking.

Plug external devices, such as wifi, cameras, or mass-storage devices.

====What can't I do with the USB? ====

The only limitation on current hardware seems to be no usb 2.0 support, which means slower communication with 2.0 devices.

====Why is only USB 1.1 provided? ====

The processor has USB 1.1 built in. One with USB2 built in would have been more expensive, and might not be open.

The FreeRunner has the same processor as the Neo1973.

====What are the details of the USB port on the Neo? How does it compare to USB On-The-Go? ====

The Neo will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just
an AB socket, but also electrical and software components which cannot be provide by the S3C2410.

You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).

[[Category:Application Developer]]
[[Category:Basic End User]]
[[Category:FAQ]]

FreeRunner: Selected Blogs and Articles

2008-10-08T17:17:03Z

Michaelshiloh: /* September 2008 */

{{Neo FreeRunner Menu}}

{|align=right
|__TOC__
|}

This page contains references to personal blog entries and reflections of the mind about FreeRunner. Please see [[Press_Coverage]] for more official pieces of information.

Newest on top.

== English ==

== October 2008 ===
* [http://www.teaparty.net/technotes/openmoko-2.html More fun with our Openmoko phones]

=== September 2008 ===
* [http://nop0.blogspot.com/2008/09/revive-openmoko-neo-freerunner-with-usb.html Revive the Freerunner with USB power]
* [http://nop0.blogspot.com/2008/09/having-multiple-distributions-on.html Multiple distributions on SD card] (work in progress)

=== August 2008 ===
* Andrénalin heavy metal chainsaw!!! [http://andre.web-yard.de/blog/2008/08/03/neo-freerunner-rocks-hard-rides-free/ http://andre.web-yard.de/blog/2008/08/03/neo-freerunner-rocks-hard-rides-free/]
* Monochrome Mentality [http://monochromementality.com/index.php/blog/show/FSO-Milestone-II-Phot-Safari-and--rant.html FSO Milestone II Photo Safari and rant]

=== July 2008 ===
* technocrat.net (Charles E. Hill) [http://technocrat.net/d/2008/7/27/46753 Openmoko Neo FreeRunner - Part 1]
* Rabble.ca (Wayne MacPhail) [http://www.rabble.ca/news_full_story.shtml?x=73765 Introducing the anti-iPhone]
* Canadia Blog [http://bieberphoto.com/canadia/index.php/2008/07/openmoko-neo-freerunner-review/ Neo FreeRunner Review]
* Holden Karau [http://blog.holdenkarau.com/2008/07/unboxing-openmokofreerunner-including.html Unboxing the Openmoko/FreeRunner including the spares kit, debug board]
* Dave Fayram [http://www.vimeo.com/1366042 Openmoko Train Wreck] (video review)
* Dave Fayram [http://www.vimeo.com/1366923 More Openmoko Train Wrecking (Now with Qt!)] (video review)
* Wired's Gadget Lab Podcast: [http://blog.wired.com/gadgets/2008/07/gadget-lab-po-1.html Summary] and [http://audio.sonibyte.com/audio/7394.mp3 mp3] (discussion starts at 5:50)
* jThinks: [http://jthinks.com/index.php/freerunner-at-last/ FreeRunner, at last]
* Holden's Blog: [http://blog.holdenkarau.com/2008/07/unboxing-openmokofreerunner-including.html Unboxing the Openmoko/FreeRunner including the spares kit, debug board]
* Wolfmans Howlings: [http://blog.wolfman.com/articles/2008/07/11/openmoko-freerunner-first-impressions Openmoko FreeRunner first impressions]
* Free Software Foundation (John Sullivan): [http://www.fsf.org/blogs/community/5-reasons-to-avoid-iphone-3g 5 reasons to avoid iPhone 3G]
* Joseph Reeves: [http://blogs.thehumanjourney.net/finds/entry/20080710 FreeRunner retail unboxing]
* Ars Technica: [http://arstechnica.com/reviews/os/open-moko-software.ars Ars Technica First Look at Openmoko]
* Juan Lucas Domínguez Rubio: [http://gvsigmobileonopenmoko.wordpress.com/2008/07/02/first-experience-with-openmoko/ First experience with Openmoko]
* Philipp Kern: [http://www.philkern.de/weblog/en/neo_freerunner.html Neo FreeRunner: First impressions]

=== June 2008 ===
* Andrzej Zaborowski: [http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket/ Accelerating in my pocket]

=== May 2008 ===
* Kevin Dean: [http://www.monochromementality.com/index.php/blog/show/Day-One-Openmoko-FreeRunner.html Day One: Openmoko FreeRunner]

==== Earlier ====
* Michael Shiloh: [http://gettingstartedopenmoko.wordpress.com/ Getting Started with Openmoko] (many blog entries in this dedicated blog)

== French (français) ==
* blog, wiki and forum in french about Openmoko: http://www.openmoko-fr.org
=== July 2008 ===
* Xavier Cremaschi : [http://wiki.troulite.fr/index.php/NeoFreerunner FreeRunner French Companion Wiki] This page is a (quite big) summary of my understanding and experimentations : what are the different software stacks, how you can install them (flashing or dual boot), how you can configure them. Note that everything comes from this wiki or mailing lists, I don't claim paternity for anything except translation and feedback.

== Italian (italiano) ==

=== August 2008 ===
* Lo schiaffo : [http://www.loschiaffo.org/telefono-open-source/ Opensource telephone]
* TuguLab : [http://blog.tugulab.org/2008/08/13/come-configurare-openmoko-sul-neofreerunner-e-utilizzarlo/ Come configurare Openmoko sul NeoFreeRunner e utilizzarlo!] by jollyr0ger

[[Category:Community]]