Openmoko - User contributions [en]

USB Networking

2009-02-03T11:21:43Z

VilleWitt: /* Ubuntu Issues */

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

In other words: if your existing router and desktop have addresses 192.168.0.(something) changing them to e.g. 192.168.1.(something) might save you a lot of troubleshooting later. A discussion of this is [http://lists.openmoko.org/pipermail/support/2008-August/thread.html#1277 here].

== Things to keep in mind ==

* When the FreeRunner suspends it disables it's USB networking interface. Therefore it is a good idea to turn off the FreeRunners suspend function when using USB networking. You can do this manually or automatically. [https://wiki.muc.ccc.de/openmoko This] site has two scripts ([https://wiki.muc.ccc.de/openmoko#disable_suspend_if_on_external_power one for Om 2007] and [https://wiki.muc.ccc.de/openmoko#disable_suspend_if_on_external_power1 one for Om 2008]) which disable suspend if the FreeRunner is on external power.

= Simple Manual Linux Configuration =
Try this first (as root on your desktop, with FreeRunner attached via USB cable and booted properly, not at the Boot Menu). If it works, then you can add permanent configuration or use more sophisticated setups below.
=== The shortest way ===
This simple way has been tested with many Linux distributions (Fedora, SuSE, Red Hat, Debian and others) and network configurations. It was even successfully applied to connect another Linux based handhelds like TDS Nomad and surely can be recommended as the first attempt. The way assumes that you have the recent Linux distribution with USB networking enabled and also rather typical network setup.

With the device connected configure usb0 interface (as root):
<pre>
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
</pre>
If your eth0 interface is also in the same 'range' (e.g. 192.168.0.105) then you can do the following:

1. ping the Neo with
# ping -I usb0 192.168.0.202
2. log in to the Neo (you do not need to be a root on the desktop host just to log in).
# ssh root@192.168.0.202
The default password is blank.

Do not forget to allow ssh (open the port 22) on your firewall so that you can connect to the device. If you suspect any firewall issues, the simplest way is to unplug the main Internet cable leaving only Neo connected and then temporary turn the firewall off.

Also, some old or narrowly configured Linux distributions may not have USB networking support. For such cases the simple way might be just to upgrade.

=== The more advanced way ===
If the previously described simple approach does not work, you may try the more complex one.

<pre>iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ip addr add 192.168.0.200/24 dev usb0</pre>

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

<pre>ip addr add 192.168.0.200/28 dev usb0</pre>

(This will just map the net from 192.168.0.192 to 192.168.0.207 onto usb0. If you get the error 'Cannot find device "usb0"', double-check that your FreeRunner is turned on and connected by USB. If that doesn't work, try unplugging and replugging the USB cable.)

And in this case you should enable ARP proxy on internet facing interface INSTEAD of using iptables:

<pre>sysctl net.ipv4.conf.eth2.proxy_arp=1</pre>

This assuming that eth2 is connected to ISP.

Then
<pre>ifconfig usb0 up</pre>

Then (ideally, not as root):

<pre>ssh root@192.168.0.202</pre>

The default password is blank.

Due to the fact that in most cases your Neo will use the same dns servers as your computer uses, you can automate the process of writing dns servers to your phone:

<pre>#!/bin/sh
/sbin/route add -host 192.168.0.202/32 dev usb0
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
iptables -P FORWARD ACCEPT
sysctl -w net.ipv4.ip_forward=1
su `whoami` -c "scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf"</pre>

Again if your net already is 192.168.0.0, replace the POSTROUTING statement with
<pre>iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/28</pre>

This simple script will set up routing for your Freerunner and than copy resolv.conf with dns addresses straight to the phone.
All you have to do is connect phone to the computer, run the script and enjoy internet connection from your phone.

=== Changing the Neo IP address ===

Like mentioned above, if the default Neo subnet 192.168.0.X is already used, it might be necessary to change the
Neo [http://en.wikipedia.org/wiki/IP_address IP adress] and subnet.
To achieve this, edit /etc/network/interfaces on the Neo (and reboot it).
In the following example the Neo will use the IP address 192.168.100.1 (instead of the default 192.168.0.202)
within the network 192.168.100.X (instead of 192.168.0.X),
another [http://en.wikipedia.org/wiki/Private_network private] class C network.
(The [http://en.wikipedia.org/wiki/Subnetwork#Binary_subnet_masks netmask] indicates that the first 3 bytes (all bits set) are used to determine the subnet
and the last byte (no bits set) to determine the machine.)
The gateway (the computer, the Neo is attached to) also has to be part of the subnet and is expected to be 192.168.100.254 (instead of 192.168.0.200) here.

Modifications for /etc/network/interfaces:

<pre>
auto usb0
iface usb0 inet static
address 192.168.100.1
netmask 255.255.255.0
network 192.168.100.0
gateway 192.168.100.254
</pre>

(The network entry seems to be redundant information, since it can be derived from address and netmask?)
Note that wiki articles usually expect default settings and you have to adjust the IP adress, gateway, etc entries according to your changes.

= Linux Kernel Support =

Your Linux desktop/laptop needs to have suitable support. In particular you will need to have enabled USB networking and masquerading support in the kernel. For default kernels in many Linux distributions this will already be the case.

== USB Networking support ==

The following options need to be enabled:

* CONFIG_USB_USBNET (''Multi-purpose USB Networking Framework''. Module will be called <tt>usbnet</tt>)
* CONFIG_USB_NET_CDCETHER (''CDC Ethernet support''. Module will be called <tt>cdc_ether</tt>)

These options are available in ''Device Drivers -> USB support -> USB Network Adapters'' or ''Device Drivers -> Network Device Support -> USB Network Adapters.

In order for USB networking to work you need to load the <tt>cdc_ether</tt> module (when loading <tt>cdc_ether</tt> the module <tt>usbnet</tt> will be loaded automatically). For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

== Masquerading support ==

Masquerading options are found in ''Networking ---> Networking options --->'' (tested on Linux 2.6.26.3).

To enable the needed options you first have to enable:

* CONFIG_NETFILTER (''Network packet filtering framework (Netfilter)'')

Then, from

''Networking --->
Networking options --->
[*] Network packet filtering framework (Netfilter) --->
Core Netfilter Configuration --->''

You need at least following options enabled as modules:

* CONFIG_NF_CONNTRACK (''Netfilter connection tracking support'')
* CONFIG_NF_CONNTRACK_FTP (''FTP protocol support'')
* CONFIG_NETFILTER_XTABLES (''Netfilter Xtables support'')

Rest of the needed options are found from

''Networking --->
Networking options --->
[*] Network packet filtering framework (Netfilter) --->
IP: Netfilter Configuration --->''

You need to enable (again, as modules is fine):

* CONFIG_NF_CONNTRACK_IPV4 (''IPv4 connection tracking support (required for NAT)'')
* CONFIG_IP_NF_IPTABLES (''IP tables support (required for filtering/masq/NAT)'')
* CONFIG_NF_NAT (''Full NAT'')
* CONFIG_IP_NF_TARGET_MASQUERADE (''MASQUERADE target support'')

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

The most relevant table is the nat table, which controls translation of addresses:

iptables -L -t nat -v -n

Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:

iptables -L -t filter -v -n

If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:

iptables -t filter -F FORWARD

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

== Configure Default Neo DNS ==

DNS is configured in /etc/resolv.conf on your FreeRunner.

You should add the IP address of the DNS servers as provided by your ISP. Check your router's or PC's network status for the nameserver IP addresses.

<pre>echo nameserver xxx.xxx.xxx.xxx > /etc/resolv.conf</pre>

You can also add the public DNS server called openDNS:
<pre>echo nameserver 208.67.222.222 > /etc/resolv.conf
echo nameserver 208.67.220.220 >> /etc/resolv.conf</pre>

These settings will be lost on reboot. You can set the DNS for the next connect, by adding the following to the end of the usb0 setting in /etc/network/interfaces, right above the bluetooth networking section:
<pre>up echo nameserver 208.67.222.222 > /etc/resolv.conf
up echo nameserver 208.67.220.220 >> /etc/resolv.conf</pre>

== Proxying DNS from Desktop/Laptop ==

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), without running or installing a DNS server. 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"

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

=== Proxying with iptables ===

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

<pre>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</pre>

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

Test if it works:
<pre>ping www.google.com</pre>

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.

= Testing Your Connection =
You should be able to connect to your Neo! Make sure you can ping your Neo to be sure.
ping 192.168.0.202

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank (press enter).

You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

Now, make sure you can ping back to your desktop
ping 192.168.0.200
(Note that some systems like Vista, don't respond to ICMP ping by default)

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com

= OS or Distro Specific & Automatic Configuration =

Based on [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] by Marcin 'Hrw' Juszkiewicz.
These instructions should keep you from having to run the Simple Manual Linux Configuration every time you plug in and want to connect to an Openmoko device. One run and then you're done!

If the Simple Manual Linux Configuration does not work for your OS or Distro (MacOS X, MS Windows, etc) there may be instructions here that work for you.

== MacOS X ==
See [[MacOS_X#USB_Networking|MacOS X USB Networking]].

== Windows ==
See [[Neo1973_and_Windows#USB_Ethernet_emulation|Windows USB Ethernet emulation for Neo1973]].

There is also a very helpful tutorial for connecting with Vista at [http://sam.curren.ws/index.cfm/2008/7/14/Using-the-Neo-FreeRunner-with-Windows-XPVista].

== FreeBSD ==
You need to load the cdce kernel module (if it is not already linked into your kernel). As root do:

# kldload cdce

The Neo should then show up as cdce0 interface and you can handle the cdce0 interface just like the usb0 device under Linux. For more information see the cdce manpage. An easy way to assign the IP address to the cdce0 interface is using the devd(8) daemon. Create the following two files,

<tt>/usr/local/etc/devd/cdce.conf</tt> as:

<pre>
notify 1 {
match "system" "IFNET";
match "subsystem" "cdce0";
match "type" "ATTACH";
action "/usr/local/etc/devd/cdce.sh $subsystem $type";
};
</pre>

and <tt>/usr/local/etc/devd/cdce.sh</tt> as:

<pre>
#!/bin/sh
case $2 in
'ATTACH')
ifconfig cdce0 192.168.0.200 netmask 255.255.255.0
exit 0 ;
;;
esac
exit 0
</pre>

Then restart the devd(8) daemon with:

# /etc/rc.d/devd restart

If you now plugin the FreeRunner into the USB port the cdce0 interface gets created and the IP addr will be assigned.

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
up iptables -A POSTROUTING -t nat -s 192.168.0.0/24 -j MASQUERADE
up echo 1 > /proc/sys/net/ipv4/ip_forward
down iptables -D POSTROUTING -t nat -s 192.168.0.0/24 -j MASQUERADE
</pre>

This is more sophisticated than the manual setup. The 'auto usb' stanza ties into the Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner 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.

Another possible configuration that adds DNS forward and removes
the iptables changes after unplugging:

in /etc/network/interfaces add
<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop
</pre>

create file /etc/network/freerunner
<pre>
#!/bin/sh
#
# configures the freerunner for internet
#
#

DEVICE=usb0
IPADDR=192.168.0.200
REMOTE_IPADDR=192.168.0.202
NETMASK=255.255.255.0

# get first ip for dns
DNSIP=$(awk '$1 == "nameserver"{print $2; exit(0);}' /etc/resolv.conf)

case "$1" in
start)
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward
echo 1 > /proc/sys/net/ipv4/ip_forward
fi
;;
stop)
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ -f /var/run/openmoko.ip_forward ]; then
rm /var/run/openmoko.ip_forward
echo 0 > /proc/sys/net/ipv4/ip_forward
fi
;;
esac
</pre>

Make /etc/network/freerunner executable with
chmod +x /etc/network/freerunner

It is possible to use network-manager to automatically connect to the Freerunner using udev. The process uses udev to run a script when the Frerunner is plugged in. The script uses the ip command to set the mac address of the usb network interface. To begin, create /etc/udev/rules.d/80-freerunner.rules :

<pre>
# This file causes programs to be run on device insertion.
# See udev(7) for syntax.
# rule to assign a fixed mac address specified in /
KERNEL=="usb[0-9]*", DRIVERS=="cdc_ether", ACTION=="add", RUN+="/usr/local/sbin/freerunner-usb-add.sh %k"
</pre>

Next, create the /usr/local/sbin/freerunner-usb-add.sh :

<pre>
#!/bin/sh
(
busNum=$( printf %.2d $( expr match "$1" "usb$[0-9]*$") )
ip link set "$1" address 00:00:22:55:bb:$busNum &> /dev/null
) &
exit 0
</pre>

Finally run "chmod +x /usr/local/sbin/freerunner-usb-add.sh" to make it executable. Now you can use network-manager with mac-address specific settings and get it to automatically connect.

=== Ubuntu 8.10 - Easy Way ===

1. Connect Neo to PC and wait about a minute when NetworkManager stops scanning usb for dhcp (wait when icon in the tray switches to normal).

2. Open "nm-connection-editor", select "Auto usb0", click "Edit", then "IPv4 Settings". Set "Method" - "Manual", click "Add". In the "Address" field write "192.168.0.200", "Netmask" - "255.255.255.0", leave "Gateway" field empty. Click "OK", then "Close".

3. Now you can connect via ssh to 192.168.0.202

Then, based on [http://sebastian-bergmann.de/index.php?url=archives/801-OpenMoko-Freerunner-and-Ubuntu.html#feedback these instructions], you should be able to setup masquerading by running the following commands on your Ubuntu PC:

<pre>sudo iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
sudo iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
sudo iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sudo bash -c 'echo 1 > /proc/sys/net/ipv4/ip_forward'</pre>

=== Ubuntu Issues ===

Ubuntu 8.10 doesn't work as expected if you used /etc/network/interfaces to automate the connection. 
Network manager likes to latch onto the network device and add a default route through 192.168.0.202, breaking your network connection.
Network manager also says you can't edit or remove this connection from its list. I'm going back to making the connection manually. 
Using the /usr/local/sbin/freerunner-usb-add.sh script for some automatism can be a workaround:
<pre>
#!/bin/sh
(
ifconfig usb0 192.168.0.200 netmask 255.255.255.192 > /dev/null
ifconfig usb0 up > /dev/null
/etc/network/freerunner start
) &
exit 0
</pre>

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. Moving the DRIVERS=="*?" out of the top GOTO, to ACTION=="add" line fixes the problem.

<pre>
SUBSYSTEM=="net", 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", DRIVERS=="?*", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}"

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

LABEL="net_end"
</pre>

The bug is that the DRIVERS variable isn't set at all when the device is unplugged.

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)
:Actually it appears that it's not fixed, but patching that file and disconnecting and reconnecting the phone works perfectly. --[[User:Johndoesacc|Johndoesacc]] 18:37, 20 August 2008 (UTC)
:Well, yes, it must be fixed because it worked for me out-of-the-box without tweaking the udev rule on 8.04 --[[User:EtienneG|EtienneG]] November 26th, 2008
:It wasn't solved in my case, as of 3. February 2009 in 8.04 (AMD64), the patch above solved my problem thou. --[[User:VilleWitt|VilleWitt]] February 3td, 2009.

=== Ubuntu Workaround ===
Use [http://wicd.sourceforge.net/ wicd] instead of networkmanager:
It is much further in development than networkmanager yet and doesn't make any problems with USB networking. You can use the "normal" settings in /network/interfaces.
;Note: Because of it's dependencies it deinstalls networkmanager.

== Mandriva ==

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

<tt>/etc/sysconfig/network-scripts/ifcfg-usb0</tt>:

<pre>
DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.0
NETWORK=192.168.0.0
BROADCAST=192.168.0.255
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes
</pre>

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)

<tt>/etc/sysconfig/network-scripts/usb0-routes</tt>:

<pre>
ADDRESS0=192.168.0.200
NETMASK0=255.255.255.0
</pre>

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

service network restart

This didn't work for me (Mandriva 2008.1), giving errors from Shorewall. However, simply using MCC, Network->Sharing Internet Access worked fine. You need to connect Neo when starting it. --[[User:Alih|Alih]] 18:50, 22 September 2008 (UTC)

== 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 FC9, FC8 & FC5 ===

edit file <tt>/etc/sysconfig/network-scripts/ifcfg-usb0</tt> to look like this:

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

and restart networking service by typing:

service network restart

if your '''openmoko''' is connected when you restart network you should see system message:

<code>Bringing up interface usb0 [OK]</code>

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

=== Option C - tested on F9 ===
(worked on FC8 too, can this be called "tested"?)

Plug in the usb cable. NetworkManager should detect the phone automatically but you should ignore it.
Open Network Configuration tool (System -> Administration -> Network) and perform following steps:
# Click '''New''' button on top bar
# Click '''Forward'''
# Select OpenMoko from device list
# Click '''Forward'''
# Select 'Statically set IP address:' and enter address: 192.168.0.200, netmask 255.255.255.0 (or use 255.255.255.240 if you want only route ip range 192.168.0.192-192.168.0.207). Leave gateway empty.
# Click '''Forward'''
# Click '''Apply''' to close add dialog
# Select newly added usb0 device from the device list.
# Click '''Edit''' button on top bar
# You might want to remove a tick from 'Activate device when computer starts' check box.
# Click '''Ok''' to close window dialog.
Save settings and close the window.

Open Firewall Configuration (System -> Administration -> Firewall) and enable masquerading:
# Select '''Masquerading''' from left panel
# Check device(s) which you'd like to share internet connection. Typically eth0 or wlan0.
# Click '''Apply''' and close application

Open terminal and perform (as root user):
# ifdown usb0
# ifup usb0
The first command will remove any existing settings given by the NetworkManager and second command brings the device up with appropriate settings.

Now you should be able to ping e.g. 74.125.39.99 [www.google.com] from OpenMoko. Configure /etc/resolv.conf and you should have full a internet access.

==== Troubleshooting ====
If Network Configuration tool cannot see the the usb0 try to unplug the usb cable for a few seconds and wait until the NetworkManager finds it again.

NetworkManager will assign a new ip address for the OpenMoko if link goes down for a while. You can fix this by issuing '''ifup usb0''' again.

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

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

Create a new init script:

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

=== Manual Configuration ===

Put iptables into use:

<pre>
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
</pre>

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

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

<pre>
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
}
</pre>

== Slackware (tested with 12.1) ==

Following is based on [http://www.enricozini.org/2008/tips/autodock-freerunner.html Enrico Zini's solution].

Create a new udev rules file <tt>/etc/udev/rules.d/91-openmoko.rules</tt>:

<pre>
SUBSYSTEM=="net", ACTION=="add", ATTRS{idVendor}=="1457", ATTRS{idProduct}=="5122", RUN+="/sbin/om-usb $env{INTERFACE} start"
SUBSYSTEM=="net", ACTION=="remove", ENV{INTERFACE}=="usb[0-9]", RUN+="/sbin/om-usb $env{INTERFACE} stop"
</pre>

Then create the script <tt>/sbin/om-usb</tt>:

<pre>
#!/bin/sh
INTERFACE=$1
ACTION=$2

# udev fails silently when the script fails, e.g. due to commands not
# being found
PATH=/usr/sbin:/sbin:/usr/bin:/bin

case $ACTION in
'start')
# Put all your setup here
;;
'stop')
# Put all your tear down here
;;
*)
echo "Usage: $0 {start|stop}"
exit 1
;;
esac
</pre>

The <tt>INTERFACE</tt> will be <tt>usb0</tt> in most cases.

== Archlinux ==
Following is based on [http://xenos.altervista.org/blogs/index.php?blog=3&title=openmoko-usb-networking-su-archlinux furester's solution].

Install package [http://aur.archlinux.org/packages.php?ID=20220 openmoko-usb-networking] from AUR:

$ yaourt -S openmoko-usb-networking

= 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 adding a new line for every ssh host-key to your known_hosts you can add the following to the phone section in ~/.ssh/config (or see the snippet at : [[USB Networking#Changing_host_keys]] bellow)

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:

user@host$ 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:

root@phone# mkdir ~/.ssh

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

user@host$ scp ~/.ssh/id_rsa.pub root@phone:~/.ssh/authorized_keys

You should now be able to ssh directly into the phone without a password prompt using a command like 'ssh root@phone' from the account user@host because the public key in the file user@host:~/.ssh/id_rsa.pub is contained in the list of keys which have access in the file root@phone:~/.ssh/authorized_keys (since scp is used, only one key exists, but you can grant access to the phone from more than one account, for example user@host, user@laptop).

To make ssh login as root by default, add the following lines to ~/.ssh/config:

Host phone
User root

Replace ''phone'' with the hostname or ip of your phone. You should now be able to ssh into the phone without having to type ''root@'' every time.

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). Now you have set this, you can issue the following command to connect to your moko :

ssh root@moko

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

<tt>
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.
</tt>

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'' #(isn't the "env" redundant here?)

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

== sftp ==
After you get the SSH connection working, it is possible to use Konqueror, Nautilus or another sftp - enabled tool to browse the phone filesystem and deploy the test applications. Just enter sftp://root@192.168.0.202 into address bar.

== sshfs ==
You can use sshfs to mount the phones filesystem into the hosts filesystem. Make sure that fuse-sshfs is installed and that you are allowed to use fuse. Now run:

sshfs 192.168.0.202:REMOTE_PATH LOCAL_MOUNT_POINT

REMOTE_PATH can now be accessed through LOCAL_PATH.

==Automated setup network and mounting partitions==

See [https://bugs.launchpad.net/ubuntu/+bug/289548 Ubuntu bug report in launchpad].


{{Languages|USB Networking}}

[[Category:USB]]
[[Category:Implemented]]
[[Category:Networking]]

Openmoko Local Groups: Denmark

2009-01-24T19:57:08Z

VilleWitt: /* Possible Participants */

=== Possible Participants ===
{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
!Has Device
!Has Debug Board
|-
|[[User:Miki|Mikkel Kirkgaard Nielsen]]
|developer; some assembly, C, some C++, Shell scripting, POSIX etc.
|Getting Openmoko (and Neo1973) to rock
|Esbjerg, Østerbyen
|
|[[ Image:Moko.jpg |center]]
|[[ Image:MokoBox.jpg |center]]
|-
|[[User:Mikl-dk|Mikkel Meyer Andersen]]
|developer; C#, C/C++ (is certainly going to be improved with this project)
|Location-based reminding and automatic sms answering among others
|Aalborg
|Computer science student
|[[ Image:Moko.jpg |center]]
|[[ Image:MokoBox.jpg |center]]
|-
|[[User:EsbenDamgaard|Esben Damgaard]]
|developer; [[Python]], C/C++
|Everything ;)
|Odense
|Computer science student
|[[ Image:Moko.jpg |center]]
|-
|[[User:Sorenmat|Soren Mathiasen]]
|developer; [[Java]], C/C++
|Everything ;)
|Roskilde
|Software developer
|[[ Image:Moko.jpg |center]]
|-
|[[User:VilleWitt|Ville Witt]]
|developer; Ada, C/C++, Dvorak, [[Java]]
|Getting dirty coding ASAP!
|Naerum & Christiania
|Computer science student(DTU) and Dvorak user.
|[[ Image:Moko.jpg |center]]
|
|-
|[[User:Odlg|Ole Dalgaard]]
|developer; [[Java]],
|GPS + having an open phone
|Hedensted
|Software developer
|[[ Image:Moko.jpg |center]]
|}

=== Meetings, Events ===
{|border=1
!Date
!Location
!Topic
!Who
|}

[[Category:Openmoko Local Groups]]

Openmoko Local Groups: Denmark

2009-01-19T22:19:19Z

VilleWitt: /* Possible Participants */

=== Possible Participants ===
{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
!Has Device
!Has Debug Board
|-
|[[User:Miki|Mikkel Kirkgaard Nielsen]]
|developer; some assembly, C, some C++, Shell scripting, POSIX etc.
|Getting Openmoko (and Neo1973) to rock
|Esbjerg, Østerbyen
|
|[[ Image:Moko.jpg |center]]
|[[ Image:MokoBox.jpg |center]]
|-
|[[User:Mikl-dk|Mikkel Meyer Andersen]]
|developer; C#, C/C++ (is certainly going to be improved with this project)
|Location-based reminding and automatic sms answering among others
|Aalborg
|Computer science student
|[[ Image:Moko.jpg |center]]
|[[ Image:MokoBox.jpg |center]]
|-
|[[User:EsbenDamgaard|Esben Damgaard]]
|developer; [[Python]], C/C++
|Everything ;)
|Odense
|Computer science student
|[[ Image:Moko.jpg |center]]
|-
|[[User:Sorenmat|Soren Mathiasen]]
|developer; [[Java]], C/C++
|Everything ;)
|Roskilde
|Software developer
|[[ Image:Moko.jpg |center]]
|-
|[[User:VilleWitt|Ville Witt]]
|developer; Ada, C/C++, Dvorak, [[Java]]
|FreeRunner in mail!
|Naerum & Christiania
|Computer science student(DTU) and Dvorak user.
|
|
|-
|[[User:Odlg|Ole Dalgaard]]
|developer; [[Java]],
|GPS + having an open phone
|Hedensted
|Software developer
|[[ Image:Moko.jpg |center]]
|}

=== Meetings, Events ===
{|border=1
!Date
!Location
!Topic
!Who
|}

[[Category:Openmoko Local Groups]]

User:VilleWitt

2008-06-27T20:30:40Z

VilleWitt:

'''Ville Johan Witt'''

name[] = {"ville", "johan", "witt"};
email = name[0] + "." + name[2] + "@gmail.com";

I'm a happy Dvorak user, and would like to get/make a Dvorak layout in Openmoko, besides all the other nice stuff that is now possible. I do like the programming language Ada, and is going to play around with it on Openmoko. (Remember, Ada is one of the official languages of GCC...) More about Ada on http://en.wikibooks.org/wiki/Ada

I study Computer Science at DTU.
Prefered desktop: Linux atm (Debian and Ubuntu)
Motorcycle: BMW R25/3, which can be seen on http://www.villewitt.net

User:VilleWitt

2008-05-27T16:35:23Z

VilleWitt:

'''Ville Johan Witt'''

name[] = {"ville", "johan", "witt"};

email = name[0] + "." + name[2] + "@gmail.com";

User:VilleWitt

2008-05-27T16:35:04Z

VilleWitt: New page: '''Ville Johan Witt''' name[] = {"ville", "johan", "witt"}; email = name[0] + "." + name[2] + "@gmail.com"

'''Ville Johan Witt'''

name[] = {"ville", "johan", "witt"};

email = name[0] + "." + name[2] + "@gmail.com"

Openmoko Local Groups: Denmark

2008-05-27T16:31:17Z

VilleWitt:

=== Possible Participants ===
{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
!Has Device
!Has Debug Board
|-
|[[User:Miki|Mikkel Kirkgaard Nielsen]]
|developer; some assembly, C, some C++, Shell scripting, POSIX etc.
|Getting OpenMoko (and Neo1973) to rock
|Esbjerg, Østerbyen
|
|[[ Image:Moko.jpg |center]]
|[[ Image:MokoBox.jpg |center]]
|-
|[[User:Mikl-dk|Mikkel Meyer Andersen]]
|developer; C#, C/C++ (is certainly going to be improved with this project)
|Location-based reminding and automatic sms answering among others
|Aalborg
|Computer science student
|[[ Image:Moko.jpg |center]]
|[[ Image:MokoBox.jpg |center]]
|-
|[[User:EsbenDamgaard|Esben Damgaard]]
|developer; [[Python]], C/C++
|Everything ;)
|Odense
|Computer science student
|[[ Image:Moko.jpg |center]]
|-
|[[User:Sorenmat|Soren Mathiasen]]
|developer; [[Java]], C/C++
|Everything ;)
|Roskilde
|Software developer
|[[ Image:Moko.jpg |center]]
|-
|[[User:VilleWitt|Ville Witt]]
|developer; Ada, [[Java]], C/C++
|Very interested, however awaiting FreeRunner.
|Naerum & Christiania
|Computer science student(DTU) and Dvorak user.
|
|
|}

=== Meetings, Events ===
{|border=1
!Date
!Location
!Topic
!Who
|}
[[Category:Community]]
[[Category: OpenMoko Local Groups| ]]

Talk:Music Player

2007-03-12T00:41:40Z

VilleWitt:

([[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?

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

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

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

Talk:Screen Saver

2007-03-12T00:34:33Z

VilleWitt:

Im not sure if [[Wishlist:Standby_clock]] should be merged with this page. As the ideas seam to be more or less the same. ;)
--[[User:C7|C7]] 05:09, 10 March 2007 (CET)

I beleave "screen saver" is a wrong name - except if it is to save the screen! Call it other things please!!! "Info screen", "Rapid info/data", etc... I beleave it is easier to change early in the development, rather than later!

Wish List - Hardware

2007-03-12T00:12:12Z

VilleWitt: /* Accelerometer */

==Hardware enhancements==

Some small hardware enhancement could be cheap, but very useful. Please add your ideas/wishes here:
 
===Video-capable camera===
* A camera that is able to take reasonable quality video and pictures is something many want. Applications vary from simple snapping, to gesture interfaces, video conferencing, barcode reading and more.

* Some people can't take cameras into work - a model without the camera, or some way of removing the camera would be useful.

===Integrated WiFi hardware===
*To sync data
*To access Internet when WiFi is available (at home, work, school, friends)
*For VoIP (this uses much power but maybe the user have the charger connected)
**I'm willing to port [http://yate.null.ro/ Yate] to it if the Internet connectivity issue is solved --[[User:Csdexter|@Dexter]] 13:58, 16 February 2007 (CET)
*for videoconferencing (as with AccessGrid)
*Even 802.11b 11Mbps -only would do -- the point is being able to connect it to the Internet without incurring the (sometimes huge) costs of GPRS or (even worse) HSCSD.
*To save power have WiFi able to wake up and check for a designated SSID then sleep again if not found (i.e. I'm not home) or wake up by GPS location (only come up at home and in the office)
*Variable TX power, to the minimum needed to connect to the AP.
*Some sort of caching (encrypted?) internet proxy that can store and forward packets. Instead of having the radio constantly on, it turns the radio on every 30s, for just long enough to register with the AP, and ask the proxy if it has new packets for it.
** An optimisation might be if the hardware, and the AP can do broadcast packets. The receiver is only turned on for .5s/30s, to recieve a broadcast packet saying 'you've got packets' without registering with the AP, or transmitting at all. The GPS synchronises the timing.
**This slows the initial connection to the phone, but most tcp/ip applications will not time out in 30s.
*For a cheap, and therefore frequent, access to the global IP Network is vital to a community collaboratively developing such a nice piece of truly open hardware and software.. eg. to share source code and compiled applications directly, and to carry out world wide, community-based communication tests.
*For an affordable Mobile device supporting popular instant messengers over cheap connection would be an irresistible market attractive. Just think about how much this would revolutionize the way people communicate in their WiFi served office area.

===LED===
*A blinking LED would be cheap and low power, good for informing the user about new SMS/Email....
**An alternative to this would be for one segment of the LCD to be seperately backlit. There are many LEDs in the backlight, all normally on. This has the advantage that you can display reasonable amounts of information on the bit of the screen that's illuminated.
**The disadvantage is the field of view is smaller, and it's dimmer than a bare LCD, as the LCD absorbs some light.
**This also requires the CPU and LCD to be somewhat active, to keep it refreshed.

*Note: the LED and button ideas could be combined: illuminated buttons
*A yellow LED for GSM/GPRS Tx burst, a blue one for Bluetooth/WiFi Tx burst, a green one for non-urgent notifications (sleep state, missed call etc.) and a red one for urgent notifications (battery almost drained out, new SMS etc.). All of this could be done in one, multicoloured (RGB) LED, similar to the nice one on the Yaesu VX-7R.

===D-Pad and Buttons===
*Adding a D-pad (to the bottom of the phone) and 2 to 4 buttons (to the top) would provide some tactile input controls, in addition to the touchscreen. They could be used as shortcut keys in the menu, or playback control when playing media. When the phone is held sideways, they can be used as games controls. (With touchscreen alone, gameplay options are limited)

Game buttons would be extremely great especially on both sides of the screen. The larger the buttons, the better. 2x 4 buttons in up-down-left-right configuration + some extra buttons separately a bit lower on the device would be extremely great for emulation games.

===Accelerometer===
This enables the phone to sense where 'down' is - to enable various options.

*[[Wishlist:3D Viewport|3D Viewport]]
*[[Wishlist:Auto Align Map|Auto Align Map]]
*[[Wishlist:Computer Mouse|Computer Mouse]]
*[[Wishlist:Determine Position|Determine Position]]
*[[Wishlist:Distance Measuring|Distance Measuring]]
*[[Wishlist:Dynamic Screen Orientation|Dynamic Screen Orientation]]

Change playlists when I'm jogging vs walking. (there ia an mp3 player on the market that does this).
*Can't the GPS information be used for that purpose? It should be possible to derive the phone's velocity from the change in coordinates over time, so such a playlist profile switcher should be a possibility even now already. [[User:Abraxa|Abraxa]] 00:09, 18 February 2007 (CET)
**Yeah in my opinion that is a very cool idea. But for that case the device should be much lighter. I wouldn't go jogging with a device with this size.--[[User:Denis std|denis_std]] 01:01, 18 February 2007 (CET)
***GPS uses alot of power and GPS signal can be lost. --[[User:VilleWitt|VilleWitt]] 01:10, 12 Marts 2007 (CET)

*Shake mitigation when using the camera (wish list item #1). How many of us end up with blurry pictures because we can't hold the phone steady?
**An accelerometer is not a gyroscope. You can't tell orientation generally from acceleration, only which way 'down' is, which does not help for side-side motion, as the phone can spin around the direction of gravity without any acceleration. Up and down tilting is slightly easier, but it's very hard to determine between shaking of the phone in an up and down axis, and tilting the phone in an up and down axis.
***There are a number of three-axis accelerometer chips on the market. These will be capable of determining most movements. I.e. accelerations in all directions and rotation (change in direction of gravity). Some related research has already been carried out (when three-axis accelerometers were not commonly available, instead using 2 two-axis devices) which shows these kind of movements can be tracked [http://eis.comp.lancs.ac.uk/fileadmin/eis/publication/2004-Towards-Playful-UI.pdf]. [[User:Mwelchuk|Mwelchuk]] 11:02, 26 February 2007 (CET)
*** 3 axis accelerometer does _not_ give orientation information. It gives direction in which the current acceleration is. There are 3 variables to orientation - roll, pitch, yaw, and only two independent outputs from the accelerometer (tilt in two axes at 90 degrees). To get these, you have to assume no acceleration, which is not the case in a shaking hand. Two 2-axis accelerometers, one on either side of the device, do give this information, or at least enough to use the device as a steering wheel. If you place them like this and tilt the device the 2 accelerometers will give opposite readings, if you move the device (translation) they will give the same readings. Simple, no ?
*** The tilt information you get cannot be separated from shaking the phone.
*** Yes it can, just dampen with a filter
*** Consider you are sitting down in a chair. You know which way down is. You cannot, without further information tell if you are spinning round. Down does not move.
*** Obviously it does move : action-reaction : say down is a vector G. If you spin direction D is the tangent to the spinning circle. This tangent will be added to G, and this is the value the accelerometer returns. So you will measure G+D. Knowing this you can easily determine D, as you always measure G somewhere in the accelerometer.

IBM's thinkpad laptops have a demonstration program that actually does this, so obviously it is possible.
--[[User:Speedevil|Speedevil]] 14:10, 26 February 2007 (CET)

===SIR/FIR transceiver (Serial Infrared)===
*An infrared tranceiver is cheap, small, and useful for sync with many laptops and mobile phones. A learning infrared remote is another application.
*Tt could be used to detect when to turn off the display (if the low power IR signal is reflected) and activate the key lock.
*FIR would be a nice option, as it's some 40 times faster than SIR.

===Standard 3.5mm jack===
*I think everyone interested (and knowledgeable) enough to buy a Neo can make a 2.5mm male to 3.5mm female adaptor cable in under 1/2h and under 10EUR :-)

Certainly - now make it light, small, pretty, durable, tangle-free.
I want a 3.5mm jack. The only problem is - are headsets widely available in the same format as 2.5mm. --[[User:Speedevil|Speedevil]] 14:28, 16 February 2007 (CET)

===Multitouch screen===

[[Wishlist:Spell_weaving]]

===Multi I/O adapter===
*VGA, standard Jack (line in & out), standard USB

===MMC/SD/SDIO slot (rather than?) miniSD or microSD===
*Cheaper, more durable cards in a widely accepted format.
*Cards are harder to lose
*Wider selection of accesories, including SDIO accessories.
*Make externally available so that larger length SDIO cards can be used (thinking about SDIO WLAN here)
*Only because CF takes too much room (or CF would be the wish, instead)

===[[Expansion Back]]===
* Replacement backs with additional features
* I believe this would be a great idea, if put into practice. It would solve the ''extensibility'' need, usually associated with Open Source projects. It would allow for lots of other devices and for functionality to be developed and put into use without making it a burden for FIC.
** With extra card slots and small footprint hard drive (if possible), Neo might become a nice ''image tank'' for photographers - --[[User:Cedel|cedel]] 18:34, 19 February 2007 (CET)

===Thumb keyboard or keyboard attachment accessory===
*Could be slide out or clamshell (hinge on long side) design with an external OLED. The keyboard should be protected when not in use.
*Could be a clip on keyboard that attaches to the serial port or communicates by bluetooth (not preferred for permanent keyboard users).
*cheap clippable miniusb keyboard

===EDGE support===

EDGE support would allow better transfer rates than non-EDGE 2G, which is limited around 5 kB/s, thus enabling a real internet connectivity for the use of (mostly geographical-based) web services.

===HSDPA support===
[http://en.wikipedia.org/wiki/HSDPA HSDPA] is currently the most popular 3G Mobile Telephony Network Protocol in Southeast Asia. It runs at a theoretical 384kbps uplink / 1.6mbps downlink.

A thought: is HSDPA worth doing while we're also going for Wifi / WiMax / WiBro? And another: is doing Wifi / Wimax / WiBro worth it considering low deployment in Asia? How 'bout doing both Wifi and 3G, is it worth it or not?

===Ability to insert more than one Sim-Card and (if possible) connect to more than one network at the same time===

* This could be achieved via a specialist dual sim card kit (currently on market)- where two sims are trimmed and combined on one card, software support for dual sims would need providing...
* What about twin-SIMs (SIMs with 2 phone lines registered on them)? Conventional GSM phones have an option to switch between the two, older ones use # (long press before dialling) to do that. I'm guessing Calypso should support it, we just need to provide an interface for it :-) --[[User:Csdexter|@Dexter]] 11:34, 19 February 2007 (CET)

===RFID tag===
* Implementation/Cooperation with: [http://www.rfidguardian.org/ RFID-Guardian]
*Advantages of a RFID tag? I would see a lot privacy problems
**The tag could be switched on or off. A nice feature would be a module able to clone tags. This would unfortunately probably be rather expensive.
**What about an RFID Reader which could be used to locate items with RFID tags (IE: in your house) [[User:Alexpb|Alexpb]]
***That would be a nice feature--[[User:Denis std|denis_std]] 08:33, 17 February 2007 (CET)
***Most tags can only be located within 10cm or so. Essentially no cheap tags can be located over several metres.--[[User:Speedevil|Speedevil]] 13:17, 18 February 2007 (CET)

=== USB ===
* USB 2.0
* Powered
** Power is a scarce resource in a mobile device as it stands. Why would anyone expect a '''powered''' USB port on a smartphone?!
--[[User:Csdexter|@Dexter]] 13:17, 28 February 2007 (CET)
***Simply because pocket space is also a scarce resource. Being able to plug in for a moment a camera, flash reader, or ... is a valuable thing. Also, many powered hubs will not recognise a totally unpowered host.
* OTG (is this maybe supported already ?)
* Bootable USB device emulation: the possibility to boot any computer on a bootable flagged partition of the transflash

===UMTS support===

===Speakerphone===
* The Neo1973 already supports that in hardware (routing GSM audio to the loudspeakers). Could someone delete this wishlist item then? --[[User:Csdexter|@Dexter]] 13:14, 28 February 2007 (CET)
* Unfortunately, speakerphone is more than simply connecting the speakers to GSM audio, it's also echo cancellation, and eliminating the feedback that will otherwise happen between the speakers and the mic.

===Special covers===
* 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)

===Video acceleration===
Hardware acceleration for video playback.

===3D acceleration===
3D hardware acceleration for 3D games, GUIs, etc. (maybe a PowerVR MBX Lite ?).

===HMD===
Possiblity to use something like [http://www.aeinnovations.com/projects/ver0/ Eyeglass Mounted Display].

===EPD===
Or electronic paper display, EPD is used in many new devices such as the new Motorola motofone, sonys new e-reader and Irex's iliad. The technology provides thin, flexible, power saving screens using new eink technology. This technology could cut the weight of the phone and its power usage. For more info see: [http://www.eink.com eink's website].

===FM/Digital Radio(DAB) Reciever===
A nice feature would be a radio reciever: FM or even better: [http://en.wikipedia.org/wiki/Digital_Audio_Broadcasting Digital Audio Broadcast] (Digital Radio)

===Thermometer===
An electronic thermometer might become handy for some users.

There are very small [[I2C]] devices available, that could easily integrate to the existing bus. For example [http://focus.ti.com/docs/prod/folders/print/tmp100.html this one from ti].

===I2C breakout===
[[I2C]] is an internal bus in the phone. This is a simple bus, with only 2-3 wires, hence ideal for making accessible to those making add-ons, as it is low powered, and can be daisy-chained. It would be a great candidate to bring out into the [[Expansion Back]].

Readily available [[I2C]] chips range from temperature sensing, digital input/ouput chips, to 1-wire bridge chips (which is designed for external switches, ID, sensing, ...)

===Finger print sensor===
Fingerprint sensor gives easy and fast access to the phone, could lock the touchscreen etc. An example of this device can be found at [http://www.sonystyle.com/is-bin/INTERSHOP.enfinity/eCS/Store/en/-/USD/SY_BrowseCatalog-Start?CategoryName=cpu_VAIONotebookComputers_UX_Series&Dept=computers Sony UX17].

As these are typically implemented with a small camera (256*4) focussed on the finger, with appropriate hardware and software, you can also use them as an optical mouse in reverse, detecting movement of the finger over the sensor.

===Trackball===
A trackball would provide an efficient mouse-like interface in a very compact package. As exemplified in the newer Blackberry® models.

===Analog Joystick===
How 'bout an analog joystick, gaming-console style, instead of a D-Pad or a trackball?

Or how 'bout a [http://www.extremetech.com/article2/0,1697,1772689,00.asp Rollermouse]-like device? But do we need any of this, considering the touchscreen?

--[[User:Lemi4|Lemi4]] 19:03, 11 March 2007 (CET)

===Laser Pointer===
Include a built in laser pointer. Everything is better with lasers.

==Ideas that will probably never be implemented==
[[Wishlist:Unlikely]]