Openmoko - User contributions [en]

NeoTool

2010-11-16T14:29:30Z

Antisol: v1.3 released, some comments

NeoTool is a bash script for your desktop system to provide a friendly GUI frontend to some common management tasks, like for example flashing Openmoko smartphones. It is aimed at being very intuitive and easy to use, and flexible enough to make it useful in a wide variety of circumstances.

== Features ==

The main features of NeoTool are:
* Ability to [[Flashing the Neo Freerunner|flash]] your Neo via a GUI for the following image types:
**rootfs
**kernel
**[[Uboot]]/[[Qi]] bootloader
**splash screen
* Ability to flash multiple images at once (for example, flash rootfs and the kernel at the same time)
* Ability to backup your Neo via a GUI
* Ability to backup Multiple images at once
* rootfs can be backed up to either a flashable image or a tar archive
* most / all configuration can be done via the GUI

== Screenshots ==
[[Image:NeoTool.png|NeoTool opening screen]]

== Download / Releases ==

The most recent version of NeoTool is available for download at http://users.on.net/~antisol/neotool

When a new version is released it will be announced on the community mailing list, and on this page.

[https://bugs.launchpad.net/ubuntu/+bug/288747 Here] is the packaging request of NeoTool for '''Ubuntu'''; [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504131 here] for '''Debian''' (which will probably not succeed).

(the author currently has no intention of taking action on these - if you want it packaged for your distro, you should do something about it rather than waiting)

=== openSUSE ===
* [http://software.opensuse.org/ymp/home:worldcitizen/SLE_10/NeoTool.ymp 1-Click Install for SLE 10]
* [http://software.opensuse.org/ymp/home:worldcitizen/SLE_11/NeoTool.ymp 1-Click Install for SLE 11]
* [http://software.opensuse.org/ymp/home:worldcitizen/openSUSE_10.3/NeoTool.ymp 1-Click Install for openSuSE 10.3]
* [http://software.opensuse.org/ymp/home:worldcitizen/openSUSE_11.0/NeoTool.ymp 1-Click Install for openSuSE 11.0]
* [http://software.opensuse.org/ymp/home:worldcitizen/openSUSE_11.1/NeoTool.ymp 1-Click Install for openSuSE 11.1]
* [http://software.opensuse.org/ymp/home:worldcitizen/openSUSE_11.2/NeoTool.ymp 1-Click Install for openSuSE 11.2]
* [http://software.opensuse.org/ymp/home:worldcitizen/openSUSE_Factory/NeoTool.ymp 1-Click Install for openSuSE Factory]

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

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

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

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

== Requirements ==

You will have to install [[dfu-util]] in order to be able to use NeoTool.

Other prerequisites for NeoTool should be installed on most modern linux systems by default:
* bash
* zenity
* which
* awk

=== Optional ===

* pipe viewer (pv), shows display while backing up rootfs

* to backup rootfs, you need to have a [[USB_Networking|USB networking]] configured and working

* mkfs-jffs2 needs to be installed on your neo to backup rootfs to a flashable image (type 'opkg install mkfs-jffs2' in ssh)

* While not a requirement, backing up rootfs is much less painful if you set up an authorized_keys entry for your host on your Neo. To do this, run 'ssh-keygen' (preferrably as root) on your host, and then copy the contents of ~/.ssh/id_rsa.pub on your host into /home/root/.ssh/authorized_keys on your freerunner

<pre>
user@host# su

root@host# ssh-keygen

root@host# scp ~/.ssh/id_rsa.pub root@<Neo IP Address>:/home/root

root@host# ssh root@<Neo IP Address>
root@om-gta02:~# cat id_rsa.pub >> /home/root/.ssh/authorized_keys

</pre>

This will prevent you from having to enter the password for your Neo when you use ssh and scp.

If you don't do this, you will need to enter your password repeatedly in order to backup rootfs.

== Usage ==

NeoTool should usually be run as root, although this is not required if you only want to backup rootfs and/or the kernel via scp.

<pre>sudo ./neotool</pre>

You will initially be presented with the main menu. Most of the functions should be relatively self-explanatory

(thorough documentation on usage goes here)

== Revision History ==

See [http://lists.openmoko.org/pipermail/community/2008-September/029731.html this thread] and [http://lists.openmoko.org/pipermail/community/2008-September/030257.html that update] for discussions on the community list.

=== 09-Sep-2008 ===

- ability to flash more than one image at once - the 'what do you wanna
flash' now has checkboxes instead of radio buttons, and all your
selections are flashed one after the other. (which i find very handy,
stops the FR powering down while you're typing the next dfu-util
command, or locating the next image - works great for flashing a new
distro & kernel). if an error occurs, subsequent files will not be flashed.

- more confirmation / idiot-proofing - it now tells you what you're
doing much more clearly (i.e: "about to flash Kernel with /foo/bar.bin,
rootfs with /foo/bar.jffs". allows you to confirm that you chose the
right images). also the 'choose file' dialogs tell you what you're
browsing for

- ability for users to press 'cancel' at the various dialogs and exit
gracefully.

- checks that dfu-util exists and is executable. I moved my dfu-util to
/usr/local/bin, so it looks there first, but it will also check the
current directory and prompt if it can't find it

- I wasn't a fan of patching dfu-util, and the pulsating zenity progress
dialog drags my (prehistoric) PC to a crawl, so I disabled the progress
bar and use the text output of dfu-util instead.

=== 12-Sep-2008 (v1.0) ===

- Utility now has the ability to flash the splash image as per request

- Utility can now also backup your device to flashable rootfs / kernel images (david might like this for building FDOM images)

- Configurification is loaded on startup and saved in /etc/frutil (you can only modify settings if you run it as root)

- more idiot proofing - uses 'which' to find dfu-util, checks to ensure it's being run as root, checks that zenity is installed on the host, checks that you have mkfs.jffs2 installed before backing up, checks that you have pv installed and acts accordingly (by either using it or not during the backup [this is not properly tested because I don't have pv, please report]), and possibly other stuff I've forgotten about.

- new name (frutil) to reflect the new abilities

=== 17-Sep-2008 (v1.1) ===

- Added ChangeLog

- Added ability to handle multiple DFU-capable devices

- Changed references to 'freerunner' to 'neo'

- name changed to NeoTool (despite implied connection with Keanu Reeves' crotch)

- Added 'Reset to defaults' option

- Added warning that flashing uboot on neo1973 may result in a paperweight

- several small bugfixes

- made backup functionality much more versatile:

- made backup filenames configurable

- Added ability to choose what to backup

- Added rootfs backup type option (jffs2 or tar)

- Added kernel backup method option (scp or dfu)

- Added ability to backup uboot and splash

=== 31-Oct-2008 (v1.2) ===
- Changed information at pre-flash prompt to include instructions for how to get to the NOR menu. eliminated any mention of NAND, as everything can be flashed from NOR.

- bugfix - when user selects a filename under 'customize backup filenames' and then presses cancel, the selected filename was set to nothing.

- NeoTool now checks that the path of backup files exist, and attempts to create it if it doesn't. This allows you to organise your backups in a folder hierarchy, i.e set the backup filename to: /data/openmoko/backups/{date}/{image}_backup and the {date} directory will be created by NeoTool, assuming /data/openmoko/backups exists and you have permission.

=== 17-Nov-2010 (v1.3) ===

- Added (broken) ubifs support per chris' patch

== Support ==

Suggestions? comments? feedback? problems?

<strike>NeoTool is perfect in every respect - if it breaks it's because you did something wrong.</strike>
* Email the Community list,
* or (if you have a patch), email antisol (at) internode (dot) on (dot) net.

[[Category:Flashing Openmoko]]
[[Category:Host OSes]]

Talk:NeoTool

2010-11-16T14:20:44Z

Antisol: reply to chris

Since I installed SHR-U from Oct. 2010 recently I thougt about ubifs support for neotool... What do you think?

Here's a patch against version 1.2 of neotool:

<code><pre>
--- neotool.sh.cpx 2010-06-09 19:53:40.000000000 +0200
+++ neotool.sh 2010-10-22 09:45:57.000000000 +0200
@@ -493,7 +493,34 @@
echo Cleanup...
ssh root@$FRIP "umount /var/tmp/root; rmdir /var/tmp/root"
;;
+ "ubifs")
+
+ ip_test
+ if [ $? != 0 ]; then
+ return
+ fi
+
+ echo ' - Checking device for mkfs-ubifs...'
+ if [ -z "`ssh root@$FRIP 'opkg status mkfs-ubifs'`" ]; then
+ zenity --error --text 'prerequisite mkfs-ubifs is not installed on the device! \n\n do "opkg install mkfs-ubifs" and try again.'
+ return
+ fi

+ echo " - Mounting flash at /var/tmp/root..."
+ ssh root@$FRIP "mkdir /var/tmp/root; mount -t ubifs ubi0:om-gta02-rootfs /var/tmp/root"
+
+ echo ' - Performing backup... (this will take a while)'
+ if [ -z "`which pv 2>/dev/null`" ]; then
+ #pv is not installed, so don't use it...
+ ssh root@$FRIP "mkfs.ubifs -r /var/tmp/root -o- -e 128KiB -m 512 -c 100 -x lzo" > $FSIMG
+ else
+ # FIXME: the mkfs.ubifs wants to have '-o <file>' option, how to pipe the data stream?
+ ssh root@$FRIP "mkfs.ubifs -r /var/tmp/root -o- -e 128KiB -m 512 -c 100 -x lzo" | pv -W > $FSIMG
+ fi
+
+ echo Cleanup...
+ ssh root@$FRIP "umount /var/tmp/root; rmdir /var/tmp/root"
+ ;;
"tar")
echo ' - Performing backup... (this will take a while)'
if [ -z "`which pv 2>/dev/null`" ]; then
@@ -637,7 +664,7 @@

function root_backup_type {
old_rootfs_type=$rootfs_type
- rootfs_type=$(zenity --list --text "Choose rootfs backup type:\n\nIf you have modified your rootsf filename, this will reset it to the default." --column "Format" --column "Description" jffs2 "Flashable JFFS2 Image" "tar" "For SD card install")
+ rootfs_type=$(zenity --list --text "Choose rootfs backup type:\n\nIf you have modified your rootsf filename, this will reset it to the default." --column "Format" --column "Description" jffs2 "Flashable JFFS2 Image" ubifs "Flashable ubifs Image" "tar" "For SD card install")
if [ -z "$rootfs_type" ]; then
rootfs_type=$old_rootfs_type
fi
</pre></code>

It does not work at the moment because the mkfs.ubifs command wants to have an output option '-o <filename>'. How to make it stream the output to stdout so we can pipe it?

To flash ubifs files nothing has to be changed, I've successfully done this using neotool v1.2.

Another feature request: Automatic installation of mkfs-jffs2/mkfs-ubifs if not found on openmoko device.

--ChrisPZV 11:45, 22 October 2010 (UTC)

Hi Chris,

Ooh! a patch! Thanks!

Sorry I haven't had a chance to get back to you, I've been meaning to check this out, but I haven't used my freerunner in nearly a year and haven't gotten around to trying out your patch. it looks OK though.

To make it send output to stdout for streaming across our ssh connection, you could try using something like '-o /dev/stdout', or you could try using a FIFO buffer using the 'mkfifo' command.

The reality of the situation is that I'm not particularly likely to add anything to NeoTool - at one time I had grand plans to rewrite it in something other than bash, but since I'm not using my FreeRunner anymore I don't see myself making any further improvements unless I have a resurgence of interest in this (terribly horribly awfully awful) device.

Having said that, I've applied your patch to the version I'm hosting (which is the 'official' download link on the wiki page - http://users.on.net/~antisol/neotool) and labelled it v1.3. If you want to play around with getting the ubifs stuff working properly and send me another patch, I'll be happy to apply it!

If you want to talk to me about neotool, probably your best option is to email me (see the bottom of the main neotool wiki page) :)

Cheers,
-Dale

Jokes

2009-05-12T10:38:27Z

Antisol:

= Jokes in English =

'''Q: Why did OM cross the road?'''

A: To get to another toolkit :)

'''Q: How many OM devs does it take to change a lightbulb?'''

A: Well first we need to abandon the old lightbulb holder because at a later date we may not be able to plug a floodlight in, bring in a new lightbulb holder and adapt it to multiple floodlights, meanwhile the engineering team has realized that this will only run green floodlights and has started rewiring the whole house.. :) The burnt out lightbulb is due to be fixed at a later date :)

'''Q: What is the difference between a professional photographer and OM user?'''

A: The OM user has to flash more often :)

'''Q: Why did the OM newbie log onto #openmoko?'''

A: Because they had not read:
*# the wiki, and
*# the topic
As then they would know you slide your finder up on the keyboard to get the numbers to enter your sim pin.

'''Q: What's the difference between an iphone and a freerunner?'''

A: One works but takes away your freedom, the other is free but needs your work

Knock, Knock
Who's There?
A Neo User
A Neo User

'''Q: What did the Neo say to the insomniac?'''

A: At least when you go to sleep you know you'll wake up!

'''Ancient chinese proverb:''' "Neo owner is man carrying wall charger"

'''Q: What's the difference between a brick and a freerunner?'''

A: The brick is heavier... slightly.

A: The brick comes in different colors.

A: You can't de-brick the brick.

A: A brick doesn't have to be recharged every twelve hours

A: A brick will reliably perform it's intended function out of the box, no configuration required.

A: You don't have to constantly re-flash / update the software on a brick

A: The brick will not buzz

A: The brick won't stop working after a day or two

A: The brick is waterproof

A: Bricks are cheap, reliable, and widely available.

A: A brick isn't designed to make phone calls.

'''Q: And what's the similarity?'''

A: The probability they ever reliably will.

'''OM2008.9 and FSO walk into a bar.'''

"How are you? How are you?" asks FSO.

"Buzzzzzzz" says OM2008.9

'''Q: How to switch off this phone?'''

A: You have to write program :)


;Q What if somebody important calls?:A Err..

;A. Because it messes up with the normal order in which people read things.:Q. Why is top-posting prohibited on our mailing lists?

;Q What is your new year resolution?:A 640x480.

'''E-mail quotes:'''

Hello,

Yesterday I accidentally put my OM phone near LCD TV (Samsung).

SW on OM is QT Extended and when I press power button (to wake up mobile) TV immediately turn off.

I tried again and TV changed channel. So, on my phone this behavioure is repeatable.

Is it normal behavioure?

Thanks in advance

Mile

'''IRC quotes:'''

[16:03] <jadams_> does 2008.8 support the neo yet?

<AntonTakk> i don't want another phone that would just need a bubble on top to look like an apple mouse
<playya_> AntonTakk, a apple mouse has less buttons

<Rampentpancake> can i run openmoko as a live cd?

<Rampentpancake> like is it a bootable linux distribution?

'''Motivator'''
[http://www.om.vptt.ch/site/wp-content/uploads/2008/11/poster81947927.jpg]

'''Accessories'''
* [http://lists.openmoko.org/pipermail/support/attachments/20081201/5bc502e1/attachment-0001.jpg Freerunner anti-theft-protection]

'''Fantasy release announcements:'''
* New distribution: [http://scap.linuxtogo.org/files/2c3159f3e1a2622fd56fe29d2f222d9c.png OpenmokoMe Millenium Edition] !
* New hardware: [http://notnews.today.com/2008/09/22/free-software-foundation-announces-gnuphone/ the GnuPhone].

= Openmoko Jokes in Other Languages =

As a special page, I'd like all languages to be on the same page.

== Finnish ==

[http://www.1songlyrics.com/k/kummeli/jumankauta-juu-n--s-p-iv--.html Kummeli-assosiaatio] 
”GTA nolla kakkonen on, luureista ehkä voittamaton; 
pientä laittoo se vaatii vaan, sitten baanalle brassailemaan 
... 
Jumankauta juu nääs päivää, ei ole huolen häivää; 
toolkitit kun tunnelmaa tuo, bassfix ja buzzfix soundit luo” 

(saa jatkaa/kehitellä)

== ... ==

[[category:Community]]

User:Drdeath

2009-05-08T19:45:11Z

Antisol: New page: Hey, AntiSol Here. I just wanted to congratulate you on your BRILLIANT expansion of my "brick" Joke. I Laughed very hard!

Hey, AntiSol Here. I just wanted to congratulate you on your BRILLIANT expansion of my "brick" Joke. I Laughed very hard!

Import Vcf Contacts

2008-12-08T10:37:55Z

Antisol: added note for later versions of QT Extended

To copy your contacts from other devices or desktop systems, you can use the VCF VCard format. This page explains how to export your contacts from various systems and how to import the resulting file on on Openmoko smartphone.

== Exporting old contacts to VCard format ==

To use the import tools you need your Contacts in VCF format.

# On nokia phones use the Nokia phone manager {{Citation needed}}
# On windows mobile phones you could use active sync to sync with Outlook and then use a Outlook VCF export plugin below
# On LG phones the backup function to memory card creates one file with multiple VCards

=== Evolution ===

Evolution can export only to VCF version 3.0, so you need to post-process the exported file.

* Select Contacts, then File > Save Address Book as VCard and save to your desired destination.
* Use the following command to remove evolution's proprietary fields and convert the file to an encoding Om2008.8 will understand (replace old.vcf to the filename you chose for export of your addressbook in evolution):

<pre>
sed -r -e 's/"X-EVOLUTION-CALLBACK"/MSG/g' \
-e 's/;TYPE=([^,]+),[^;]+([;:])/;TYPE=\1\2/g' \
-e 's/;X-EVOLUTION-UI-SLOT=[0-9]//g' old.vcf \
| iconv -t ISO-8859-1 > new.vcf
</pre>

Note that if you run into errors like

<pre>found unknown attribute in vobject, TEL </pre>

then there are probably still occurrences of X-EVOLUTION- fields that need to be removed.
Also note that the above script converts your addressbook file to ISO-8859-1 (see last line), as its native UTF-8 apparently isn't recognized by Om2008.8. If necessary, eplace ISO-8859-1 by a encoding that better suits your needs.

=== Thunderbird ===

To export VCF from Thunderbird:

* Get "MoreFunctionsForAddressBook" from http://nic-nac-project.de/~kaosmos/morecols-en.html
* Install the downloaded *.xpi file in Thunderbird
* Open address book
* Select address book to export (not a contact or set of contacts!)
* Right click and export to Vcf format (or use the Tools menu, Actions for AddressBooks) (If gray, you did not select an addressbook.)
* Select destination folder

=== Outlook / ActiveSync to VCF ===

To export VCF from Outlook, open Outlook, then open the VB editor by pressing ALT-F11, Insert a module, and paste in the following. Change "Z:\Openmoko\contacts" to wherever you want your vcf files saved (should be an existing, empty directory), and press F5 to run it.

'''Code:'''

<pre>

Sub ExportContactsToVCF()

'Cheap and nasty way to export All Contacts to VCF files.
'By Dale Maggee, antisol (at) earthling (dot) net

Dim CN As ContactItem
Dim NS As NameSpace
Dim Fld As MAPIFolder

Set NS = Application.GetNamespace("MAPI")
Set Fld = NS.GetDefaultFolder(olFolderContacts)

For Each CN In Fld.Items
Debug.Print CN.FullName
CN.SaveAs "z:\Openmoko\contacts\" & CN.FullName & ".vcf", olVCard
Next CN

MsgBox "Done!"

End Sub
</pre>

voila! you now have multiple VCF files in whatever directory you chose, suitable to be imported by the Om 2007.2 python script below. (However not suitable for the addressbook tool of Om 2008.8.)

=== Mac OS X Addressbook ===

To export VCF:

# Set the vCard Format to 2.1 in the config dialog
# Select all contacts and say "export vcard"
# Despite having selected the charset to be utf-8 you may need to do:

<code>
iconv -f latin1 -t utf-8 vCards.vcf | sed 's/CHARSET=LATIN1://g' > all.vcf
</code>

== Import (and export?) on Om 2008.8 and Qtopia ==

The Qtopia addressbook application supports import of VCF files out of the box. However, since there is a bug, if there are non-ASCII characters in your contacts you cannot use the version 3 format, otherwise you get multibyte UTF-8 characters mangled. Use the version 2.1 to get the encoding stated explicitly and thus characters imported correctly. But because there is another bug, when using version 2.1 vCards, the addressbook eats up all memory (and potentionally crashes the system) on ''some'' vCards with multiline entries.

If you're connected via SSH, run the following command first:

<pre>
export DISPLAY=:0
</pre>

''(So that the addressbook will show on your phone. If you do not that and try to run addressbook locally on your computer display, you won't be able to use the application since the needed buttons will not show.)''

Then you can simply run:

<pre>
addressbook path_to_vCards_file_to_import.vcf
</pre>

Make sure your contact list has extension .vcf.

You will be asked if you want to import the contacts form addressbook.vcf (the contact name will be taken from the "N:" vCard field).

To import a huge number of contacts, single .vcf files can be merged together using:

<pre>
cat *.vcf > all.tmp
mv all.tmp all.vcf
</pre>

then import all.vcf

''Tip: If you want to prevent crashing your system if the memory leak occurs, set some limit on memory available to use, so that only the addressbook application dies after reaching the limit. I.e. prior to running the import, do something like:''

<pre>
ulimit -v 50000
</pre>

If the above does not work, here are the original import guidelines:

To import your address book from VCard format (ASU/<=Qtopia 4.3.2-080808 snapshot):

'''''Note: On later versions of QT Extended, replace /opt/Qtopia with /opt/Trolltech/Qtopia in the instructions below'''''

<pre>
export LD_LIBRARY_PATH=/opt/Qtopia/lib
/opt/Qtopia/bin/addressbook /home/root/addressbook.vcf
</pre>

To import your address book from VCard format (>=Qtopia 4.3.2 stable):

<pre>
export LD_LIBRARY_PATH=/opt/Nokia/Qtopia/lib
/opt/Nokia/Qtopia/bin/addressbook /home/root/addressbook.vcf
</pre>

To import your address book from VCard format (>=QTextended 4.4.1 stable):

<pre>
export LD_LIBRARY_PATH=/opt/Trolltech/Qtopia/lib
/opt/Trolltech/Qtopia/bin/addressbook /home/root/addressbook.vcf
</pre>

===Mass Delete===

The Qtopia addressbook doesn't seem to have a delete all function, which means that botching a vcf import is a painful process to undo through the phone GUI.

If you want to delete your entire addressbook or do other mass edits then you'll need access to a command line or GUI SQLite client (SQLite Database Browser seems to be a good, free one, though the SQLite command line client should be fine).

====Qtopia====

* Shutdown Qtopia
* Use the client you have chosen to open up /home/root/Applications/qtopia_sqlite.db.
* Important tables: contacts, contactphonenumbers, contactaddresses
* Restart Qtopia when you're done and you should have a reset addressbook.

====On Om 2008.8====

* Install sqlite3
* Open the database
* Delete all data from the contacts tables '''This will erase all your contacts and contact categories.'''

<pre>
opkg install sqlite3
sqlite3 /home/root/Applications/Qtopia/qtopia_db.sqlite

delete from contactcategories;
delete from contactaddresses;
delete from contactcustom;
delete from contactphonenumbers;
delete from contacts;
.quit
</pre>

The first two are shell commands, the ''delete'' commands must by typed in the '''sqlite>''' prompt which appears after the sqlite3 command. Prompt is not included here to allow copy/paste.

==== Exporting ====
Make sure you have sqlite3 client installed
<pre>opkg install sqlite3</pre>

Now we can play with the PIM database file located at
<pre>/home/root/Applications/Qtopia/qtopia_db.sqlite</pre>

Exporting to VCF can be done via qtmail's 'send all' function (which only supports sms, bluetooth). Exporting all the contacts to a VCF file has yet to be documented. Here is [http://lists.openmoko.org/pipermail/community/2008-October/033588.html Vasco Névoa's contribution] to export to a tab-delimited file:
<pre>
sqlite3 ~/Applications/Qtopia/qtopia_db.sqlite \
'Select distinct nickname, title, firstname, middlename, lastname, suffix, \
profession, b_webpage, company, office, department, jobtitle, default_email, \
phone_number, h_webpage, spouse, gender, birthday, anniversary from contacts, \
contactphonenumbers where contacts.recid=contactphonenumbers.recid;'\
| sed 's/|/\t/g' > addressbook.txt
</pre>

Vasco says:
<pre>
Each contact that has more than one phone number will appear multiple
times because I haven't yet come up with a clean way to show the "join"
between the "contacts" and "contactphonenumbers" tables, so for now it
just duplicates the whole line, with the only difference being the phone
number. Also, this still does not take care of contacts with multiple email
addresses, so it is just a work in progress (but better than nothing if you're
in a jam).

Anyone versed in SQL will be able to hack this into a full VCF file
generator... or you can just go the Python or Perl way (but I prefer to use
the nice tools already in place - SQL is pretty powerful if you know how).
</pre>

You can export all your contact's phone numbers on the same line with this SQL query. This works because the contactphonenumbers table has limited phone_type values. We can't do the same left outer join query for the emails because there can be an unlimited count of emails per contacts.
<pre>
Select distinct nickname, title, firstname, middlename, lastname, suffix,
profession, b_webpage, company, office, department, jobtitle, default_email,
cpn1.phone_number as Home_Phone,
cpn2.phone_number as Home_Mobile,
cpn3.phone_number as Home_VOIP,
cpn4.phone_number as Home_Fax,
cpn5.phone_number as Business_Phone,
cpn6.phone_number as Business_Mobile,
cpn7.phone_number as Business_VOIP,
cpn8.phone_number as Business_Fax,
cpn9.phone_number as Business_Pager,
h_webpage, spouse, gender, birthday, anniversary from contacts

left outer join contactphonenumbers as cpn1
on contacts.recid=cpn1.recid and cpn1.phone_type=1

left outer join contactphonenumbers as cpn2
on contacts.recid=cpn2.recid and cpn2.phone_type=257

left outer join contactphonenumbers as cpn3
on contacts.recid=cpn3.recid and cpn3.phone_type=769

left outer join contactphonenumbers as cpn4
on contacts.recid=cpn4.recid and cpn4.phone_type=513

left outer join contactphonenumbers as cpn5
on contacts.recid=cpn5.recid and cpn5.phone_type=2

left outer join contactphonenumbers as cpn6
on contacts.recid=cpn6.recid and cpn6.phone_type=258

left outer join contactphonenumbers as cpn7
on contacts.recid=cpn7.recid and cpn7.phone_type=770

left outer join contactphonenumbers as cpn8
on contacts.recid=cpn8.recid and cpn8.phone_type=514

left outer join contactphonenumbers as cpn9
on contacts.recid=cpn9.recid and cpn9.phone_type=1026;
</pre>

I needed the vcf file for other purposes and found a script [http://sourceforge.net/projects/tsv2vcf/] on SF.net to convert a tab seperated value to a vcf file.
So I used this ugly thing:

<pre>

sqlite3 ~/Applications/Qtopia/qtopia_db.sqlite $1 'Select distinct firstname, lastname, middlename,
nickname, default_email,title,
cpn5.phone_number as Business_Phone,
cpn1.phone_number as Home_Phone,
cpn8.phone_number as Business_Fax,
cpn9.phone_number as Business_Pager,
cpn2.phone_number as Home_Mobile from contacts
left outer join contactphonenumbers as cpn1
on contacts.recid=cpn1.recid and cpn1.phone_type=1
left outer join contactphonenumbers as cpn2
on contacts.recid=cpn2.recid and cpn2.phone_type=257
left outer join contactphonenumbers as cpn3
on contacts.recid=cpn3.recid and cpn3.phone_type=769
left outer join contactphonenumbers as cpn4
on contacts.recid=cpn4.recid and cpn4.phone_type=513
left outer join contactphonenumbers as cpn5
on contacts.recid=cpn5.recid and cpn5.phone_type=2
left outer join contactphonenumbers as cpn6
on contacts.recid=cpn6.recid and cpn6.phone_type=258
left outer join contactphonenumbers as cpn7
on contacts.recid=cpn7.recid and cpn7.phone_type=770
left outer join contactphonenumbers as cpn8
on contacts.recid=cpn8.recid and cpn8.phone_type=514
left outer join contactphonenumbers as cpn9
on contacts.recid=cpn9.recid and cpn9.phone_type=1026;'| sed 's/|/\t/g' > addressbook.tsv

</pre>

put the output through tsv2vcf:
<pre>
perl tsv2vcf addressbook.tsv addressbook.vcf
</pre>

and got a usable vcf File, with some problems with special chars.

== Export raw config (including contacts) with Qtopia ==

scp root@192.168.0.202:~/Applications/Qtopia/qtopia_db.sqlite /tmp/
sqlite3 /tmp/qtopia_db.sqlite .dump

Then you can grep the output for your contacts.

== Import and export for 2007.2 ==

=== Basic Information ===

Neo FreeRunner uses Evolution data server (eds) to save contacts.
However, the specific version used differs from what is probably used on your desktop (if you have Evolution installed).

You ''cannot'' copy your addressbook.db from your desktop to Neo ([http://docs.openmoko.org/trac/ticket/1119 bug 1119]).

=== Import and Manage Scripts ===

If you want to import your old contacts to the Neo you could use this script:

[http://www.smurfy.de/files/neo/manage-contacts Manage Contacts script] [http://www.placard.fr.eu.org/~roland/tmp/manage-contacts.py mirror]

If you first want to remove all existing contacts you could use this script.

[http://www.smurfy.de/files/neo/remove_all_contacts remove all script]

If you have all contacts in seperate vcf files and just want to import all at once:

[http://www.smurfy.de/files/neo/ac Simple script]

[http://www.smurfy.de/files/neo/import_contacts Simple script for one big contactsfile]

(please add a .py after the filename, sorry my hoster gives an error if i link to .py files, even .py.txt)

In the simple scripts you need to add the following lines
ps = os.popen ('ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS')
l = ps.read ()
r = re.compile ('DBUS_SESSION_BUS_ADDRESS=(\S+)')
m = r.search (l)
a = m.expand ('\\1')
os.environ ['DBUS_SESSION_BUS_ADDRESS'] = a

=== Usage ===

The script is for the 2007.2 Version (default install on Neo FreeRunner), not for Qtopia

You need Python to use this script so do a

opkg install python-dbus

to install python and the python dbus module

==== Manage Contacts Script ====

'''This script needs all contacts in one big file'''

'''You also could run this script on a ssh session!'''

# Copy your big contacts file (contacts.txt) to your Neo
# Copy script to your Neo
# Connect via ssh to your Neo
# Fix special chars in your contacts file with you favorite text editor
# To import the file run on the SSH shell:

python manage-contacts.py load < contacts.txt

# For a backup your existing contacts on the Neo

python manage-contacts.py dump > contacts.txt

==== Simple Script ====

'''You must run the script in the OM Terminal, not over ssh'''

The script does a listdir and imports ALL files it found in that dir. (i'm a bad python programmer)

# Copy all vcf files to a separate directory on my freerunner
# Copy the ac script to the parent directory also on my freerunner
# Have the contacts program running (so you have eds running too)
# Go to the terminal on the freerunner and type in the vcf directory: "python ../ac" (root@om-gta02:~/vcf# python ../ac)
## Note: '''You must call the script in the OM terminal''' not via Bluetooth or USB or you get a dbus error. Using "dbus-launch python ../ac" doesn't work either.
# Done :D

==== Troubleshooting ====
* Make sure you have python and python-dbus installed
* Make sure you have no illegal chars (utf) in the filename and inside the vcf files. (I had problems with Ü,Ä etc)
** The characters seem to work if you convert them from =C3=A4 type of format to proper UTF-8, and the vcards also specify UTF-8 charset. you cannot use other charsets besides UTF-8 since they are delivered via DBus which does not allow others.
* Only vcf files should be in your current directory so do a ../ac.
* You must call the script in the OM terminal not via Bluetooth or USB. If you do so a dbus error occur

=== Authors ===

* Simple script by smurfy - phil <openmoko at smurfy.de>
* Manage Contacts script by Roland Mas <lolando at debian.org>
* Remove all Contacts script / simple script for one big file by Andreas Dalsgaard <andreas.dalsgaard at gmail.com>

Thanks to [[Import_Sim_Contacts]] for the original Python Script.

[[Category:Advanced End User]]

Talk:Community Updates

2008-11-30T03:08:08Z

Antisol:

Add news to this page, and from time to time we will issue a community update.

Watch these links:
* Git logs: [http://git.openmoko.org/?p=kernel.git;a=log;h=stable kernel/stable], [http://git.openmoko.org/?p=kernel.git;a=log;h=stable-tracking kernel/stable-tracking], [http://git.openmoko.org/?p=qtopia.git;a=log;h=master Qtopia/master], [http://git.openmoko.org/?p=openmoko.git;a=summary Openmoko's OpenEmbedded], [http://git.openmoko.org/?p=u-boot.git;a=log;h=stable uboot/stable], [http://git.openmoko.org/?p=qi.git;a=log Qi/master]
* Mailing lists: [http://lists.openmoko.org/nabble.html#nabble-f528196 hardware], [http://lists.openmoko.org/nabble.html#nabble-f528196 devel], [http://lists.openmoko.org/nabble.html#nabble-f1954 community], [http://lists.openmoko.org/nabble.html#nabble-f681789 kernel], [http://lists.openmoko.org/nabble.html#nabble-f528183 support], [http://lists.openmoko.org/nabble.html#nabble-f832940 SHR devel], [http://lists.projects.openmoko.org/pipermail/fdom-development/ FDOM devel]
* [http://projects.openmoko.org/ Project news].

How are newsletters organized elsewhere:
http://lists.openmoko.org/pipermail/community/2008-October/032628.html

[[/Archive 1]]

== Applications ==

* A [http://scalde.free.fr/index.php?option=com_content&view=article&id=93:pong-pogresses&catid=43:openmoko&Itemid=66 Pong]
* [http://blog.1407.org/2008/11/19/openmoko-newrotate-050-lazy-edition-is-out/ Newrotate 0.5] is out, uses really little CPU now.
* Valério won the first 24h-coding prize at Sapo Codebits by turning [http://www.valeriovalerio.org/?p=187 freerunner in a mouse and gamepad] using the accelerometers. Code will be merged with [[ReMoko]].
* [[Gtkaddpoi]] 0.5 : software to add a Point Of Interest to TangoGPS.
* neoqplayer 0.1 : codenamed frog. A media player that conserves CPU cycles.
* First release of [[TwitterMoko]], a twitter client for openmoko.
* ShortOm 0.2 : an application/shell launcher.
* openmoko-panel-plugin 0.6 : support for fso frameworkd milestone 4.
* [[Unison]] works.
* [http://www.srcf.ucam.org/~taw27/openmoko/openmoocow/ OpenMooCow] 0.2. Mooes more, runs headless, tickleable.
* [http://www.cs.helsinki.fi/u/rantalai/freerunner/aaterm/ AaTerm], an improved openmoko-terminal2.
* Azmodie proposed a solution for right and middle clicking: Use the gnome accessibility tool [http://live.gnome.org/Mousetweaks/Home mousetweaks] ([http://packages.debian.org/lenny/mousetweaks .deb]).

== Distributions ==

* The [http://downloads.openmoko.org/releases/ official 2008.9 image] is back online without the questionable audio codecs.
* ASU. 2008.11 is not going to see the light, but at least the bug count is decreasing in the testing build (see testing [http://lists.openmoko.org/pipermail/devel/2008-November/003312.html penultimate] and [http://lists.openmoko.org/pipermail/devel/2008-November/003493.html latest] reports, where A7 with capacitor is declared good for mess roduction ;). The testing build is the one with all the fixes from optimization team (read their [http://lists.openmoko.org/pipermail/community/2008-November/036276.html last], [http://lists.openmoko.org/pipermail/community/2008-November/035769.html previous] reports), i.e. about 1 minute boot and [http://git.openmoko.org/?p=qtopia.git;a=commit;h=eb855af76018bedf6a89b9ac736d2ffa3961932b Volume control] during call.
* SHR. [http://lists.openmoko.org/nabble.html#nabble-td1576966 newer snapshot] available.
* For [[Android]]: Walter Chang [http://lists.openmoko.org/pipermail/community/2008-November/036054.html made a soft keyboard]. Rui Castro implemented an [http://lists.openmoko.org/pipermail/community/2008-November/036564.html OnScreen Keyboard]. It was immediately included in Sean's image, to be released at [[User:Seanmcneil3|the usual page]] without mp3 support soon.

== Hardware ==

* For an armband to hold the Freerunner while exercising, Gilles Casse recommends the [http://www.caselogic.com/universal_mp3_sport_case_large/product_detail/index.cfm?modelid=120544 UMC-3] from Case Logic.
* Patrick Beck grafted a light on a miniusb - connector, to make an [http://yourse.de/wiki/doku.php?id=openmoko:usb_light OpenMoko flash light]. More lumens the bright white screen one get with the [http://projects.openmoko.org/projects/flashlight/ Flashlight] script.
* The [http://lists.openmoko.org/pipermail/community/2008-November/036132.html official fix] for buzzing is to add a 100uF capacity here and replace one resistance there. Technical details to be published in an Openmoko rework SOP paper. The company is looking at how to fix *all* devices sold.
* The Calypso GSM firmware moko10 was released, it fixes {{ticket|666}} for those users with 3G SIM cards. A few Indiana Jones types did try and follow [http://wiki.openmoko.org/wiki/GSM/Flashing the wiki instructions] to reflash, most with success, some with hubris (def: excessive pride). For the rest of us, a user-friendly installer is being prepared.

== Kernel and bootloaders ==

Big bad bug of the month prize goes to {{ticket|1841}} white screen of death (WSOD) after resume. This bug shows itself only by cold weather! Nicolas Dufresne found out that the culprit was probably a too tight timing in the JBT driver. Hopefully this will be fixed soon now, and we can all switch to Linux 2.6.28 happily everafter. Developpers must read [http://lists.openmoko.org/pipermail/community/2008-November/036142.html Andy's explanations] about kernel branch management.

* Preview upcoming [http://lists.openmoko.org/nabble.html#nabble-td1569863 changes to the /sys] directory.
* Improvements to the touchscreen, backlight and accelleremometers kernel drivers.
* [[Qi]] gets lots of GTA03 love, audio back and a memory test ability (called when there are no valid kernels).
* The opkg package manager was patched to cache downloaded files.

==Community==
* Removed the tagcloud extension that messed up with page formatting.
* There are many links to nice [[Ringtones]] on the wiki, but the page and the whole topic need a good overhaul.
* GnuPhone here we come: Sten Kvamme explains how to [http://lists.openmoko.org/pipermail/devel/2008-November/003318.html make a call from the command line] (on FSO).
* For your pleasure, here is the OpenMoko [[Jokes]] page. Thanks to the community, keep them coming ;) We (Coolcat and I) are also thinking about adding a pic of the week to the homepage, so stay tuned.
* Courtesy of Dale Maggee, [http://lists.openmoko.org/pipermail/community/2008-November/036053.html here] and [http://lists.openmoko.org/pipermail/community/2008-November/036142.html here] are a few funny splash screens. Note that you already trust Dale if you are using ''neotool'' to flash your Neo.

NeoTool

2008-10-31T06:41:46Z

Antisol: v1.2 released - info added

NeoTool is a bash script for your desktop system to provide a friendly GUI frontend to some common management tasks, like for example flashing Openmoko smartphones. It is aimed at being very intuitive and easy to use, and flexible enough to make it useful in a wide variety of circumstances.

== Features ==

The main features of NeoTool are:
* Ability to flash your Neo via a GUI
* Ability to flash multiple images at once (for example, flash rootfs and the kernel at the same time)
* Ability to backup your Neo via a GUI
* Ability to backup Multiple images at once
* rootfs can be backed up to either a flashable image or a tar archive
* most / all configuration can be done via the GUI

== Screenshots ==
[[Image:NeoTool.png|NeoTool opening screen]]

== Download / Releases ==

The most recent version of NeoTool is available for download at http://users.on.net/~antisol/neotool

When a new version is released it will be announced on the community mailing list, and on this page.

== Requirements ==

The software prerequisites for NeoTool should be installed on most modern linux systems by default:
* bash
* zenity
* which
* awk

* dfu-util is required to be able to flash your Neo, but NeoTool is able to download this automatically.

=== Optional ===

* pipe viewer (pv), shows display while backing up rootfs

* to backup rootfs, you need to have a [[USB_Networking|USB networking]] configured and working

* mkfs-jffs2 needs to be installed on your neo to backup rootfs to a flashable image (type 'opkg install mkfs-jffs2' in ssh)

* While not a requirement, backing up rootfs is much less painful if you set up an authorized_keys entry for your host on your Neo. To do this, run 'ssh-keygen' (preferrably as root) on your host, and then copy the contents of ~/.ssh/id_rsa.pub on your host into /home/root/.ssh/authorized_keys on your freerunner

<pre>
user@host# su

root@host# ssh-keygen

root@host# scp ~/.ssh/id_rsa.pub root@<Neo IP Address>:/home/root

root@host# ssh root@<Neo IP Address>
root@om-gta02:~# cat id_rsa.pub >> /home/root/.ssh/authorized_keys

</pre>

This will prevent you from having to enter the password for your Neo when you use ssh and scp.

If you don't do this, you will need to enter your password repeatedly in order to backup rootfs.

== Usage ==

NeoTool should usually be run as root, although this is not required if you only want to backup rootfs and/or the kernel via scp.

<pre>sudo ./neotool</pre>

You will initially be presented with the main menu. Most of the functions should be relatively self-explanatory

(thorough documentation on usage goes here)

== Revision History ==

See [http://lists.openmoko.org/pipermail/community/2008-September/029731.html this thread] and [http://lists.openmoko.org/pipermail/community/2008-September/030257.html that update] for discussions on the community list.

=== 09-Sep-2008 ===

- ability to flash more than one image at once - the 'what do you wanna
flash' now has checkboxes instead of radio buttons, and all your
selections are flashed one after the other. (which i find very handy,
stops the FR powering down while you're typing the next dfu-util
command, or locating the next image - works great for flashing a new
distro & kernel). if an error occurs, subsequent files will not be flashed.

- more confirmation / idiot-proofing - it now tells you what you're
doing much more clearly (i.e: "about to flash Kernel with /foo/bar.bin,
rootfs with /foo/bar.jffs". allows you to confirm that you chose the
right images). also the 'choose file' dialogs tell you what you're
browsing for

- ability for users to press 'cancel' at the various dialogs and exit
gracefully.

- checks that dfu-util exists and is executable. I moved my dfu-util to
/usr/local/bin, so it looks there first, but it will also check the
current directory and prompt if it can't find it

- I wasn't a fan of patching dfu-util, and the pulsating zenity progress
dialog drags my (prehistoric) PC to a crawl, so I disabled the progress
bar and use the text output of dfu-util instead.

=== 12-Sep-2008 (v1.0) ===

- Utility now has the ability to flash the splash image as per request

- Utility can now also backup your device to flashable rootfs / kernel images (david might like this for building FDOM images)

- Configurification is loaded on startup and saved in /etc/frutil (you can only modify settings if you run it as root)

- more idiot proofing - uses 'which' to find dfu-util, checks to ensure it's being run as root, checks that zenity is installed on the host, checks that you have mkfs.jffs2 installed before backing up, checks that you have pv installed and acts accordingly (by either using it or not during the backup [this is not properly tested because I don't have pv, please report]), and possibly other stuff I've forgotten about.

- new name (frutil) to reflect the new abilities

=== 17-Sep-2008 (v1.1) ===

- Added ChangeLog

- Added ability to handle multiple DFU-capable devices

- Changed references to 'freerunner' to 'neo'

- name changed to NeoTool (despite implied connection with Keanu Reeves' crotch)

- Added 'Reset to defaults' option

- Added warning that flashing uboot on neo1973 may result in a paperweight

- several small bugfixes

- made backup functionality much more versatile:

- made backup filenames configurable

- Added ability to choose what to backup

- Added rootfs backup type option (jffs2 or tar)

- Added kernel backup method option (scp or dfu)

- Added ability to backup uboot and splash

=== 31-Sep-2008 (v1.2) ===
- Changed information at pre-flash prompt to include instructions for how to get to the NOR menu. eliminated any mention of NAND, as everything can be flashed from NOR.

- bugfix - when user selects a filename under 'customize backup filenames' and then presses cancel, the selected filename was set to nothing.

- NeoTool now checks that the path of backup files exist, and attempts to create it if it doesn't. This allows you to organise your backups in a folder hierarchy, i.e set the backup filename to: /data/openmoko/backups/{date}/{image}_backup and the {date} directory will be created by NeoTool, assuming /data/openmoko/backups exists and you have permission.

== Support ==

Suggestions? comments? feedback? problems?
* Are all welcome
* Email the Community list,
* or, email antisol (at) internode (dot) on (dot) net

<strike>NeoTool is perfect in every respect - if it breaks it's because you did something wrong.</strike>

[[Category:Flashing Openmoko]]
[[Category:Host OSes]]

Configuring the boot splash screens

2008-10-25T05:07:05Z

Antisol: Plugged NeoTool

There are three boot screens (also called splashes or splash screens) as of 13 Nov. 2007. The U-Boot splash is displayed until the kernel takes over. Presumably the kernel will eventually display a splash while it boots. When userspace initializes, psplash displays a splash. Finally X displays a splash when it starts.

== U-boot Splash ==

=== Original instructions ===
Is a raw framebuffer bitmap that is gzipped.

Here is a basic description: http://svn.openmoko.org/trunk/src/host/splash/README

Use [[dfu-util]] or [[NeoTool]] to send to the Openmoko.

=== Instructions which worked for me ===
The above instruction did not work, unfortunately, maybe there were for a previous release of u-boot. The following did work for me:

* Install the appropriate tools
** Download the README and the Perl script from http://svn.openmoko.org/developers/werner/splash/
** chmod a+rx *.pl
** Be sure to have netpbm installed

* How to use the tools
** First, make a PNG 480x640x8 (or just get the original picture from http://wiki.openmoko.org/images/c/c2/), and name it System_boot.png
** Convert the System_boot.png into a compressed converted image file splash.gz, then download it to the splash partition (the neo1973 must be in u-boot mode, and you need dfu-util)
*** ./imghs.pl | gzip -9 > splash.gz
*** sudo ../bin/dfu-util -a splash -R -D splash.gz
** If the size of splash.gz is not exactly 0x5000, please see the next section.

=== Modifying the size of the compressed splash image ===
NOTE... the README states you must issue two U-Boot commands to enable the flashed splash image to appear on the screen at boot:

''setenv splashimage nand read.e 0x32000000 splash 0x5000\; unzip 0x32000000 0x33d00000 0x96000''
''saveenv''

This is already a part of the U-Boot image received in the phone... however, if you make changes to your splash image, you may need to change the splashimage variable to compensate!

0x5000 is the (maximum) size of the compressed file -- the splash.gz that gets created. If you've made changes to your image you may have increased the compressed size; if it exceeds 0x5000 (20480) bytes, the entire image will not load unless you increase this value in your splashimage U-Boot environment variable.

Note that the framebuffer address on GTA02 is mapped to 0x8800000, not 0x33d00000

=== See also ===

This ticket has recent explanations: <strike>[http://docs.openmoko.org/trac/ticket/1735 1735]</strike>.

== Linux kernel ==
''To Do''

== psplash ==
You need to recompile psplash, because the picture is hardcoded. There is a script in the source for psplash for making a new header file. On Ubuntu, you need the libgtk2.0-dev package to run the script.

make-image-header.sh my_image.png HAND
mv my_image-img.h psplash-hand-img.h

Then add your custom header to the OpenEmbedded recipe (org.openembedded.dev/packages/psplash/files/openmoko/psplash-hand-img.h), or rebuild psplash by hand.

== X splash ==

The X server accepts a -root-ppm option, which takes a plain old (raw) ppm file. Replace /usr/share/pixmaps/xsplash-vga.ppm on the phone or org.openembedded.dev/packages/xserver-kdrive-common/xserver-kdrive-common/openmoko/xsplash-vga.ppm in OpenEmbedded.

[[Category:Application Developer]]

Backup

2008-09-17T13:57:46Z

Antisol: /* Pretty GUI Script */

== Backing up just /home/root ==

To backup the home folder (all your personal files in theory).

From the desktop pc run:

ssh root@phone 'tar -cpz /home/root' > moko-home-`date +%Y%m%d-%H%M%S`.tar.gz

Where phone is the ip address of your phone (192.168.0.202).

Personally I added an entry to /etc/hosts so the above works for me. I also added the desktop key to /home/root/.ssh/authorized_keys on the phone as per the instructions in [[USB_Networking#SSH_Keys]].

If you want to check what is in the backup, run the following, replacing the filename with what was just created.

tar -tzf moko-home-20080802-203108.tar.gz | less

[http://timwise.wikispaces.com/my+neo+freerunner reference]

== Backing up everything ==

You may either :
* Backup the flash contents, in order to be able to restore (see below)
* or move the system to SD to be able to boot it from SD in case of need. See [[Moving current system from flash to SD]]

=== Backing-up flash images ===

{{note|Upload support is currently broken - [http://docs.openmoko.org/trac/ticket/676 #676]}}

You will need the [[Dfu-util]] to make a backup of your existing image.

As when [[Flashing_the_Neo_FreeRunner|flashing]], you will need to be in [[Booting_the_Neo_FreeRunner#Log_into_U-Boot_in_the_NOR_Flash|U-Boot in the NOR Flash]]. Log into the NOR uBoot menu and select ''Set console to USB'' (for NRF just stay in NOR uBoot menu, do not select or enter anything). Now you will be able to flash, make backups of your FreeRunner or query the FreeRunner with [[Dfu-util|dfu-util]]. Backup is fairly slow; it took over ten minutes to back up a 247 MB rootfs.

It is important that you connect the USB cable directly from your computer to your phone. If there is a hub between them, backup (and flashing) will mostly likely fail.

{{note|On a Windows host, omit the "./" or "sudo ./" that precedes the commands listed on this page}}

<pre>
sudo ./dfu-util -a kernel -R -U good-kernel.bin
sudo ./dfu-util -a rootfs -R -U good-rootfs.jffs2
sudo ./dfu-util -a splash -R -U good-splash.bin
sudo ./dfu-util -a u-boot -R -U good-u-boot.bin
sudo ./dfu-util -a u-boot_env -R -U good-u-boot_env.bin
</pre>

Here is what a successful dfu-util backup run looks like:

on the host PC:
<pre>
$ sudo ./dfu-util -a kernel -R -U good-kernel.img
dfu-util - (C) 2007 by Openmoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Opening USB Device 0x0000:0x0000...
Claiming USB DFU Runtime Interface...
Determining device status: state = appIDLE, status = 0
Device really in Runtime Mode, send DFU detach request...
Resetting USB...
Opening USB Device...
Found Runtime: [0x1d50:0x5119] devnum=12, cfg=0, intf=0, alt=3, name="kernel"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x1000
Resetting USB to switch back to runtime mode
</pre>

on the FreeRunner:
<pre>
DFU: Switching to DFU Mode
DEVICE_CONFIGURED: 1
Starting DFU Upload of partition 'kernel'
</pre>

A failed run of dfu-util looks like this:

dfu-util - (C) 2007 by Openmoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Opening USB Device 0x0000:0x0000...
Claiming USB DFU Runtime Interface...
Determining device status: state = appIDLE, status = 0
Device really in Runtime Mode, send DFU detach request...
Resetting USB...
Opening USB Device...
Found Runtime: [0x1d50:0x5119] devnum=20, cfg=0, intf=0, alt=6, name="rootfs"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x1000
dfu_upload error -110

And shows errors demsg like this:
usb 5-2: usbfs: USBDEVFS_CONTROL failed cmd dfu-util rqt 161 rq 2 len 4096 ret -110

=== Backing-up flash images (alternative) ===

On the device:
mkdir /var/tmp/root
mount /dev/root /var/tmp/root

On your workstation:
ssh root@192.168.0.202 "mkfs.jffs2 -d /var/tmp/root -e 128 --pad --no-cleanmarkers -x lzo" | pv -W > rootfs.jffs2
(The "| pv -W" is optional, it just gives you something to watch as the bytes fly by.)

On the device:
umount /var/tmp/root

=== Backing-up in a tar archive ===

ssh root@192.168.0.202 "tar c /bin /etc /home /lib /opt /sbin /tmp /usr /var" | pv -W > rootfs.tar
(The "| pv -W" is optional, it just gives you something to watch as the bytes fly by.)

Extract it and use <code>mkfs.jffs2</code> if you want convert it to a jffs2 image.

==Backup Scripts==

If you plan on backing up frequently, using a script will simplify the process:

===Simple backup script===

This script works well if you want to configure it to backup always the same device.

<pre>
#!/bin/sh
#
# Back up all partitions of the phone to a backup directory,
# adding today's date to the saved filenames.

DATE=`date +%Y-%m-%d`
DFU=./dfu-util
BACKUP_DIR=bak/

${DFU} -a kernel -R -U ${BACKUP_DIR}kernel-${DATE}.bin
${DFU} -a rootfs -R -U ${BACKUP_DIR}rootfs-${DATE}.jffs2
${DFU} -a splash -R -U ${BACKUP_DIR}splash-${DATE}.bin
${DFU} -a u-boot -R -U ${BACKUP_DIR}u-boot-${DATE}.bin
${DFU} -a u-boot_env -R -U ${BACKUP_DIR}u-boot_env-${DATE}.bin
</pre>

===Interactive script===

This script is based on the above "Simple backup script" (by unknown). It does the backup of what you want and choose promting you for choices. Enjoy it! test it! contribute! You can find us at /server irc.freenode.net /j #openmoko and we'll be pleased to accept you help (ideas || code).

NOTE that the script works for me(tm) but it still needs some love. especially on traps and catches for wrong choices.

<pre>
#!/bin/bash

#############################################################################################################
## ##
## This script is Free Software is licensed under the GPLv3 and has ABSOLUTELY NO WARRANTY ##
## you can find and read the complete version of the GPLv3 @ http://www.gnu.org/licenses/gpl.html ##
## ##
## Q: what does this script do? ##
## A: the script back up all partitions of the phone to a backup directory, interactively, ##
## adding today's date to the saved filenames. ##
## ##
## IMPORTANT:!!! REMEMBER TO RUN THIS SCRIPT AS ROOT SINCE dfu-util HAS TO BE USED AS ROOT!!! ##
## ##
## based on the orginal simple backup script at http://wiki.openmoko.org/wiki/Pre-Flash_Backup ##
## ##
## this version has been conceived and written by cga, x77686d, Infoport, jomat at /server irc.freenode.net##
## /j #openmoko,#bash and my collegue aubba @ work. ##
## ##
## for any suggestions and contributions contact cga (or one of the above) in the #openmoko channel ##
## ##
#############################################################################################################

## let's roll!!

## sets the date format for the date in the backup file, change accordingly to your local custom if you need
DATE=`date +%d-%m-%Y`

## here the scripts try to find the dfu-util binary and set it as the DFU var:
if which dfu-util >/dev/null ; then
echo
echo "dfu-util found in your path"
echo
## 1 the function use this if you placed/linked dfu-util in your $PATH
DFU=dfu-util

elif ls dfu-util >/dev/null ; then
echo
echo "dfu-util found in current directory"
echo
## or 2 use following line if dfu-util is placed in the same directory where you run the script
DFU=./dfu-util

else
## or 3 if the script doesn't find dfu-util shows the link for installing it and exit
echo
echo "dfu-util NOT found! install and use howto @ http://wiki.openmoko.org/wiki/Dfu-util"
echo
exit 1
fi

## here we get the hex code for devices found with dfu-util --list
## the hex code is grabbed and the name of the device is shown accordingly and you are prompetd to chose the right one:
echo
echo 'these are the devices i found:'
echo
for device in `${DFU} --list | grep 0x | cut -f3 -d' ' | tr -d '[]'` ; do
if [ "$device" == '0x1457:0x5119' ] ; then
echo 'Neo 1973'
elif [ "$device" == '0x1d50:0x5119' ] ; then
echo "Neo FreeRunner"
else
echo 'other device found, DO NOT use dfu-util on this!!! it might bork it...'
exit 1
fi
done | nl
echo
echo 'choose the device to backup:'
echo
read selection
HEX=$(${DFU} --list | grep 0x | head -n $selection | tail -1 | cut -f3 -d' ' | tr -d '[]')

## use the built-in read command to ask you and use the directory for the backup
while [ -z "$BACKUP_DIR" ] ; do
echo
read -e -p $"enter the directory for the backup:" BACKUP_DIR
echo

## chek wether the dir exist and proceed, else create it and proceed.
if [ ! -d "$BACKUP_DIR" ] ; then
echo
echo -n "$BACKUP_DIR does not exist, create it? [Y/n] "
echo
read CREATE_DIR
if [ x"$CREATE_DIR" = xy -o x"$CREATE_DIR" = xY -o -z "$CREATE_DIR" ] ; then
mkdir -p -v "${BACKUP_DIR}"
else
BACKUP_DIR=
fi
fi
done

## here you get prompted to chose the backup you want, you can backup single files or all of them.
echo
echo 'choose the component to backup from the list:'
echo

select howto in kernel splash u-boot u-boot_env rootfs all quit; do
if [ "$howto" == "kernel" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a kernel -R -U ${BACKUP_DIR}/kernel-${DATE}.bin
fi
if [ "$howto" == "splash" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a splash -R -U ${BACKUP_DIR}/splash-${DATE}.bin
fi
if [ "$howto" == "u-boot" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a u-boot -R -U ${BACKUP_DIR}/u-boot-${DATE}.bin
fi
if [ "$howto" == "u-boot_env" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a u-boot_env -R -U ${BACKUP_DIR}/u-boot_env-${DATE}.bin
fi
if [ "$howto" == "rootfs" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a rootfs -R -U ${BACKUP_DIR}/rootfs-${DATE}.jffs2
fi
if [ "$howto" == "quit" ] ; then
exit 0
fi
echo
echo 'the component(s) has/have been backed up, what next? (press enter for menu)'
echo
done

exit 0

</pre>

=== Pretty GUI Script ===

[[NeoTool]] is a zenity-based script which allows you to both backup and Flash your device from a pretty GUI. It uses both the dfu-util method and the alternate method described on this page, and can produce flashable images of everything including rootfs. Check it out.

[[category:Advanced End User]]
[[Category:Flashing Openmoko]]

Backup

2008-09-17T13:54:37Z

Antisol: Added link to NeoTool

== Backing up just /home/root ==

To backup the home folder (all your personal files in theory).

From the desktop pc run:

ssh root@phone 'tar -cpz /home/root' > moko-home-`date +%Y%m%d-%H%M%S`.tar.gz

Where phone is the ip address of your phone (192.168.0.202).

Personally I added an entry to /etc/hosts so the above works for me. I also added the desktop key to /home/root/.ssh/authorized_keys on the phone as per the instructions in [[USB_Networking#SSH_Keys]].

If you want to check what is in the backup, run the following, replacing the filename with what was just created.

tar -tzf moko-home-20080802-203108.tar.gz | less

[http://timwise.wikispaces.com/my+neo+freerunner reference]

== Backing up everything ==

You may either :
* Backup the flash contents, in order to be able to restore (see below)
* or move the system to SD to be able to boot it from SD in case of need. See [[Moving current system from flash to SD]]

=== Backing-up flash images ===

{{note|Upload support is currently broken - [http://docs.openmoko.org/trac/ticket/676 #676]}}

You will need the [[Dfu-util]] to make a backup of your existing image.

As when [[Flashing_the_Neo_FreeRunner|flashing]], you will need to be in [[Booting_the_Neo_FreeRunner#Log_into_U-Boot_in_the_NOR_Flash|U-Boot in the NOR Flash]]. Log into the NOR uBoot menu and select ''Set console to USB'' (for NRF just stay in NOR uBoot menu, do not select or enter anything). Now you will be able to flash, make backups of your FreeRunner or query the FreeRunner with [[Dfu-util|dfu-util]]. Backup is fairly slow; it took over ten minutes to back up a 247 MB rootfs.

It is important that you connect the USB cable directly from your computer to your phone. If there is a hub between them, backup (and flashing) will mostly likely fail.

{{note|On a Windows host, omit the "./" or "sudo ./" that precedes the commands listed on this page}}

<pre>
sudo ./dfu-util -a kernel -R -U good-kernel.bin
sudo ./dfu-util -a rootfs -R -U good-rootfs.jffs2
sudo ./dfu-util -a splash -R -U good-splash.bin
sudo ./dfu-util -a u-boot -R -U good-u-boot.bin
sudo ./dfu-util -a u-boot_env -R -U good-u-boot_env.bin
</pre>

Here is what a successful dfu-util backup run looks like:

on the host PC:
<pre>
$ sudo ./dfu-util -a kernel -R -U good-kernel.img
dfu-util - (C) 2007 by Openmoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Opening USB Device 0x0000:0x0000...
Claiming USB DFU Runtime Interface...
Determining device status: state = appIDLE, status = 0
Device really in Runtime Mode, send DFU detach request...
Resetting USB...
Opening USB Device...
Found Runtime: [0x1d50:0x5119] devnum=12, cfg=0, intf=0, alt=3, name="kernel"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x1000
Resetting USB to switch back to runtime mode
</pre>

on the FreeRunner:
<pre>
DFU: Switching to DFU Mode
DEVICE_CONFIGURED: 1
Starting DFU Upload of partition 'kernel'
</pre>

A failed run of dfu-util looks like this:

dfu-util - (C) 2007 by Openmoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Opening USB Device 0x0000:0x0000...
Claiming USB DFU Runtime Interface...
Determining device status: state = appIDLE, status = 0
Device really in Runtime Mode, send DFU detach request...
Resetting USB...
Opening USB Device...
Found Runtime: [0x1d50:0x5119] devnum=20, cfg=0, intf=0, alt=6, name="rootfs"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x1000
dfu_upload error -110

And shows errors demsg like this:
usb 5-2: usbfs: USBDEVFS_CONTROL failed cmd dfu-util rqt 161 rq 2 len 4096 ret -110

=== Backing-up flash images (alternative) ===

On the device:
mkdir /var/tmp/root
mount /dev/root /var/tmp/root

On your workstation:
ssh root@192.168.0.202 "mkfs.jffs2 -d /var/tmp/root -e 128 --pad --no-cleanmarkers -x lzo" | pv -W > rootfs.jffs2
(The "| pv -W" is optional, it just gives you something to watch as the bytes fly by.)

On the device:
umount /var/tmp/root

=== Backing-up in a tar archive ===

ssh root@192.168.0.202 "tar c /bin /etc /home /lib /opt /sbin /tmp /usr /var" | pv -W > rootfs.tar
(The "| pv -W" is optional, it just gives you something to watch as the bytes fly by.)

Extract it and use <code>mkfs.jffs2</code> if you want convert it to a jffs2 image.

==Backup Scripts==

If you plan on backing up frequently, using a script will simplify the process:

===Simple backup script===

This script works well if you want to configure it to backup always the same device.

<pre>
#!/bin/sh
#
# Back up all partitions of the phone to a backup directory,
# adding today's date to the saved filenames.

DATE=`date +%Y-%m-%d`
DFU=./dfu-util
BACKUP_DIR=bak/

${DFU} -a kernel -R -U ${BACKUP_DIR}kernel-${DATE}.bin
${DFU} -a rootfs -R -U ${BACKUP_DIR}rootfs-${DATE}.jffs2
${DFU} -a splash -R -U ${BACKUP_DIR}splash-${DATE}.bin
${DFU} -a u-boot -R -U ${BACKUP_DIR}u-boot-${DATE}.bin
${DFU} -a u-boot_env -R -U ${BACKUP_DIR}u-boot_env-${DATE}.bin
</pre>

===Interactive script===

This script is based on the above "Simple backup script" (by unknown). It does the backup of what you want and choose promting you for choices. Enjoy it! test it! contribute! You can find us at /server irc.freenode.net /j #openmoko and we'll be pleased to accept you help (ideas || code).

NOTE that the script works for me(tm) but it still needs some love. especially on traps and catches for wrong choices.

<pre>
#!/bin/bash

#############################################################################################################
## ##
## This script is Free Software is licensed under the GPLv3 and has ABSOLUTELY NO WARRANTY ##
## you can find and read the complete version of the GPLv3 @ http://www.gnu.org/licenses/gpl.html ##
## ##
## Q: what does this script do? ##
## A: the script back up all partitions of the phone to a backup directory, interactively, ##
## adding today's date to the saved filenames. ##
## ##
## IMPORTANT:!!! REMEMBER TO RUN THIS SCRIPT AS ROOT SINCE dfu-util HAS TO BE USED AS ROOT!!! ##
## ##
## based on the orginal simple backup script at http://wiki.openmoko.org/wiki/Pre-Flash_Backup ##
## ##
## this version has been conceived and written by cga, x77686d, Infoport, jomat at /server irc.freenode.net##
## /j #openmoko,#bash and my collegue aubba @ work. ##
## ##
## for any suggestions and contributions contact cga (or one of the above) in the #openmoko channel ##
## ##
#############################################################################################################

## let's roll!!

## sets the date format for the date in the backup file, change accordingly to your local custom if you need
DATE=`date +%d-%m-%Y`

## here the scripts try to find the dfu-util binary and set it as the DFU var:
if which dfu-util >/dev/null ; then
echo
echo "dfu-util found in your path"
echo
## 1 the function use this if you placed/linked dfu-util in your $PATH
DFU=dfu-util

elif ls dfu-util >/dev/null ; then
echo
echo "dfu-util found in current directory"
echo
## or 2 use following line if dfu-util is placed in the same directory where you run the script
DFU=./dfu-util

else
## or 3 if the script doesn't find dfu-util shows the link for installing it and exit
echo
echo "dfu-util NOT found! install and use howto @ http://wiki.openmoko.org/wiki/Dfu-util"
echo
exit 1
fi

## here we get the hex code for devices found with dfu-util --list
## the hex code is grabbed and the name of the device is shown accordingly and you are prompetd to chose the right one:
echo
echo 'these are the devices i found:'
echo
for device in `${DFU} --list | grep 0x | cut -f3 -d' ' | tr -d '[]'` ; do
if [ "$device" == '0x1457:0x5119' ] ; then
echo 'Neo 1973'
elif [ "$device" == '0x1d50:0x5119' ] ; then
echo "Neo FreeRunner"
else
echo 'other device found, DO NOT use dfu-util on this!!! it might bork it...'
exit 1
fi
done | nl
echo
echo 'choose the device to backup:'
echo
read selection
HEX=$(${DFU} --list | grep 0x | head -n $selection | tail -1 | cut -f3 -d' ' | tr -d '[]')

## use the built-in read command to ask you and use the directory for the backup
while [ -z "$BACKUP_DIR" ] ; do
echo
read -e -p $"enter the directory for the backup:" BACKUP_DIR
echo

## chek wether the dir exist and proceed, else create it and proceed.
if [ ! -d "$BACKUP_DIR" ] ; then
echo
echo -n "$BACKUP_DIR does not exist, create it? [Y/n] "
echo
read CREATE_DIR
if [ x"$CREATE_DIR" = xy -o x"$CREATE_DIR" = xY -o -z "$CREATE_DIR" ] ; then
mkdir -p -v "${BACKUP_DIR}"
else
BACKUP_DIR=
fi
fi
done

## here you get prompted to chose the backup you want, you can backup single files or all of them.
echo
echo 'choose the component to backup from the list:'
echo

select howto in kernel splash u-boot u-boot_env rootfs all quit; do
if [ "$howto" == "kernel" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a kernel -R -U ${BACKUP_DIR}/kernel-${DATE}.bin
fi
if [ "$howto" == "splash" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a splash -R -U ${BACKUP_DIR}/splash-${DATE}.bin
fi
if [ "$howto" == "u-boot" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a u-boot -R -U ${BACKUP_DIR}/u-boot-${DATE}.bin
fi
if [ "$howto" == "u-boot_env" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a u-boot_env -R -U ${BACKUP_DIR}/u-boot_env-${DATE}.bin
fi
if [ "$howto" == "rootfs" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a rootfs -R -U ${BACKUP_DIR}/rootfs-${DATE}.jffs2
fi
if [ "$howto" == "quit" ] ; then
exit 0
fi
echo
echo 'the component(s) has/have been backed up, what next? (press enter for menu)'
echo
done

exit 0

</pre>

=== Pretty GUI Script ===

[[NeoTool]] is a zenity-based script which allows you to both backup and Flash your device from a pretty GUI. Check it out.

[[category:Advanced End User]]
[[Category:Flashing Openmoko]]

Flashing the Neo FreeRunner

2008-09-17T13:48:19Z

Antisol: Changed GUI script to point to the new NeoTool page

{{Languages|Flashing_the_Neo_FreeRunner}}
Openmoko regularly releases updated versions of the Openmoko root filesystem, the [[kernel]], and the [[Bootloader| U-Boot]] as binary images. These may be programmed into the Flash memory (NAND) of Neo FreeRunner. For that, you can use the USB cable and another computer which will run an Openmoko provided tool to flash the Neo FreeRunner "through" USB.

== Overview ==
All the components of the software in the FreeRunner are bundled together into binary images.

On a desktop computer when you want to replace the operating system (OS), you would boot it from a CD-ROM drive, then copy OS files from the CD to the internal hard drive. The FreeRunner does not have a CD-ROM drive and files must typically be re-written/flashed directly into internal storage (NAND flash). It is also possible to load all the OS files to and boot from a microSD.

The FreeRunner has two kinds of internal program storage: NOR flash and NAND flash. The NOR flash is small and stores only a special boot program used when you need to re-write the contents of the NAND flash. NAND flash acts more like a hard drive.

The NAND Flash is divided into 3 partitions for the bootloader, kernel, and root filesystem - so each of these components can be flashed separately. For example if you are trying to install a modified kernel, you only have to follow the steps to flash the kernel image.

* '''bootloader''': a small program that runs first and starts everything else when the FreeRunner is powered on or reset (depending on [[Booting the Neo FreeRunner|how you reset it]], the version from NOR or NAND is booted).
* '''kernel''': the central component in the Linux operating system.
* '''root filesystem''': contains all the files that make up the commands and applications that you can run.

'''Before you start: Erasing the root filesystem or flashing the uboot are radical measures. Take the time to ponder the necessity. Sometimes problems can be fixed by updating only the kernel.'''

== Alternative : running from microSD card ==

You may install this distribution on the microSD card, in order to [[Booting from SD | boot from microSD card]]. That allows you to keep another distribution installed in NAND (for instance to test 2008.08 while still having 2007.2 for default boot).

== Collect the things you need ==

=== Download the DFU-util program ===

You will download that program on your desktop computer. It will allow you to connect to the FreeRunner through the USB cable and control its bootloader. That connection uses a special protocol which addresses the bootloader's interface, and differs from USB networking. There is a separate page to describe it in more detail: [[dfu-util]].

'''MacOS X:''' [[MacOS_X#Graphical_Flashing_with_Openmoko_Flasher]]

'''Linux:''' http://downloads.openmoko.org/releases/Om2008.8-update/dfu-util

Make sure it is executable by setting the permissions with this command: chmod a+x dfu-util

'''Note:''' dfu-util seems to consistently fail with a "-62" error on 64-bit Linux. If you have access to a 32-bit machine, use it instead!
There are some ubuntu64 interpid packages which work just fine for me in hardy too. So you might try at your own risk: [http://packages.ubuntu.com/de/intrepid/dfu-util].

Using 32-bit chroot (on amd64 debian) worked for me --[[User:Bubak|Bubak]] 16:54, 4 September 2008 (UTC).

'''Windows:''' http://projects.openmoko.org/frs/?group_id=166&release_id=162

See additional driver installation instructions for Windows at [[Dfu-util-windows]]

=== Download the image files that you will need ===

Exactly what files you need depends on what you are trying to install. In most cases you will need to install a Kernel (uImage) and a Root Filesystem (rootfs). In rare cases, when there is a bug you need fixed, you will also install a new bootloader.

Please read [[Distributions]] for choosing the distribution which fits your needs, and then see [[Download]] for downloading.

== Boot the FreeRunner from NOR Flash ==

[[Image:menu15.jpg|thumb|Booting from NOR Flash]]

# Read the other sections of this page first, because you will have 30 seconds to enter the flashing commands, come back here when ready.
# Do not connect the USB cable from the PC to your Neo FreeRunner yet (disconnect it).
# Boot your Neo FreeRunner into the NOR uBoot menu for flashing.
## Press and hold AUX button
## Press the Power button until the boot menu comes up
## This menu is labelled '''*** BOOT MENU (NOR) ***'''
## See also [[Booting the Neo FreeRunner]]
# Stay in NOR uBoot menu, do not select or enter any item in menu. Now you will be able to flash, make backups of your FreeRunner or query the FreeRunner with dfu-util.
# The FreeRunner only stays at the NOR boot prompt for about 30 seconds and then shuts off unless you do something.
# Connect your Neo to the GNU/Linux or Windows host via a USB cable.
# Now you can enter the dfu-util commands on your PC as described below.
# If the Neo FreeRunner turns off before you press start flashing ('''screen goes black'''), go back to step 2. If you start flashing in time, the phone will not turn off meanwhile.



Note that the dfu-util connection does '''not''' use Ethernet over USB - that is, you should not attempt to set up a usb0 network interface on your GNU/Linux host desktop (on Windows, you need a DFU class driver, or you can use the LibUSB-Win32 driver described on the [[Dfu-util-windows]] page). The dfu-util utility sets up its own connection to the FreeRunner. In fact, you will not be able to make an Ethernet-over-USB connection to the FreeRunner when it is at the uBoot menu; this type of connection is only available when the FreeRunner has booted fully.

After connecting the FreeRunner to your host via USB cable, you can test whether dfu-util "sees" the FreeRunner by executing:

dfu-util -l

If you get error messages from the dfu-util command then try again. Often it works on the second try.

Also, please remember to execute the dfu-util command with sufficient privileges (ie. root) -- you will need complete control over the usb bus.

== Do a backup ==

If you have a working image that you're happy with but want to try something different, you should probably do a [[Pre-Flash Backup]].

== Using dfu-util ==

dfu-util can be used to read flash memory, write memory, and get information from the device.

This is the general command format to write an image file to a (predefined) "partition name" (referred to as ''altsetting'' in dfu-util help/manual) :

dfu-util -a ''altsetting'' -R -D ''file_name''

where: 
-a ''altsetting'' : Specify the altsetting of the DFU interface by name or by number 
-R : Issue USB Reset signalling once we're finished 
-D ''file_name'' : Write firmware from ''file_name'' into device

On Linux, you run dfu-util from a command shell prompt. If you have not put it somewhere on your command path you probably need to prefix it with a "./" like this '''./dfu-util'''.
On some systems you need to be root before this will work and on Ubuntu you must preface the command with "sudo" or you will get the following error: "Cannot claim interface: could not claim interface 2: Operation not permitted"

On Windows, you need to open a command window and run from a command line. Use Start-Run Program and type "cmd" to open a Window.

More detailed manual for dfu-util is available here : [[Dfu-util]]

== Flashing the Kernel ==

Note: The phone needs to be in the U-boot bootup menu for this to work.
Get there by holding down the aux button while powering up the device.

The command format is

dfu-util -a kernel -R -D ''/path/to/uImage''

When flashing succeeds the following will be shown:

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

Flashing may fail with an error -110. This indicates that the kernel is too big for the default kernel partition. uboot can be used to change the size of the default partitions on the device. It may also mean that you are trying to put the wrong thing in the kernel space.

== Flashing the Root Filesystem ==

The root filesystem has to be an image in jffs2 format. If the file you downloaded is zipped or compressed (has a .gz, bz2, .zip, tar, tar.gz or .tgz extension) you have to uncompress it first.

The command format is

dfu-util -a rootfs -R -D ''rootfs_filename.jffs2''

where ''rootfs_filename.jffs2'' is the name of the file containing the root filesystem.

When flashing succeeds the following will be shown:

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

== Flashing the boot loader to the NAND==

The boot loader (U-boot) file should have a .bin extension. As with the root filesystem, if the file you downloaded is zipped or compressed (has a .gz or .zip extension) you have to uncompress it first.

The command format is

dfu-util -a u-boot -R -D ''uboot.bin''

where ''uboot.bin'' is the name of the boot loader binary image file.

''Reminder'': You should have [[Flashing_the_Neo_FreeRunner#Boot_the_FreeRunner_from_NOR_Flash|boot from NOR first]], in order to flash the boot-loader in NAND. After flashing succesfully, make sure you reboot from NAND's newly flashed boot loader, to benefit from the updates.


(Optional) After an upgrade, you may wish to check that the u-boot version matches the one you have just flashed. You can use 'grep Bootloader /dev/mtdblock1' from a shell on the FreeRunner (and possibly the 1973 as well) to get the '''NAND''' u-boot version, like this:
root@om-gta02:~# grep Bootloader /dev/mtdblock1
Neo1973 Bootloader U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb

You can grep for the same string in /dev/mtdblock0 to retrieve the '''NOR''' u-boot version:
root@om-gta02:~# grep Bootloader /dev/mtdblock0
Neo1973 Bootloader U-Boot 1.3.2-moko12



== Reboot the FreeRunner from NAND ==

You should now be able to boot into the new images.

Pay attention '''to booting from the NAND flash this time''', in particular if you upgraded the boot-loader (in short: 1. press and hold ''power button'' down, and then 2. press ''aux button'')

The boot menu should be labelled '''*** BOOT MENU (NAND) ***''' this time (see [[Booting#Log_into_U-Boot_in_the_NAND_Flash|booting from NAND]] for more detailed instructions).

== A script to do all this from a nice GUI... ==

... is available, see [[NeoTool]]

== A command line script to simplify dfu-util ==

DFUScript developed to assist users who have multiple devices in using dfu-util via the command line. Information on where to download and use DFUScript can be found on [[DFUScript]]

[[Category:Flashing Openmoko| ]]

NeoTool

2008-09-17T13:45:32Z

Antisol: Created Page

=NeoTool=

NeoTool is a bash script which makes use of zenity to provide a friendly GUI frontend to some common management tasks. It is aimed at being very intuitive and easy to use, and flexible enough to make it usefull in a wide variety of circumstances.

== Features ==

The main features of NeoTool are:
* Ability to flash your Neo via a GUI
* Ability to flash multiple images at once (for example, flash rootfs and the kernel at the same time)
* Ability to backup your Neo via a GUI
* Ability to backup Multiple images at once
* rootfs can be backed up to either a flashable image or a tar archive
* most / all configuration can be done via the GUI

== Download / Releases ==

The most recent version of NeoTool is available for download at http://users.on.net/~antisol/neotool

When a new version is released it will be announced on the community mailing list, and on this page.

== Requirements ==

The software prerequisites for NeoTool should be installed on most modern linux systems by default:
* bash
* zenity
* which
* awk

* dfu-util is required to be able to flash your Neo, but NeoTool is able to download this automatically.

=== Optional ===

* pipe viewer (pv), shows display while backing up rootfs

* to backup rootfs, you need to have a [[USB_Networking|USB networking]] configured and working

* mkfs-jffs2 needs to be installed on your neo to backup rootfs to a flashable image (type 'opkg install mkfs-jffs2' in ssh)

* While not a requirement, backing up rootfs is much less painful if you set up an authorized_keys entry for your host on your Neo. To do this, run 'ssh-keygen' (preferrably as root) on your host, and then copy the contents of ~/.ssh/id_rsa.pub on your host into /home/root/.ssh/authorized_keys on your freerunner

<pre>
user@host# su

root@host# ssh-keygen

root@host# scp ~/.ssh/id_rsa.pub root@<Neo IP Address>:/home/root

root@host# ssh root#<Neo IP Address>
root@om-gta02:~# cat id_rsa.pub >> /home/root/.ssh/authorized_keys

</pre>

This will prevent you from having to enter the password for your Neo when you use ssh and scp.

If you don't do this, you will need to enter your password repeatedly in order to backup rootfs.

== Usage ==

NeoTool should usually be run as root, although this is not required if you only want to backup rootfs and/or the kernel via scp.

<pre>sudo ./neotool</pre>

You will initially be presented with the main menu. Most of the functions should be relatively self-explanatory

(thorough documentation on usage goes here)

== Revision History ==

See [http://lists.openmoko.org/pipermail/community/2008-September/029731.html this thread] and [http://lists.openmoko.org/pipermail/community/2008-September/030257.html that update] for discussions on the community list.

=== 09-Sep-2008 ===

- ability to flash more than one image at once - the 'what do you wanna
flash' now has checkboxes instead of radio buttons, and all your
selections are flashed one after the other. (which i find very handy,
stops the FR powering down while you're typing the next dfu-util
command, or locating the next image - works great for flashing a new
distro & kernel). if an error occurs, subsequent files will not be flashed.

- more confirmation / idiot-proofing - it now tells you what you're
doing much more clearly (i.e: "about to flash Kernel with /foo/bar.bin,
rootfs with /foo/bar.jffs". allows you to confirm that you chose the
right images). also the 'choose file' dialogs tell you what you're
browsing for

- ability for users to press 'cancel' at the various dialogs and exit
gracefully.

- checks that dfu-util exists and is executable. I moved my dfu-util to
/usr/local/bin, so it looks there first, but it will also check the
current directory and prompt if it can't find it

- I wasn't a fan of patching dfu-util, and the pulsating zenity progress
dialog drags my (prehistoric) PC to a crawl, so I disabled the progress
bar and use the text output of dfu-util instead.

=== 12-Sep-2008 (v1.0) ===

- Utility now has the ability to flash the splash image as per request

- Utility can now also backup your device to flashable rootfs / kernel images (david might like this for building FDOM images)

- Configurification is loaded on startup and saved in /etc/frutil (you can only modify settings if you run it as root)

- more idiot proofing - uses 'which' to find dfu-util, checks to ensure it's being run as root, checks that zenity is installed on the host, checks that you have mkfs.jffs2 installed before backing up, checks that you have pv installed and acts accordingly (by either using it or not during the backup [this is not properly tested because I don't have pv, please report]), and possibly other stuff I've forgotten about.

- new name (frutil) to reflect the new abilities

=== 17-Sep-2008 (v1.1) ===

- Added ChangeLog

- Added ability to handle multiple DFU-capable devices

- Changed references to 'freerunner' to 'neo'

- name changed to NeoTool (despite implied connection with Keanu Reeves' crotch)

- Added 'Reset to defaults' option

- Added warning that flashing uboot on neo1973 may result in a paperweight

- several small bugfixes

- made backup functionality much more versatile:

- made backup filenames configurable

- Added ability to choose what to backup

- Added rootfs backup type option (jffs2 or tar)

- Added kernel backup method option (scp or dfu)

- Added ability to backup uboot and splash

== Support ==

Suggestions? comments? feedback? problems?
* Are all welcome
* Email the Community list,
* or, email antisol (at) internode (dot) on (dot) net

<strike>NeoTool is perfect in every respect - if it breaks it's because you did something wrong.</strike>

Toolchain

2008-08-04T10:25:55Z

Antisol: /* Prerequisites */

{{Languages|Toolchain}}

= Introduction =

A toolchain is a set of tools that allows you to compile code. For Openmoko, we have to differentiate between the following use-cases:

== Developing a single application ==

For this, you should use a prebuilt toolchain from the Openmoko project. Here you can find a recipe to get started with this toolchain leading you through a series of steps to compile a project and run it on your target device. You might have heard about [[OpenEmbedded]], however as an application programmer, you should '''not''' be using [[OpenEmbedded]].

== System Integration and customizing a distribution ==

For this task, you should use [[OpenEmbedded]] which builds its own cross compiler during the bootstrapping/build process. System Integration and customizing a distribution is out of scope of this page.

=Basic toolchain usage=

==Prerequisites==

You should be reasonably familiar with Linux and its command line tools, have an x86-compatible computer with at least 1G of free disk space. You should have experience with compiling programs from source using your local compiler. The remainder of this document will also assume you have write access in your home directory (~) and <tt>/usr/local/</tt> (becoming root if needed). If any of this is not the case, please call your local administrator for help.

Last but not least you should have a working setup that allows you to compile native software packages using the autotools build system (the triade of '''./configure, make, make install''').

A (partial) list of required packages -- please append as necessary:

* For most Linux version you might only need to install the packages
** autoconf, automake
** binutils, gcc, gcc-c++
** libtool
** ccache
** intltool

* For Ubuntu 8.04 ( Previous versions don't support libmokoui2 ) the following is required:
sudo apt-get install gcc g++ autoconf automake binutils libtool libglib2.0-dev \
ccache libxrender-dev intltool libmokoui2-dev libgconf2-dev mtools

* For Fedora-Core the following is required, while logged in as <tt>root</tt>:
yum install gcc gcc-c++ autoconf automake binutils libtool glib2-devel \
ccache libXrender-devel intltool GConf2-devel mtools gettext-devel
Fedora-Core does not appear to have <tt>libmokoui2</tt> available.

==Downloading and installing==

{{Note|Debian and Ubuntu i386 users (or others who can install a .deb) may wish to skip the below and instead use:
[http://andreasdalsgaard.blogspot.com/2008/07/openmoko-development-in-5-minutes.html Openmoko application development in 5 minutes] by Andreas Dalsgaard.}}

The prebuilt toolchain can be downloaded from [http://downloads.openmoko.org/toolchains downloads.openmoko.org]:

* Creating a destination directory can be anywhere, but for example:

mkdir ~/sources
cd ~/sources

* Depending on your CPU type (x86_64 or i686) download the proper package:

wget http://downloads.openmoko.org/toolchains/openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.bz2
or
wget http://downloads.openmoko.org/toolchains/openmoko-i686-arm-linux-gnueabi-toolchain.tar.bz2

{{Note|Several people have had problems with the latest toolchain built 20080521. If you experience errors, try an older version. (as of July 23, 2008)}}

Next, you want to extract it on your filesystem. This toolchain is ''not'' relocatable, it needs to be installed into <tt>/usr/local/openmoko/</tt>.
Now you have the following options:

* Extract it directly as root, so use command "su" first (or prefix the tar command with "sudo" when you are using Debian/Ubuntu):

cd /
tar -xjvf ~/sources/openmoko-XYZ-arm-linux-gnueabi-toolchain.tar.bz2

* On Debian-based systems, you can use alien(+fakeroot) to create an easy-to-uninstall package from this .tar.bz2:

bunzip2 openmoko-*-arm-linux-gnueabi-toolchain.tar.bz2
gzip openmoko-*-arm-linux-gnueabi-toolchain.tar
fakeroot alien -d openmoko-*-arm-linux-gnueabi-toolchain.tar.gz
sudo dpkg -i openmoko_*-arm-linux-gnueabi-toolchain*.deb

* The prebuilt toolchain is for x86_64 or i686. If you wanted, you could build it on your own with OE:

bitbake meta-toolchain-openmoko

Finally, everytime you want to use this toolchain, you need to alter some environment variables, so that your tools will be found. The toolchain provides a script to do that, so the only thing you need to do is to source it.
Note that if you are not using a "sh" or "bash" shell (check with "echo $SHELL") that you need
to start "sh" or "bash" first.

. /usr/local/openmoko/arm/setup-env

* At least, you should add /usr/local/openmoko/arm/bin to your $PATH variable, otherwise the next steps won't work (om-conf and make).

==Building OpenMoko Kernel from git repo using Toolchain==

git clone git://git.openmoko.org/git/kernel.git linux-2.6
cd linux-2.6
git checkout origin/stable
cp defconfig-gta02 .config
./build

Will fail with error message "arm-angstrom-linux-gnueabi-ld: unrecognized option '-Wl,-rpath-link,/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/lib'" until /usr/local/openmoko/arm/setup-env is modified. LDFLAGS should be changed from:

export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-rpath-link,${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-O1"

to:

export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -rpath-link ${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -O1"

==Building a sample project==

In a chosen destination directory (in this example ~/):

* copy the downloaded sample application source:

cp -r /usr/local/openmoko/source/openmoko-sample2 ~/

* Remember to set the proper environment variables (again with "sh" or "bash") for openmoko:

. /usr/local/openmoko/arm/setup-env

* You need to create a build configuration for this application. This also checks if all needed libraries, tools, etc.. is available on your system. If this fails see the notes about the needed packages in the section "Prerequisites" mentioned earlier.

om-conf openmoko-sample2

* Optionally now you can modify the source code in openmoko-sample2/src. Before the next step, go into the sample directory.

cd openmoko-sample2

* If you are using an older version of the toolchain, you may have to create the makefile by running "./autogen.sh". Otherwise, to build the application from the source code just type:

make

* If there are errors (i.e. "You need to install gnome-common from the GNOME CVS") deal with them. Also see "Troubleshooting" section at the end of this page for known issues.

If you want to install this project on host for staging usage later, a shared library, for example, you can do the following to install it into a given configured prefix.
om-conf --prefix=/usr/local/openmoko openmoko-sample2
cd openmoko-sample2
make install

==How to modify the sample project==

In order to build your own project by using openmoko-sample2 files, some changes are needed:

* copy the downloaded sample application source

cp -r /usr/local/openmoko/source/openmoko-sample2 ~/

* rename the folder with the name of your project (in this example your-project-name) and delete old sample files

mv openmoko-sample2 your-project-name
cd your-project-name
cd src
rm *.c

* copy your sources (in this example your-sources) into src/

cp your-sources .
cd ..

* now in the main folder modify autogen.sh by updating the following lines

PKG_NAME="your-project-name"

* modify configure.ac by updating the following lines ('main.c' should be the main file in your project)

AC_INIT(your-project-name, 0.0.1, http://www.openmoko.org/)
AC_CONFIG_SRCDIR(src/main.c)

* go into data/ folder and rename these files with the name of your project

cd data
mv openmoko-sample.png your-project-name.png
mv openmoko-sample.desktop your-project-name.desktop

* modify Makefile.am inside data/ by updating the following lines

dist_desktop_DATA = your-project-name.desktop
dist_appicon_DATA = your-project-name.png

* modify Makefile.in inside data/ by updating the following lines

dist_desktop_DATA = your-project-name.desktop
dist_appicon_DATA = your-project-name.png

* modify your-project-name.desktop by updating the following lines

Name=your-project-name
Encoding=UTF-8
Version=0.0.1
Type=Application
Exec=your-project-name

* and by adding the following line

Icon=your-project-name

* move into src/ folder

cd ..
cd src

* modify Makefile.am by updating the following lines

bin_PROGRAMS = your-project-name
your_project_name_SOURCES = \
main.c
your_project_name_LDADD = @DEPENDENCIES_LIBS@

* be sure to put instead of main.c all your .c and .h files and modify all the '-' characters with '_' in the variable names

==Packaging your application==

We have included a script to make an ipkg out of your application. Note that this is not needed to test your application on the Neo (for that you can just scp the resulting binary and data over), however it's very handy if you want to distribute your application to others.

om-make-ipkg openmoko-sample2

Now you got openmoko-sample2_0.1_armv4t.ipk , you can `scp' it to your
Neo and install it:

scp openmoko-sample2_0.1_armv4t.ipk root@192.168.0.202:
ssh root@192.168.0.202 opkg install openmoko-sample2_0.1_armv4t.ipk

Note that while you can redistribute the generated ipkg, be aware that this is a bare-bones ipk that contains no further information, i.e. you will lack library dependencies. See below how to fix this.

You can also supply the version number, a description, and an author / contacts string in a control file:

om-make-ipkg myapp myapp_control

A template of myapp_control:

Package: $appname
Version: 0.1
Description: package built by openmoko toolchain
Section: openmoko/applications
Priority: optional
Maintainer: $USER
Architecture: armv4t
Homepage: http://www.openmoko.org/
Depends:
Source: ${SRC}

==Where to go from here==

Using the external toolchain is an easy way to build applications for your Neo. If you are familiar with this procedure, you might also want to look into
* Using [[Qemu]] to test your applications in an emulated environment
** Ubuntu users might prefer to look at [[Automatic_emulation_in_Ubuntu]]
* Using [[Host-based_development_with_Xoo_and_Xephyr|host-based development]] to improve your efficiency
* Using [[OpenEmbedded]] to customize your Openmoko distribution image

=Advanced topics=
==Using toolchain provided libraries==
Add the necessary libraries to the _LDADD field in src/Makefile.am, for example:
openmoko_sample2_LDADD = @DEPENDENCIES_LIBS@ -lmokogsmd2

make sure to run om-conf again after this.

==Installing additional libraries into the toolchain==

Sooner or later you will want to compile an application that has dependencies which can't be fulfilled by the precompiled toolchain, e.g. some obscure libraries.

In that case, feel free to request the inclusion of additional libraries into the next release of the OpenMoko toolchain. Until then, here is how you enhance your already installed toolchain. Say, we want to add the library called liburiparse:

cd ~/source
wget http://downloads.sourceforge.net/uriparser/uriparser-0.6.0.tar.bz2
./configure --host=arm-angstrom-linux-gnueabi \
--prefix=/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr
make
make install

That's it.

==Getting your application packaged by OE==

If you have written a cool application which you want to share with others, the best way to do that is to

# upload your application source code to a public location
# submit a [[BitBake]] recipe to [[OpenEmbedded]], preferably via the [http://bugzilla.openembedded.org OpenEmbedded bugtracker].

See also [[Customizing the Openmoko Distribution]].

==Troubleshooting==

* Some Versions of the Toolchain have corrupt .la files. If you compile an application using the Toolchain and you receive a '/space/fic/openmoko-daily/neo1973/work/armv4t-angstrom-linux-gnueabi/pango-1.18.3-r0/pango-1.18.3/pango/libpangoft2-1.0.la' error, you are affected. To fix that you should go to your "/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib" directory and open the affected .la files and change "/space/fic..." to "/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib". You have to fix more than one .la file. For the pango error you have to change "libpangocairo-1.0.la", but there are more corrupt .la files.

Attached is a beta fix for the .la problem. Untar the .tar.bz2 as root, and execute the following bash script as root:

#!/bin/sh
DIR=/usr/local/openmoko/arm
for la in `find $DIR -iname \*.la`; do
dependency_libs=
. $la
for lib in $dependency_libs ; do
delib=`echo $lib | grep -E .la$`
if [ -z $delib ] ; then
echo -n
elif [ -f $delib ]; then
echo -n
else
basedelib=`basename $delib`
replacedelibs=`find $DIR -iname $basedelib`
found=0
for replacedelib in $replacedelibs ; do
if [ $replacedelib == $delib ]; then
found=1
fi
done
if [ $found -gt 0 ] ; then
echo -n
else
sed_delib=`echo $delib | sed 's/\//\\\\\//g'`
sed_replacedelib=`echo $replacedelib | sed 's/\//\\\\\//g'`
# A bit slow, we could chain expressions for speed. :)
cp $la $la.old
cat $la | sed "s/$sed_delib/$sed_replacedelib/g" > $la.new
mv $la.new $la
rm $la.old
fi
fi
done
done

* Please use the [http://lists.openmoko.org/mailman/listinfo/openmoko-devel Openmoko-Devel] mailing list.

[[Category:Application Developer]]

USB Networking

2008-07-31T16:39:51Z

Antisol: /* Option A - Tested with FC8 */

= OpenMoko Networking Setup =

In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).

Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.

= DNS =

In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.

= Linux Kernel Support =

Your Linux desktop/laptop needs to have suitable support, in particular, you will need to have enabled full masquerading in the kernel and USB networking options:

* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER

Both USB networking options are available in the ''Device Drivers -> USB support -> USB Network Adapters'' or ''Device Drivers -> Network Device Support -> USB Network Adapters -> Multipurpose USB Networking Framework''. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

It can be complex to set all the correct options for masquerading in the kernel if they are not turned on. This could be detailed further.

= Simple Manual Linux Configuration =

Try this first. If it works, then you can add permanent configuration or use more sophisticated setups below:

(as root on your host machine):

iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ifconfig usb0 192.168.0.200

If your Internet connection is also in the range 192.168.0.x then instead you might want to use:

ifconfig usb0 192.168.0.200 netmask 255.255.255.248

Then (ideally, not as root):

ssh root@192.168.0.202

== Testing Your Connection ==

Log in with a blank password (press enter). Now, make sure you can ping back to your desktop:

ping 192.168.0.200

This tests the basic network connection.

(Note that some systems like Vista, don't respond to ICMP ping by default)

Or your router, for example (your IP will probably be different):

ping 192.168.1.99

Or to a Google IP:

ping 74.125.19.147

This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

== Configure DNS ==

Note that step won't help much if you don't have connectivity above. DNS is configured in /etc/resolv.conf. It should contain:

nameserver 192.168.0.200

Which means that by default it expects your desktop to have a DNS server. On some Linux and Windows systems this is true, especially those configured as servers, but in general it is not. You can install packages such as ''bind9'' or ''dnsmasq''. See the section below on [[USB Networking#More on DNS|More on DNS]] for other solutions.

Test if it works:

ping www.google.com

If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.

== Firewall Issues ==

On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.

= Make it Permanent =

Based up [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] by Marcin 'Hrw' Juszkiewicz.

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
</pre>

This is more sophisticated than the manual setup. The allow-hotplug stanza ties into Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner's is connected via USB, this is run.

In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.

=== Ubuntu Issues ===

Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437

One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:

SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

# Bring devices up and down only if they're marked auto.
# Use start-stop-daemon so we don't wait on dhcp
ACTION=="add", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}"

LABEL="net_end"

ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"

The bug is that the LABEL="net_end" is at the wrong position

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)

== Mandriva ==

Tested with Mandriva 2008.1. The idea here is that we will carve out a small (8 hosts) subnet from the main subnet. So our netmask will be 255.255.255.252

This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured.

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.252
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes

This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)

/etc/sysconfig/network-scripts/usb0-routes:

ADDRESS0=192.168.0.200
NETMASK0=255.255.255.252

Now we need to restart the network system to pick up the changes.

service network restart

== SuSE ==

/etc/sysconfig/network/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].

== Fedora ==

=== Option A - Tested with FC8 & FC5 ===

/etc/sysconfig/network-scripts/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
# from http://www.handhelds.org/moin/moin.cgi/UsbNet
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes

=== Option B ===

This setup is probably over-complex:

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

/etc/sysconfig/network-scripts/ifup-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/ip addr flush dev ${DEVICE} 2>/dev/null
/sbin/ip link set dev ${DEVICE} up
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}

/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/sysctl net.ipv4.ip_forward=1
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT

Set /etc/sysconfig/network-scripts/ifdown-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/sysctl net.ipv4.ip_forward=0
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}

/sbin/ip link set dev ${DEVICE} down
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null

If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.

/sbin/service NetworkManager restart

== Red Hat or Similar (tested with Workstation 5) ==

Edit /etc/sysconfig/network-scripts/net.hotplug:

After this command:

<pre>
case $INTERFACE in
# interfaces that are registered after being "up" (?)
</pre>

add

<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
echo 1 > /proc/sys/net/ipv4/ip_forward
exit 0
;;
</pre>

== Gentoo ==

Open /etc/conf.d/net and add:

# Neo
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )

Create a new init script:

cd /etc/init.d
ln -s net.lo net.usb0

Put iptables into use:

iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24

Store them:

/etc/init.d/iptables save

If you want the routing by default:

rc-update add iptables default

You must also inform the kernel, to start forwarding.

echo 1 > /proc/sys/net/ipv4/ip_forward

One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.

preup() {
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

postdown() {
echo 0 > /proc/sys/net/ipv4/ip_forward
iptables -D INPUT -s 192.168.0.202 -j ACCEPT
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

== MacOS X ==
See the [[MacOS_X#USB_Networking|USB Networking section in the MacOS X article]].

== Windows ==
See the [[Neo1973_and_Windows#USB_Ethernet_emulation|USB Ethernet emulation section in the Neo1973 and Windows]] article.

= More on DNS =

== Hostnames ==

Instead of using the IP address, instead enter in your desktop's /etc/hosts:

192.168.0.202 openmoko

Then instead type:

ssh root@openmoko

== DNS proxying ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you). There are a number of ways to do this:

=== Proxying with dnrd ===

The script is designed to use [http://dnrd.sourceforge.net/ dnrd] as the DNS proxy. The [http://buildhost.automated.it/gta01 script] and a copy of [http://buildhost.automated.it/dnrd-2.20.3.tar.gz dnrd] are available. The script also performs the initial setup of the connection as per the [[USB_Networking#Manual_method]] above.

=== Proxying with a UDP forwarder ===

Another easy setup is using a UDP forwarder like the one from http://www.tapor.com/udpf/ - use it with the command"

udpf-elf -p=53-f=`cat /etc/resolv.conf|awk '$1 == "nameserver"{print $2; exit(0);}'`:53

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1

Where <tt>192.168.0.1</tt> is the IP of your router.

= SSH Extras =

Reportedly, the ssh daemon (dropbear 0.49) on the FreeRunner appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

To avoid ssh added a new line for every ssh host-key to you known_hosts you can add the following to the phone section in ~/.ssh/config

UserKnownHostsFile /dev/null

You might want to use keys to bypass the login prompt too.

== SSH Keys ==

== From desktop to FreeRunner ==

To generate ssh keys for use as a login mechanism type:

ssh-keygen -t rsa

When prompted for a password either hit enter for no password (''not really a good idea'') or enter a password for this key. ssh into the phone and create ~/.ssh:

# mkdir ~/.ssh

Then from your desktop copy the '''.pub''' file to the phone.

# scp ~/.ssh/id_rsa.pub phone:.ssh/authorized_keys

You should now be able to ssh directly into the phone without a password prompt.

To disable password logins ('''after setting up key access''') edit /etc/init.d/dropbear and change the following line:

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

You will need to restart dropbear for this to take effect.

=== From FreeRunner to Desktop ===

Generate the key:

dropbearkey -t rsa -f id_rsa

The output will look something like this:

Will output 1024 bit rsa secret key to 'id_rsa'
Generating key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3Nza[...]
Fingerprint: md5 ca:e8:f0:b7:f6:7b:c2:b6:b9:71:e4:45:86:a9:ff:b8

Copy and paste the one line (in this example, starting with 'ssh-rsa' onto the end of the host's authorized_keys file (often in ~/.ssh/).

From the phone, ssh with -i:

ssh -i id_rsa user@host

=== Changing host keys ===

If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:

Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root

This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts).

== GUI on desktop through SSH ==

To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows:

ssh -l root -X -v 192.168.0.202

Using this, run openmoko-finger-demo for example, and it will open up on the desktop. To get landscape view, just resize the GUI window on the desktop.

If you get an error like this:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.
you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the Freerunner before launching the process from your desktop. You can find the value of this variable by using a command such as
ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS
Note that you must run that command on the Freerunner. Back on your desktop, run the process you want with the ''env'' command like this:
env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process''

==Display Remote Applications on FreeRunner==

To get desktop apps to show up on your FreeRunner, first log in:

ssh -l root 192.168.0.202

Then run:

DISPLAY=:0 xhost +192.168.0.200

After this you can close the ssh session. Back on the desktop computer, run:

DISPLAY=openmoko:0 xclock

Note that the xhost command will allow remote applications on 192.168.0.200 to access the X server. It will allow anyone on the desktop machine to access the X server of the neo, including snooping anything you type on it. To disallow remote applications again, run this in the neo:

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:USB]]
[[Category:Hardware]]
[[Category:Implemented]]

Import Vcf Contacts

2008-07-31T16:31:10Z

Antisol: /* Exporting from Outlook / ActiveSync */

== Import for 2007.2 ==
=== Basic Information ===

Neo FreeRunner uses Evolution data server (eds) to save contacts.
However, the specific version used differs from what is probably used on your desktop (if you have Evolution installed).

You ''cannot'' copy your addressbook.db from your desktop to Neo ([http://docs.openmoko.org/trac/ticket/1119 bug 1119]).

=== Import and Manage Scripts ===

If you want to import your old contacts to the Neo you could use this script:

[http://www.smurfy.de/files/neo/manage-contacts Manage Contacts script] [http://www.placard.fr.eu.org/~roland/tmp/manage-contacts.py mirror]

If you first want to remove all existing contacts you could use this script.

[http://www.smurfy.de/files/neo/remove_all_contacts remove all script]

If you have all contacts in seperate vcf files and just want to import all at once:

[http://www.smurfy.de/files/neo/ac Simple script]

[http://www.smurfy.de/files/neo/import_contacts Simple script for one big contactsfile]

(please add a .py after the filename, sorry my hoster gives an error if i link to .py files, even .py.txt)

In the simple scripts you need to add the following lines
ps = os.popen ('ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS')
l = ps.read ()
r = re.compile ('DBUS_SESSION_BUS_ADDRESS=(\S+)')
m = r.search (l)
a = m.expand ('\\1')
os.environ ['DBUS_SESSION_BUS_ADDRESS'] = a

=== Exporting old contacts to VCard format ===

To use the manage Script you need your Contacts in VCF format.

# on nokia phones i used the nokia phone manager (long time ago)
# on windows mobile phones you could use active sync to sync with Outlook and then use a Outlook export plugin to export as vcf
# on lg phones the backup function to memory card creates one file with multiple VCards.

=== Exporting from Outlook / ActiveSync to VCF ===

Doing a quick google I was unable to find a free export plugin for outlook (they all seem to want between $19.95 and $49), so I put together some quick-and-dirty VB code to do it. To use it, Open Outlook, then open the VB editor by pressing ALT-F11, Insert a module, and paste in the following. Change "Z:\OpenMoko\contacts" to wherever you want your vcf files saved (should be an existing, empty directory), and press F5 to run it.

'''Code:'''

<pre>

Sub ExportContactsToVCF()

'Cheap and nasty way to export All Contacts to VCF files.
'By Dale Maggee, antisol (at) earthling (dot) net

Dim CN As ContactItem
Dim NS As NameSpace
Dim Fld As MAPIFolder

Set NS = Application.GetNamespace("MAPI")
Set Fld = NS.GetDefaultFolder(olFolderContacts)

For Each CN In Fld.Items
Debug.Print CN.FullName
CN.SaveAs "z:\OpenMoko\contacts\" & CN.FullName & ".vcf", olVCard
Next CN

MsgBox "Done!"

End Sub
</pre>

voila! you now have multiple VCF files in whatever directory you chose, suitable to be imported by the python script below.

=== Usage ===

The script is for the 2007.2 Version (default install on Neo FreeRunner), not for Qtopia

You need Python to use this script so do a

opkg install python-dbus

to install python and the python dbus module

==== Manage Contacts Script ====

'''This script needs all contacts in one big file'''

'''You also could run this script on a ssh session!'''

# Copy your big contacts file (contacts.txt) to your Neo
# Copy script to your Neo
# Connect via ssh to your Neo
# Fix special chars in your contacts file with you favorite text editor
# To import the file run on the SSH shell:

python manage-contacts.py load < contacts.txt

# For a backup your existing contacts on the Neo

python manage-contacts.py dump > contacts.txt

==== Simple Script ====

'''You must run the script in the OM Terminal, not over ssh'''

The script does a listdir and imports ALL files it found in that dir. (i'm a bad python programmer)

# Copy all vcf files to a separate directory on my freerunner
# Copy the ac script to the parent directory also on my freerunner
# Have the contacts program running (so you have eds running too)
# Go to the terminal on the freerunner and type in the vcf directory: "python ../ac" (root@om-gta02:~/vcf# python ../ac)
## Note: '''You must call the script in the OM terminal''' not via Bluetooth or USB or you get a dbus error.
# Done :D

==== Troubleshooting ====
* Make sure you have python and python-dbus installed
* Make sure you have no illegal chars (utf) in the filename and inside the vcf files. (I had problems with Ü,Ä etc)
** The characters seem to work if you convert them from =C3=A4 type of format to proper UTF-8, and the vcards also specify UTF-8 charset. you cannot use other charsets besides UTF-8 since they are delivered via DBus which does not allow others.
* Only vcf files should be in your current directory so do a ../ac.
* You must call the script in the OM terminal not via Bluetooth or USB. If you do so a dbus error occur

=== Authors ===
* Simple script by smurfy - phil <openmoko at smurfy.de>
* Manage Contacts script by Roland Mas <lolando at debian.org>
* Remove all Contacts script / simple script for one big file by Andreas Dalsgaard <andreas.dalsgaard at gmail.com>

Thanks to [[Import_Sim_Contacts]] for the original Python Script.

== Import for ASU/Qtopia ==
The Qtopia addressbook application suports import of VCF files out of the box:
LD_LIBRARY_PATH=/opt/Qtopia/lib /opt/Qtopia/bin/addressbook /home/root/addressbook.vcf

You will be asked if you want to import the contacts form addressbook.vcf (the contact name will be taken from the "N:" vCard field).

[[category:Openmoko]]
[[category:Documentation]]

Import Vcf Contacts

2008-07-31T16:29:28Z

Antisol: /* Exporting old contacts to VCard format */

== Import for 2007.2 ==
=== Basic Information ===

Neo FreeRunner uses Evolution data server (eds) to save contacts.
However, the specific version used differs from what is probably used on your desktop (if you have Evolution installed).

You ''cannot'' copy your addressbook.db from your desktop to Neo ([http://docs.openmoko.org/trac/ticket/1119 bug 1119]).

=== Import and Manage Scripts ===

If you want to import your old contacts to the Neo you could use this script:

[http://www.smurfy.de/files/neo/manage-contacts Manage Contacts script] [http://www.placard.fr.eu.org/~roland/tmp/manage-contacts.py mirror]

If you first want to remove all existing contacts you could use this script.

[http://www.smurfy.de/files/neo/remove_all_contacts remove all script]

If you have all contacts in seperate vcf files and just want to import all at once:

[http://www.smurfy.de/files/neo/ac Simple script]

[http://www.smurfy.de/files/neo/import_contacts Simple script for one big contactsfile]

(please add a .py after the filename, sorry my hoster gives an error if i link to .py files, even .py.txt)

In the simple scripts you need to add the following lines
ps = os.popen ('ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS')
l = ps.read ()
r = re.compile ('DBUS_SESSION_BUS_ADDRESS=(\S+)')
m = r.search (l)
a = m.expand ('\\1')
os.environ ['DBUS_SESSION_BUS_ADDRESS'] = a

=== Exporting old contacts to VCard format ===

To use the manage Script you need your Contacts in VCF format.

# on nokia phones i used the nokia phone manager (long time ago)
# on windows mobile phones you could use active sync to sync with Outlook and then use a Outlook export plugin to export as vcf
# on lg phones the backup function to memory card creates one file with multiple VCards.

=== Exporting from Outlook / ActiveSync ===

Doing a quick google I was unable to find a free export plugin for outlook (they all seem to want between $19.95 and $49), so I put together some quick-and-dirty VB code to do it. To use it, Open Outlook, then open the VB editor by pressing ALT-F11, Insert a module, and paste in the following. Change "Z:\OpenMoko\contacts" to wherever you want your vcf files saved (should be an existing, empty directory), and press F5 to run it.

'''Code:'''

<pre>

Sub ExportContactsToVCF()

'Cheap and nasty way to export All Contacts to VCF files.
'By Dale Maggee, antisol (at) earthling (dot) net

Dim CN As ContactItem
Dim NS As NameSpace
Dim Fld As MAPIFolder

Set NS = Application.GetNamespace("MAPI")
Set Fld = NS.GetDefaultFolder(olFolderContacts)

For Each CN In Fld.Items
Debug.Print CN.FullName
CN.SaveAs "z:\OpenMoko\contacts\" & CN.FullName & ".vcf", olVCard
Next CN

MsgBox "Done!"

End Sub
</pre>

voila! you now have multiple VCF files in whatever directory you chose, suitable to be imported by the python script below.

=== Usage ===

The script is for the 2007.2 Version (default install on Neo FreeRunner), not for Qtopia

You need Python to use this script so do a

opkg install python-dbus

to install python and the python dbus module

==== Manage Contacts Script ====

'''This script needs all contacts in one big file'''

'''You also could run this script on a ssh session!'''

# Copy your big contacts file (contacts.txt) to your Neo
# Copy script to your Neo
# Connect via ssh to your Neo
# Fix special chars in your contacts file with you favorite text editor
# To import the file run on the SSH shell:

python manage-contacts.py load < contacts.txt

# For a backup your existing contacts on the Neo

python manage-contacts.py dump > contacts.txt

==== Simple Script ====

'''You must run the script in the OM Terminal, not over ssh'''

The script does a listdir and imports ALL files it found in that dir. (i'm a bad python programmer)

# Copy all vcf files to a separate directory on my freerunner
# Copy the ac script to the parent directory also on my freerunner
# Have the contacts program running (so you have eds running too)
# Go to the terminal on the freerunner and type in the vcf directory: "python ../ac" (root@om-gta02:~/vcf# python ../ac)
## Note: '''You must call the script in the OM terminal''' not via Bluetooth or USB or you get a dbus error.
# Done :D

==== Troubleshooting ====
* Make sure you have python and python-dbus installed
* Make sure you have no illegal chars (utf) in the filename and inside the vcf files. (I had problems with Ü,Ä etc)
** The characters seem to work if you convert them from =C3=A4 type of format to proper UTF-8, and the vcards also specify UTF-8 charset. you cannot use other charsets besides UTF-8 since they are delivered via DBus which does not allow others.
* Only vcf files should be in your current directory so do a ../ac.
* You must call the script in the OM terminal not via Bluetooth or USB. If you do so a dbus error occur

=== Authors ===
* Simple script by smurfy - phil <openmoko at smurfy.de>
* Manage Contacts script by Roland Mas <lolando at debian.org>
* Remove all Contacts script / simple script for one big file by Andreas Dalsgaard <andreas.dalsgaard at gmail.com>

Thanks to [[Import_Sim_Contacts]] for the original Python Script.

== Import for ASU/Qtopia ==
The Qtopia addressbook application suports import of VCF files out of the box:
LD_LIBRARY_PATH=/opt/Qtopia/lib /opt/Qtopia/bin/addressbook /home/root/addressbook.vcf

You will be asked if you want to import the contacts form addressbook.vcf (the contact name will be taken from the "N:" vCard field).

[[category:Openmoko]]
[[category:Documentation]]

User:Antisol

2008-07-04T09:33:13Z

Antisol: New page: * Semi-Recently converted Open Source evangelist from Melbourne, AU. * Windows programmer of sorts (VB / Delphi mostly) * Not a kernel hacker by any means, or even a (good) shell-scripte...

* Semi-Recently converted Open Source evangelist from Melbourne, AU.

* Windows programmer of sorts (VB / Delphi mostly)

* Not a kernel hacker by any means, or even a (good) shell-scripter, but not afraid to compile a program or follow a HOWTO.

Openmoko Local Groups: Melbourne

2008-07-04T09:26:40Z

Antisol:

Welcome to the Melbourne Openmoko usergroup.

{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
|-
|[[User:KellyV|Kelly Vlahovic]]
|Linux, C, PHP
|User and developer
|Hawthorn, Melbourne
|
|-
|[[User:Mcsporran|Johnny McKenzie ]]
| Linux, Networking
| User
| City, Melbourne
|
|-
|[[User:Antisol|Dale Maggee ]]
| Following HOWTOs
| User
| Scumsborough, Melbourne
|
|}
[[Category:Community]]
[[Category:Openmoko Local Groups]]

Wishlist/Accessories

2008-07-04T06:20:19Z

Antisol:

{{Hardware Wishlist}}
This is a page detailing accessories that may be of use for your Neo1973.

This is both accessories that do not exist, and existing devices that may be good to add to a web-store.

Advertising on this page is permitted, but keep it brief and factual.

=Existing devices=

==Storage Devices==

* '''Seagate's DAVE (Digital Audio Video Experience)''' with Bluetooth 2.0 WiFi 802.11b/g and USB-on-the-go-Interface (USB-OTG) http://www.seagate.com/docs/pdf/marketing/po_DAVE.pdf

==Input Devices==

===Pedometer===

There are (at least) two uses for a Bluetooth pedometer as a Neo1973 accessory:

* As an input device for exercise-monitoring software

* A pedometer combined with a compass (see [[Wish_List_-_Hardware#Digital_compass]]) would allow the positioning software to perform [http://en.wikipedia.org/wiki/Dead_reckoning dead reckoning] when the GPS signal has been lost. The US Army's [http://www.army-technology.com/projects/land_warrior/ Land Warrior system] already does this. (Maybe the pedometer is partly redundant with the accelerometers for dead reckoning tasks? See the [http://www.autospectator.com/modules/news/article.php?storyid=9942 SiRFDiRect announcement].)

=Wishlist=
==Special covers==
Different special covers could be made available with features like:
* A standard slip-on or clip-on template (possibly with buttons) to make the touch-screen blind accessible
* Small metal frame for protection (like Siemens M65, only with more style)
* Case with mirror on the back, for putting on makeup/checking appearance or helping with self-portraits with an integrated camera.
* Option to completely design printable case styles, perhaps with engraving. Ability to share these on a 'community' site.
* Solar powered recharger (perhaps as extendable/unfoldable [[Expansion Back]]).
* Rubber protection like available for iPod, of course in different colors and transparency.
* Underwater case. This could be a housing that fits around a normal Freerunner like the kinds for digital cameras. Alternatively, it could be an actual case that the Freerunner guts fits into.
* Screen Protector: A simple and very easy to produce screen protector, like the one on my iPaq:

Protector Flipped up image: http://www.pocketpcthoughts.com/images/ppct-ipaq6900-preview-small-01.jpg

Protector Flipped down image: http://www.pocketpcthoughts.com/images/ppct-ipaq6900-preview-small-06.jpg

This serves the dual purpose of protecting the screen from scratches, and stopping user's ear/face from accidentally pressing buttons while talking.

==Car kit==
A car kit with a cradle which simultaneously recharges the device.

==Bike kit==
Sporting a GPS, the phone would be ideal to have mounted by a bracket on the bike handle bars. Viewable from your position over the handlebars. Snap-on/snap-off, and some locking mechanism that actually keeps the phone from getting airborne on a hard break. Also, a basic spring on the bracket, making bumps softer on the phone. This type of bracket would cost peanuts to make.
Should also include a padded and waterproof pack that you can place the phone inside, keeping it (somewhat) safe from the elements.
Would also be really cool if it was possible to create a dynamo that can charge the phone, like old school bike headlights.
=== Cadence ===
Something to measure the Cadence like a normal bike computer would be great.
=== Heartbeat ===
Have the possibility to measure the heartbeat would make it a great accessory for training :)

==Charger conversion connector==
A flexible converter allowing you to recharge the Neo1973 with power from many DC sources such as other devices chargers.
Problems are that it may overload the DC source. It may require sensing of the input voltage, and reducing load if the voltage drops by a factor. Ideally the device should accept input voltage in the range of around 3.3v-28V in either polarity.

==Ability to connect a USB keyboard to the phones USB port==

It has a USB port. There are USB keyboards everywhere. It would be great to be able to ssh anywhere over wifi with a regular sized keyboard.

'''Portability'''

I think it should all be seen within the context of portability.
Have a keyboard incorporated, hinged along the long side, as noted elsewhere, with a micro-switch that induces hibernation on closing to conserve power.
Limit the touch screen function to different aspects of the file system and peripheral aspects - in other words, don't limit it to a phone.
Those of us on the go need a phone, yes, but a lot more.
And all of society is evolving in this direction, so the product needs to also to survive.

USB2 - obviously, could be employed for something like this:

[http://www.techpin.com/new-32gb-usb-flash-drives-from-corsair/]

on which an entire OS with a massive /home partition could be carried round on a keyring.

Why try to crowd it all onto one screen when all you have to do is make an alteration in the size of your belt mounted, carry pouch.

The world needs the portable office, not just the portable phone.

--

Weaver.

==Make the stylus laser-pen recharge its batteries from phone while "docked"==

The stylus pen with built in laser pointer and flashlight seemed too big to be able to be attached to the phone while it is not being used, according to the demonstration video. If that is the case, make a slot on the phone where one can "dock" the pen while not using it. Make the phone recharge the batteries in the pen while the pen is docked to the phone.

==USB laser pointer==

Make a laser pointer that plugs into the USB connector and controlled in the same through the same interface that that wold make the Freerunner a presentation remote control.

==Bluetooth earpiece with possible both-ears use==

It will be like a regular bluetooth speaker, but with another (wired or wireless) speaker in the other ear for music listening and telephony. The main, bulky piece with bluetooth could have a multi-purpose button: for answering calls when it whispers the name of the caller in my ears, or to raise/lower the volume of music or telephone call.

Would be nice to have them for the left-handed too.

==Make a VGA and/or DVI out connector==

The screen on the phone is small. But if it had a VGA out connector, we could connect an ordinary full sized monitor to it. It already has a USB connector. Imagine the coolness of attaching a usb keyboard and a 22" widescreen monitor to your ''phone'' and then viewing youtube videos through the phones wlan connection. You wouldn't have to carry around your laptop anymore since usb keyboards and vga monitors are availible practically everywhere.

This also may be used to show the conference presentations. There is enough memory in the phone to store the average presentation (the pdf or maybe even html formats could be used). Having the VGA port would transform it into very lightweight tool that could even replace a laptop for some people. It may be OK to have the same VGA resolution as presentations are usually prepared with the big fonts and figures.

== Pouch ==
The pouch could have external or internal place to keep the stylus.

== USB camera ==
A camera connected to the usb port.

[[Category:User]]
[[Category:Ideas| ]]
[[Category:Hardware ideas]]

Talk:Music Player

2008-06-29T08:25:39Z

Antisol: /* Features I'd like to see */ new section

([[User:ken]])
* Q:Does our media player support both audio and video files?
* Q:What kind of decoding library should be added?

([[User:Mickey]])

The S3C2410 is too slow to do video.
Audio-wise, we should limit support for the most popular formats which is
* mp3
* ogg
* wav.
We don't have an FM-Chip in the device, so I'm afraid we can't do .mid -- at least not in hardware. There are software MIDI players available, but I don't know whether this is interesting for us or not.

The S3C2410 is too slow to do fullscreen video.
It is able to do halfscreen video, with the LCD stretch mode enabled
See [[Video Player]]
--[[User:Speedevil|Speedevil]] 14:33, 18 February 2007 (CET)
<HR>

[Q]: At present, we will decide what kind of third party software for media player?

([[User:Sean|Sean Moss-Pultz]])
''What kind of third party software do you have in mind?''

([[user:Alex|Alex]]) ''What about RealPlayer? It has a linux version, but for mobile phone use, the performance should be taken into consideration.''

([[User:Sean|Sean Moss-Pultz]])
Unless we can't find a FOSS version, I would prefer not to use closed-source programs. Have a look at the follow:

[http://www.mplayerhq.hu/design7/news.html]
[http://www.videolan.org/vlc/]

We should check what OPIE and GPE use. [[User:Mickey]] Can you provide some feedback here?

([[user:Alex|Alex]]) GPE and OPIE both have their own media players.
*GPE's NMF[http://gpe.handhelds.org/projects/GPE-media.shtml] is based on GStreamer[http://www.gstreamer.net/]. NMF can play ogg and mp3 files.
*OPIE's opie-mediaplayer2[http://zaurus.logix.cz/ipkg/detail.xp?package=opie-mediaplayer2] It plays mp3, mpeg, wav, ogg, quicktime, divx and more. Also it is streaming capable.

<hr>

Q: In "Playback Mode" section it says "15) Panning -- realtime updated when panning wheel been rotated." The panning wheel isn't mentioned anywhere else. Is it another option for objects 5 and 6?
A: Looks like it, yeah. However I don't see the point for being able to do panning since the speakers are so close and point in the same direction, meaning that you probably won't be able to tell the differences panning would make. I'll have to check that on real hardware but unless it's noticable I'll leave panning out. Yes, it would also affect the headphones but I can't think of any situation where panning would be necessary with headphones so I don't see the point there either. If anyone does, please do tell :)
[[User:Abraxa|Abraxa]] 16:44, 18 April 2007 (CEST)

I would like a way to set balance, though I don't care much about realtime panning. My right ear is moderately less sensitive than my left, and I like to boost the volume on that ear, rather than on both ears, so I maintain some external hearing. (headphones only) --[[User:Speedevil|Speedevil]] 01:13, 20 April 2007 (CEST)

<HR>

Q: '''12) Repeat''' -- Repeats the current track. Is most player, repeat doesn't repeat the current track. It repeats the playlist (it starts playback from the beginning of the playlist after the last song in the list is played). Does this player's repeat do it differently than other players?

A: See question below
<HR>

Q: On the repeat button as well: I'd like to see a function where it repeats the current track once and then advances in the playlist afterwards. Maybe you could have the repeat button toggle its function with each tap - e.g. repeat all -> repeat current -> repeat current once -> repeat off -> ... [[User:Abraxa|Abraxa]] 01:51, 18 February 2007 (CET)

A: Since I'm writing the Music Player I'll just do it that way ;)
<hr>

Q: Is this Music Player a MPD-client (MPC)? That would be nice... However - all basic, "preloaded" software, should take speed into consideration...

A: I don't intend it to be as running MPD on the Neo seems like overkill to me and writing a separate application to act as some kind of remote control to a MPD server at home makes more sense in my opinion. [[User:Abraxa|Abraxa]] 16:09, 18 April 2007 (CEST)
<hr>

Q: What about Cover display ? For example browsing the music folder on the SD-Card by viewing the covers or displaying the cover while playing a song from it ? [[User:SrRaven|SrRaven]] 01:15, 19 April 2007 (CEST)

A: I might add this once the must-have features are working as this is something not everyone will make use of. [[User:Abraxa|Abraxa]] 01:29, 19 April 2007 (CEST)
<hr>

Q: Certainly not a must-have and therefore not high priority, but how about built-in support for queuing songs from an off-phone song repository (such as one's home computer). Thus if you get a hankering for a particular song that doesn't happen to be on the phone, you could pick it from a preloaded list. Assuming there is some network available, the player would start downloading on the background (meanwhile continuing with the local songs) and queue the request on arrival. On server-end, perchance a CGI script to recode songs on the fly to take up less bandwidth and space.

(No promises but I've half a mind to tinker with such a feature at some point if I find the time.) --[[User:Mjr|Mjr]] 01:46, 19 April 2007 (CEST)

<hr>

Q: Could there be a way to feed 'skip track' information to a script of some sort, so it can aggregate statistics, perhaps even going so far as cooperatively updating like/dislike data, line amazon. (yes, track ID is a fun problem).

A: Do you mean some kind of last.fm submit plugin? It's certainly possible, though the lack of persistent internet connection may be an issue. If that's not what you mean then please elaborate. [[User:Abraxa|Abraxa]] 17:34, 20 April 2007 (CEST)

R: I was more meaning simply throw 'user skipped track "Violent Femmes - Blister in the sun.mp3" at second 23/180' to a named pipe in ~/.music_player/output or something, and trying to read playlists from ~/.music_player/playlist, so that functionality can easily be added externally. Could be named pipe, external program called at appropriate times, or whatever. --[[User:Speedevil|Speedevil]] 11:32, 21 April 2007 (CEST)
<hr>

Q: Could there be a way to read playlists similarly?

A: Um... I'm afraid I don't understand what you mean... [[User:Abraxa|Abraxa]] 17:34, 20 April 2007 (CEST)

<hr>

Q: As you mentioned last.fm,I am a big last.fm fan and it annoys me that the tracks I played on the go don't get added at all.So how about a buffer that you than can just let it get uploaded once a wifi connection is established.Sometimes my last.fm plugin doesn't send tracks immediatly but caches them and submits them at some other time (reboot of media player) so that should not be a problem.So is that possible ? [[User:SrRaven|SrRaven]] 22:17, 20 April 2007 (CEST)

A: If there'll be such a feature this mechanism will definitely be part of it, yes. [[User:Abraxa|Abraxa]] 09:02, 21 April 2007 (CEST)

<hr>

Notice: [http://moc.daper.net/ mocp] is a console based music player : lightweight, very usable.
It could be interesting to write a shared library embedding the mocp features. This library would have the great advantage to be independent of the user interface.
--[[User:Gcasse|Gcasse]] 11:30, 25 June 2007 (CEST)

<hr>

Q: Should the Shuffle button be greyed out when shuffle is turned off? Usability guidelines suggest that options be grayed out only when they are unavailable; perhaps the Shuffle button should look normal when shuffle is turned off, and "active" when it is turned on.
--[[User:Cp.tar|Cp.tar]] 21:03, 5 February 2008 (CET)

== Features I'd like to see ==

Hi, Here are a couple of things I'd like to see included in the music player software which I haven't seen mentioned anywhere (perhaps because they're obvious?):

* 'Ipod Mode' - a button to Turn off the screen / put the unit in standby but keep the music playing, to save battery and extend the playing time.

* 'Auto-Pause' - If I'm listening to music and the phone rings, the music should pause itself automatically. Also it should resume playing after the call ends.

These are two cool features of the Excellent [http://www.pocketpcfreewares.com/en/index.php?soft=813 MortPlayer], which is the MP3 Player I currently use on my Windows CE (shudder) device. I'd love to see them on my freerunner!