Instalace Micro-SD karty, SIM karty, a akumulátoru

Remove the rear cover of the Neo FreeRunner by first holding the Neo FreeRunner on the side and then use your fingernail to prise off the rear cover at the slot on top of the device.

Now you should be able to locate the combined SIM and Micro-SD card holder at the bottom of the battery compartment.

Unlock the SIM card holder by sliding the metal clip down, towards the USB socket, with your fingernail. Use caution, as these parts are delicate and could be damaged by forcing them in the wrong direction.

Lift up on the SIM card holder.

The Micro-SD card holder is held in place by a latch on either side. It is easiest to open the Micro-SD card holder by releasing these latches one at a time rather than by lifting from the middle, as lifting from the middle tends to increase the latching pressure. A small screwdriver or knife can be used for this.

Insert the Micro-SD card into the Micro-SD card holder. Note that on the inside of metal part of the holder there are little holding tabs for the card. Slide the card in these holders (on the metal part) before closing the card holder. Note that the electrical contacts should face down and towards the edge of the Neo FreeRunner.

Close the Micro-SD card holder, making sure that both latches of the holder are securely fastened.

Insert the SIM card into the SIM card holder, taking care to slide inside the two metal tabs in the cover. Note that the electrical contacts should face down and that the cut corner should be closest to the external GPS Antenna Socket.

Close the SIM card holder and lock it by sliding the metal clip towards the external GPS Antenna Socket on the FreeRunner.

Insert the battery into the battery compartment, aligning the electrical contacts on the battery with the electrical contacts in the battery compartment. Insert the side with the electrical contacts first.

Odemknutí obrazovky

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

Menus and Applications

Note: this section describes the interface used by the "2007.2" image, which is the current default image for Openmoko.

Today Page

The first thing after you boot Openmoko should be the "Today" page. This is your home page. In the top row, you see icons that indicate the status of the phone. The second row are quick links to commonly-used applications such as the dialer. The main body of the screen is your home page, displaying a clock and other useful information. The bottom row consists of three tabs representing Today (the page you're viewing now), Launch Task Page, and Running Tasks Page.

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

Launch Task Page

Stub: This is a stub. You can help OpenMokoWiki by expanding it.

This page displays a menu of available applications. You may choose a category of applications to display to simplify the screen, or choose to display them all.

Running Tasks Page

Stub: This is a stub. You can help OpenMokoWiki by expanding it.

This page displays currently-running tasks. Any individual task may be terminated by selecting it and then clicking on the garbage-can icon to close it. All tasks may be terminated by clicking on any one of them and then clicking on the "folder" icon in the upper right (expect this to change in future releases). Any task may be rejoined by selecting it and then selecting the "return" icon at the middle top.

Ukončení aplikace

Any time an application is running, you can simply click the device's power button and the application will exit, returning you to the Today page.

Alternatively, you can switch tasks at any time by clicking the menu of tasks at the far upper-left of the screen, which will display a list of running tasks, allowing you to select one.

(Note: If the task menu is not shown, use the Aux button to bring up the Aux menu, and select "Toggle Fullscreen".)

Změna hlasitosti

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

For now, run the terminal application or log in via usb, and run the alsamixer application. The mixer is simpler than it looks. Just use the left and right arrow keys to select "headphone" or "PCM" and use the up and down arrow keys to adjust the volume. You can also adjust your microphone volume with the "mic2" adjustment. Press ESC when finished. Then exit the terminal application or log out of the USB login.

You may need to update configuration files in /usr/share/openmoko/scenarios/ to make the microphone setting permanent. Use

alsactl -f path-to-statefile store

to do this.

The default files are as follows (in /usr/share/openmoko/scenarios/):

gsmhandset.state

gsmheadset.state

gsmspeakerout.state

headset.state

stereoout.state

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

Accessing the microSD card

Mounted at /media/card

Import kontaktů

If you can export your contacts to VCard format, either multiple files or single file containing all of them, you may use the script on Import Vcf Contacts page to bring them to Neo.

Note that uboot, the kernel and the root filesystem may all be flashed to update them. For uboot, this is the only possibility (see Flashing_the_Neo_FreeRunner#Flashing_the_boot_loader). The advantage of flashing the kernel manually rather than using opkg seems to be speed. The disadvantage of flashing the root file system is that it wipes out all local modifications, including /home. If /home is moved to the SD disk, this is no longer a problem.

Warning: UPGRADING TO DAILY KERNELS FROM THE DEVELOPMENT BRANCH MAY BREAK THINGS. That said, assuming that your FreeRunner can access the internet (see above), the kernel and other packages can be updated with

# opkg update
# opkg -test upgrade
# opkg upgrade

The first updates the repository information, telling opkg what packages are available. The second allows you to see what the package manager wants to do. The third upgrades all packages for which a newer version is available. At the moment, some signature files are missing (404 errors), which opkg complains about, but this is cosmetic. The repositories will still update with the missing signature files.

Note that running opkg upgrade on a factory-fresh phone will upgrade dropbear (the ssh software) and various xserver packages, and neither upgrades elegantly while in use. Xserver must be updated over ssh to complete succesfully. Dropbear can be updated over ssh with the proper command:

# nohup opkg upgrade dropbear &

Or upgrade it directly in the FreeRunner terminal.

# opkg upgrade dropbear

When updating over ssh, the session will be interrupted, but the command should complete successfully(check nohup.out on your device to verify), and you should be able to reconnect within a few seconds.

Another (better) option is to start a screen session before the upgrade with:

# screen

After loosing the ssh connection and login in again via ssh reconnect to the running screen session with:

# screen -x

Then connect to the FreeRunner via ssh and type:

# opkg upgrade

Recent changes to the usb ethernet support require that you install these two modules, before you reboot, after updating.

Alternatively you can upgrade the xserver packages via ssh and then upgrade the rest from the FreeRunner's terminal.

If you do your first upgrade in two installments like this, it will go more smoothly.

It will be possible in the future to update uboot with opkg, but this has not yet been implemented.

Installing multimedia, web browsing and other applications

There are many applications you can install - check out the Repositories for a list of packages, an example of how to add a repository using scaredy cat as an example can also be found here. A list of pre-installed and available packages with descriptions can be found here - Available Packages.

Importing contacts

If you can export your contacts to VCard format, either multiple files or single file containing all of them, you may use the script on Import Vcf Contacts page to bring them to Neo.

The Architecture

There are three layers to the software on the FreeRunner:

uBoot

Think of u-boot as a combination of the BIOS and Grub on a PC.

Kernel

The Linux kernel.

Root Filesystem

The rest of the system

Updating the software

In order to keep the FreeRunner up-to-date with the latest features and bug-fixes, it is advisable update the software at regular intevals. There are two main methods of doing this.

opkg

Assuming that your FreeRunner can access the internet (see above), the kernel and other packages can be updated with

# opkg update
# opkg upgrade

The first updates the repository information, telling opkg what packages are available. The second upgrades all packages for which a newer version is available. At the moment, some signature files are missing (404 errors), which opkg complains about, but this is cosmetic. The repositories will still update with the missing signature files.

It will be possible in the future to update uboot with opkg, but this has not yet been implemented

Flashing

uboot, the kernel and the root filesystem can all be flashed to update them. See below for how. For uboot, this is the only possibility. The advantage of flashing the kernel, rather than using opkg seems to be speed.

The disadvantage of flashing the root file system is that it wipes out all local modifications, including /home. If /home is moved to the SD disk, this is no longer a problem.

Un-crippling the 2007.2 image

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

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

Start the Openmoko Image

Press and hold Power button for about 8 seconds, until the Openmoko splash screen turns up. You may now release the Power button and the Neo FreeRunner will continue to boot into the Openmoko Image.

Log into U-Boot in the NAND Flash

Press and hold Power button, then press and hold AUX button for about 5 to 8 seconds. You should see the boot menu for the NAND Flash. Press the AUX button to select one of the options and then press the Power button to execute.

Log into U-Boot in the NOR Flash

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

NOTE: There are six options you can choose when you log into the NOR Flash.

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

Flashing the Neo FreeRunner

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

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

Step 2. Flashing the Kernel

Before you execute the following command, please log into U-Boot in the NOR Flash. The Neo FreeRunner needs to be at the NOR boot menu for flashing. You will then need to connect your Neo with the GNU/Linux host via USB cable.

Type in the following command in the terminal on a GNU/Linux host. On some systems you need to be root before this will work 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"

Instalace Micro-SD karty, SIM karty, a akumulátoru

Remove the rear cover of the Neo FreeRunner by first holding the Neo FreeRunner on the side and then use your fingernail to prise off the rear cover at the slot on top of the device.

Now you should be able to locate the combined SIM and Micro-SD card holder at the bottom of the battery compartment.

Unlock the SIM card holder by sliding the metal clip down, towards the USB socket, with your fingernail. Use caution, as these parts are delicate and could be damaged by forcing them in the wrong direction.

Lift up on the SIM card holder.

The Micro-SD card holder is held in place by a latch on either side. It is easiest to open the Micro-SD card holder by releasing these latches one at a time rather than by lifting from the middle, as lifting from the middle tends to increase the latching pressure. A small screwdriver or knife can be used for this.

Insert the Micro-SD card into the Micro-SD card holder. Note that on the inside of metal part of the holder there are little holding tabs for the card. Slide the card in these holders (on the metal part) before closing the card holder. Note that the electrical contacts should face down and towards the edge of the Neo FreeRunner.

Close the Micro-SD card holder, making sure that both latches of the holder are securely fastened.

Insert the SIM card into the SIM card holder, taking care to slide inside the two metal tabs in the cover. Note that the electrical contacts should face down and that the cut corner should be closest to the external GPS Antenna Socket.

Close the SIM card holder and lock it by sliding the metal clip towards the external GPS Antenna Socket on the FreeRunner.

Insert the battery into the battery compartment, aligning the electrical contacts on the battery with the electrical contacts in the battery compartment. Insert the side with the electrical contacts first.

Odemknutí obrazovky

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

Menus and Applications

Note: this section describes the interface used by the "2007.2" image, which is the current default image for Openmoko.

Today Page

The first thing after you boot Openmoko should be the "Today" page. This is your home page. In the top row, you see icons that indicate the status of the phone. The second row are quick links to commonly-used applications such as the dialer. The main body of the screen is your home page, displaying a clock and other useful information. The bottom row consists of three tabs representing Today (the page you're viewing now), Launch Task Page, and Running Tasks Page.

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

Launch Task Page

Stub: This is a stub. You can help OpenMokoWiki by expanding it.

This page displays a menu of available applications. You may choose a category of applications to display to simplify the screen, or choose to display them all.

Running Tasks Page

Stub: This is a stub. You can help OpenMokoWiki by expanding it.

This page displays currently-running tasks. Any individual task may be terminated by selecting it and then clicking on the garbage-can icon to close it. All tasks may be terminated by clicking on any one of them and then clicking on the "folder" icon in the upper right (expect this to change in future releases). Any task may be rejoined by selecting it and then selecting the "return" icon at the middle top.

Ukončení aplikace

Any time an application is running, you can simply click the device's power button and the application will exit, returning you to the Today page.

Alternatively, you can switch tasks at any time by clicking the menu of tasks at the far upper-left of the screen, which will display a list of running tasks, allowing you to select one.

(Note: If the task menu is not shown, use the Aux button to bring up the Aux menu, and select "Toggle Fullscreen".)

Změna hlasitosti

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

For now, run the terminal application or log in via usb, and run the alsamixer application. The mixer is simpler than it looks. Just use the left and right arrow keys to select "headphone" or "PCM" and use the up and down arrow keys to adjust the volume. You can also adjust your microphone volume with the "mic2" adjustment. Press ESC when finished. Then exit the terminal application or log out of the USB login.

You may need to update configuration files in /usr/share/openmoko/scenarios/ to make the microphone setting permanent. Use

alsactl -f path-to-statefile store

to do this.

The default files are as follows (in /usr/share/openmoko/scenarios/):

gsmhandset.state

gsmheadset.state

gsmspeakerout.state

headset.state

stereoout.state

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

Accessing the microSD card

Mounted at /media/card

Import kontaktů

If you can export your contacts to VCard format, either multiple files or single file containing all of them, you may use the script on Import Vcf Contacts page to bring them to Neo.

Note that uboot, the kernel and the root filesystem may all be flashed to update them. For uboot, this is the only possibility (see Flashing_the_Neo_FreeRunner#Flashing_the_boot_loader). The advantage of flashing the kernel manually rather than using opkg seems to be speed. The disadvantage of flashing the root file system is that it wipes out all local modifications, including /home. If /home is moved to the SD disk, this is no longer a problem.

Warning: UPGRADING TO DAILY KERNELS FROM THE DEVELOPMENT BRANCH MAY BREAK THINGS. That said, assuming that your FreeRunner can access the internet (see above), the kernel and other packages can be updated with

# opkg update
# opkg -test upgrade
# opkg upgrade

The first updates the repository information, telling opkg what packages are available. The second allows you to see what the package manager wants to do. The third upgrades all packages for which a newer version is available. At the moment, some signature files are missing (404 errors), which opkg complains about, but this is cosmetic. The repositories will still update with the missing signature files.

Note that running opkg upgrade on a factory-fresh phone will upgrade dropbear (the ssh software) and various xserver packages, and neither upgrades elegantly while in use. Xserver must be updated over ssh to complete succesfully. Dropbear can be updated over ssh with the proper command:

# nohup opkg upgrade dropbear &

Or upgrade it directly in the FreeRunner terminal.

# opkg upgrade dropbear

When updating over ssh, the session will be interrupted, but the command should complete successfully(check nohup.out on your device to verify), and you should be able to reconnect within a few seconds.

Another (better) option is to start a screen session before the upgrade with:

# screen

After loosing the ssh connection and login in again via ssh reconnect to the running screen session with:

# screen -x

Then connect to the FreeRunner via ssh and type:

# opkg upgrade

Recent changes to the usb ethernet support require that you install these two modules, before you reboot, after updating.

Alternatively you can upgrade the xserver packages via ssh and then upgrade the rest from the FreeRunner's terminal.

If you do your first upgrade in two installments like this, it will go more smoothly.

It will be possible in the future to update uboot with opkg, but this has not yet been implemented.

Installing multimedia, web browsing and other applications

There are many applications you can install - check out the Repositories for a list of packages, an example of how to add a repository using scaredy cat as an example can also be found here. A list of pre-installed and available packages with descriptions can be found here - Available Packages.

Importing contacts

If you can export your contacts to VCard format, either multiple files or single file containing all of them, you may use the script on Import Vcf Contacts page to bring them to Neo.

The Architecture

There are three layers to the software on the FreeRunner:

uBoot

Think of u-boot as a combination of the BIOS and Grub on a PC.

Kernel

The Linux kernel.

Root Filesystem

The rest of the system

Updating the software

In order to keep the FreeRunner up-to-date with the latest features and bug-fixes, it is advisable update the software at regular intevals. There are two main methods of doing this.

opkg

Assuming that your FreeRunner can access the internet (see above), the kernel and other packages can be updated with

# opkg update
# opkg upgrade

The first updates the repository information, telling opkg what packages are available. The second upgrades all packages for which a newer version is available. At the moment, some signature files are missing (404 errors), which opkg complains about, but this is cosmetic. The repositories will still update with the missing signature files.

It will be possible in the future to update uboot with opkg, but this has not yet been implemented

Flashing

uboot, the kernel and the root filesystem can all be flashed to update them. See below for how. For uboot, this is the only possibility. The advantage of flashing the kernel, rather than using opkg seems to be speed.

The disadvantage of flashing the root file system is that it wipes out all local modifications, including /home. If /home is moved to the SD disk, this is no longer a problem.

Un-crippling the 2007.2 image

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

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

Start the Openmoko Image

Press and hold Power button for about 8 seconds, until the Openmoko splash screen turns up. You may now release the Power button and the Neo FreeRunner will continue to boot into the Openmoko Image.

Log into U-Boot in the NAND Flash

Press and hold Power button, then press and hold AUX button for about 5 to 8 seconds. You should see the boot menu for the NAND Flash. Press the AUX button to select one of the options and then press the Power button to execute.

Log into U-Boot in the NOR Flash

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

NOTE: There are six options you can choose when you log into the NOR Flash.

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

Flashing the Neo FreeRunner

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

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

Step 2. Flashing the Kernel

Before you execute the following command, please log into U-Boot in the NOR Flash. The Neo FreeRunner needs to be at the NOR boot menu for flashing. You will then need to connect your Neo with the GNU/Linux host via USB cable.

Type in the following command in the terminal on a GNU/Linux host. On some systems you need to be root before this will work 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"