Openmoko - User contributions [en]

Getting Started with your Neo FreeRunner

2008-07-10T12:10:23Z

Tommy: /* Charging the Neo Freerunner */ Added title.

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

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

== The Package Contents ==

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

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

==Getting To Know the Neo FreeRunner==

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

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

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

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

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

===Turning on the Neo Freerunner===

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

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

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

====Booting the Neo Freerunner====

You can boot your Neo FreeRunner in the following ways:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

3. Set console to USB

4. Set console to Serial

5. Reset

6. Power off}}

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

===Unlocking the screen===

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

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

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

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

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

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

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

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

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

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

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

ex:

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

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

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

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

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

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

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

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

When flashing succeeds the following will be shown:

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

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

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

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

ifconfig usb0 192.168.0.200 netmask 255.255.255.0
ssh root@192.168.0.202

Press Enter to get by the password.

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

auto usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0

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

config_usb0="192.168.0.200/24"

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

ssh root@192.168.0.202

Press Enter to get by the password.

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

192.168.0.202 openmoko

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

ssh root@openmoko

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

=====Sharing your Internet connection via USB=====
In Ubuntu:

Within /etc/network/interfaces, change your interface setup to this:

auto usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
up echo 1 > /proc/sys/net/ipv4/ip_forward &
up iptables -P FORWARD ACCEPT &
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &

Then, on your Freerunner, edit /etc/
and modify the code from this:

iface usb0 inet static
address 192.168.0.202
netmask 255.255.255.0
network 192.168.0.0
gateway 192.168.0.200
up echo nameserver 192.168.0.200 > /etc/resolv.conf

to something that points to a real name server, like a public DNS system from OpenDNS, like this:

iface usb0 inet static
address 192.168.0.202
netmask 255.255.255.0
network 192.168.0.0
gateway 192.168.0.200
up echo nameserver 208.67.222.222 > etc/resolv.conf
up echo nameserver 208.67.220.220 >> /etc/resolv.conf

==Un-crippling the 2007.2 image==

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

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

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

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

To test GPS, you can use agpsui:

# opkg install openmoko-agpsui

For a nice map, try tangoGPS:

# opkg install tangogps

And if you want the Media Player back:

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

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

# opkg install gpe-icons gpe-gallery

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

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

[[Category:GTA02 Hardware]]

U-Boot commands

2008-02-17T21:26:39Z

Tommy: /* Neo1973 specific commands */ spelling

Various tasks are performed with bootloader commands. On the [[bootloader]] console, you can list the available commands with "help", and get more information about each command with "help command".

== Auto-boot ==

Auto-boot executes the command[s] specified in the ''bootcmd'' environment variable. The default configuration is:
<pre>
GTA01Bv3 # printenv
bootcmd=setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel; bootm 0x32000000
</pre>

This basically tells us that it will load the content of the NAND [[partition]] '''kernel''' to memory address 0x32000000 and then try to boot it.

== Environment ==

:''See also [[bootloader environment]].''

u-boot is configured to manage a non-volatile environment that is stored in the NAND flash [[partition]] named "u-boot_env". u-boot itself gets the location from OOB. You have commands to display, alter, and store the environment.

This displays all definitions in the current environment:
<pre>
GTA01Bv2 # printenv
baudrate=115200
bootargs=rootfstype=jffs2 root=/dev/mtdblock4 console=ttySAC0,115200 console=tty0 loglevel=8 dyntick=enable lpj=252416
usbtty=cdc_acm
bootdelay=10
stdout=serial
stderr=serial
stdin=serial
mtdparts=mtdparts=neo1973-nand:0x00030000(u-boot),0x0000c000(u-boot_env),0x00200000(kernel),0x00130000(splash),0x03c94000(rootfs)
mtdids=nand0=neo1973-nand
bootargs_base=rootfstype=jffs2 root=/dev/mtdblock4 console=ttySAC0,115200 console=tty0 loglevel=8 dyntick=enable lpj=252416
bootcmd=setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel; bootm 0x32000000
pcf50606_int1=0x40
filesize=160C000
partition=nand0,0
mtddevnum=0
mtddevname=u-boot
Environment size: 670/16380 bytes
GTA01Bv2 #
</pre>

The following example shows how to manipulate an individual definition, and store the updated environment in flash:
<pre>
GTA01Bv3 # setenv bootdelay 10
GTA01Bv3 # printenv bootdelay
bootdelay=10
GTA01Bv3 # saveenv
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
GTA01Bv3 #
</pre>

Note: When setting multiple commands, e.g. for bootcmd, you need to escape the ';', for instance:

<pre>
GTA01Bv3 # setenv bootcmd mmcinit\; ext2load mmc 0 0x32000000 uImage\; bootm 0x32000000
</pre>

== MMC/SD ==

in order to initialize a MMC/SD card, you have to use the ``mmcinit'' command.
<pre>
GTA01Bv3 # mmcinit
trying to detect SD Card...
MMC found. Card desciption is:
Manufacturer ID = 58d564
HW/FW Revision = 3 8
Product Name = 21DN!@X�
Serial Number = 445303
Month = 5
Year = 2000
READ_BL_LEN=15, C_SIZE_MULT=7, C_SIZE=3197
size = 4208984064
GTA01Bv3 #
</pre>

afterwards, you can read ext2 filesystems like:
<pre>
GTA01Bv3 # ext2ls mmc 0
<DIR> 1024 .
<DIR> 1024 ..
<DIR> 12288 lost+found
1544788 uImage
</pre>

== NAND ==

<pre>
GTA01Bv3 # help nand
nand info - show available NAND devices
nand device [dev] - show or set current device
nand read[.jffs2] - addr off size
nand write[.jffs2] - addr off size - read/write `size' bytes starting
at offset `off' to/from memory address `addr'
nand erase [clean] [off size] - erase `size' bytes from
offset `off' (entire device if not specified)
nand bad - show bad blocks
nand dump[.oob] off - dump page
nand scrub - really clean NAND erasing bad blocks (UNSAFE)
nand markbad off - mark bad block at offset (UNSAFE)
nand biterr off - make a bit error at offset (UNSAFE)
</pre>

=== Loading Kernel from NAND ===

<pre>
GTA01Bv3 # nand read 0x32000000 kernel

NAND read: device 0 offset 212992, size 2097152 ... 2097152 bytes read: OK
GTA01Bv3 # bootm 0x32000000
## Booting image at 32000000 ...
Image Name: OpenMoko Kernel Image Neo1973
Created: 2007-02-15 23:54:18 UTC
Image Type: ARM Linux Kernel Image (gzip compressed)
Data Size: 1546258 Bytes = 1.5 MB
Load Address: 30008000
Entry Point: 30008000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting kernel ...
</pre>

=== Writing new bootloader to NAND ===

The following set of commands loads the file u-boot.bin from ext2/mmc and flashes it into the
bootloader flash [[partition]]:

<pre>
GTA01Bv3 # ext2load mmc 0 0x32000000 u-boot.bin
GTA01Bv3 # nand erase u-boot
GTA01Bv3 # nand write.e 0x32000000 u-boot ${filesize}
</pre>

=== Writing kernel to NAND ===

The following set of commands loads the file uImage from ext2/mmc and flashes it into the
kernel flash [[partition]]:

<pre>
GTA01Bv3 # ext2load mmc 0 0x32000000 uImage
GTA01Bv3 # nand erase kernel
GTA01Bv3 # nand write.e 0x32000000 kernel ${filesize}
</pre>

=== Writing rootfs to NAND ===

The following set of commands loads the file rootfs.jffs2 from ext2/mmc and flashes it into the
rootfs flash [[partition]]:

<pre>
GTA01Bv3 # ext2load mmc 0 0x32000000 rootfs.jffs2
GTA01Bv3 # nand erase rootfs
GTA01Bv3 # nand write.e 0x32000000 rootfs ${filesize}
</pre>

Please note that this will only work with root file system sizes that are smaller than the amount of memory above 0x32000000, which in the case of 64MB SDRAM is something like 32MB. '''Warning''': you risk bricking your phone if you attempt to read in too large a file as extload appears to write the overflow into dangerous parts of memory address space.

== Neo1973 specific commands ==

Our version of u-boot supports a couple of Neo1973 specific commands:
<pre>
GTA01Bv4 # help neo1973
neo1973 neo1973 info - display phone information
neo1973 power-off - switch off the phone
neo1973 charger status - display charger status
neo1973 charger autofast - enable automatic fast (500mA) charging
neo1973 charger !autofast - disable automatic fast (500mA) charging
neo1973 charger fast - enable fast (500mA) charging
neo1973 charger off - disable charging
neo1973 backlight (on|off) - switch backlight on or off
neo1973 led num (on|off) - switch LED number 'num' on or off
neo1973 vibrator (on|off) - switch vibrator on or off
neo1973 gsm (on|off|version) - switch GSM Modem on/off or print firmware version
neo1973 gps (on|off) - switch GPS system on or off
neo1973 udc pullup (on|off) - switch USB device controller pull-up on or off
</pre>

=== Info ===

Using
GTA01Bv4 # neo1973 info
FIC Neo1973 Hardware Revision 0x0240
GTA01Bv4 #

you can display hardware reference and revision

=== Power-off ===

Using
neo1973 power-off

you can switch the device off from the bootloader prompt.

=== Battery charger related ===

For a detailed description of the charger basics, see [[Neo1973 Battery Charger]].

==== Inquiring the charger state ====

You can get the current charger status by issuing
neo1973 charger status

The following modes are possible:

* idle - no charging
* trickle - FIXME
* pre - Slow (100mA) charging, works in hardware.
* fast_cccv - Fast (500mA) charging, using Constant-Current followed by Constant Voltage (Li-Ion)

==== Disabling battery charging ====

You can disable battery charging (until the next reboot) by issuing
neo1973 charger off

==== Forcing fast charge ====

Using
neo1973 charger fast
you can force the PMU to try to do a fast (500mA) charge of the battery. It will abort if the battery is in over temperature or some other error condition occurs.

The following commands will add a boot menu entry that switches to fast charging and turns off the backlight:
setenv menu_6 Fast-Charge and Backlight Off: neo1973 charger fast\; neo1973 backlight off
saveenv

While in this state, your Neo1973 can be charged with a generic USB charger. You also need to set
setenv boot_menu_timeout 65000
saveenv
to keep it from powering down, though.

==== Enabling / Disabling automatic fast charge ====

Autofast is a feature of the PCF50606 PMU. It means that the fast_cccv mode will be automatically selected if a charger with suitable voltage is plugged in, and the battery not in over temperature condition.

{{warning|This is potentially dangerous. Only enable autofast if you ARE SURE that you can draw 500mA from the USB connector. This is the case with a wall outlet charger, or if you are attached to a self-powered hub or a desktop PC root hub. Bus powered hubs and some laptops only provide 100mA on their USB ports and can thus not support fast charging}}

You can enable or disable autofast by
neo1973 charger autofast
and
neo1973 charger !autofast
respectively.

=== Backlight ===

You can switch the backlight on and off by using
neo1973 backlight on
and
neo1973 backlight off
respectively.

=== Vibrator ===

You can switch the vibrator on and off by using
neo1973 vibrator on
and
neo1973 vibrator off
respectively.

=== GSM ===

Starting with OpenMoko patchset '''SVN revision 2885''', u-boot contains support for powering the GSM modem,
and even accessing the modem from the console.

==== GSM power ====

You can switch the GSM modem on and off by using
neo1973 gsm on
and
neo1973 gsm off
respectively.

==== terminal mode ====

You can access the GSM modem using openmoko's built-in terminal emulator in u-boot.

The following example demonstrates how:

<pre>
GTA01Bv4 # neo1973 gsm on
GTA01Bv4 # terminal serial
switching s3ser0 from console into GSM mode
Entering terminal mode for port serial
Use '~.' to leave the terminal and get back to u-boot
ATE1
OK
AT+CGMI?
ERROR
AT+CGMI
FIC

OK
AT+CGMR
GTA01Bv4

OK
~[u-boot]~.
switched s3ser0 from GSM mode back into console mode
GTA01Bv4 # neo1973 gsm off
GTA01Bv4 #
</pre>

{{note|If you're using the ''cu'' terminal emulator on your host PC to access u-boot, you have
to press '~' twice in order to escape it and make sure it actually gets sent to the Neo!}}

== S3C2410 specific commands ==

<pre>
GTA01Bv2 # help s3c2410
s3c2410 speed get - display current PLL speed config
s3c2410 speed list - display supporte PLL speed configs
s3c2410 speed set - set PLL speed
GTA01Bv2 # s3c2410 speed list
50 MHz
101 MHz
202 MHz
266 MHz
GTA01Bv2 # s3c2410 speed get
FCLK = 202 MHz, HCLK = 101 MHz, PCLK = 50 MHz
GTA01Bv2 # s3c2410 speed set 101
GTA01Bv2 # s3c2410 speed get
FCLK = 101 MHz, HCLK = 50 MHz, PCLK = 50 MHz
</pre>

=== 266MHz clock ===

You can re-configure the [[S3C2410]] PLL to generate a 266 MHz core cpu clock (rather than the 200MHz default) by using
GTA01Bv2 # s3c2410 speed set 266
and
GTA01Bv2 # s3c2410 speed set 202
respectively.

{{warning|The old hardware (Phase 0 - GTA01Bv3) only runs stable at 266MHz if you do not attach anything (esp. the FPC / [[Debug Board]] to the Debug Port}}

{{note|New U-Boot (at least the svn3817 I use at now) use a new command 'S3C24xx', I assume for consistency when using GTA02}}

== TFTP on QT2410 ==

The QT2410 cs8900a Ethernet can be used to download images via network.

First, you have to make sure that ''ipaddr'', ''serverip'', ''ethaddr' and ''netmaskk'' are set correctly in the environment:

<pre>
QT2410 # printenv
ethaddr=00:01:02:03:04:05
netmask=255.255.255.0
ipaddr=192.168.100.100
serverip=192.168.100.1
</pre>

=== TFTP kernel download ===

<pre>
QT2410 # tftpboot 0x32000000
*** Warning: no boot file name; using 'C0A86464.img'
TFTP from server 192.168.100.1; our IP address is 192.168.100.100
Filename 'C0A86464.img'.
Load address: 0x32000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
##########################################
done
Bytes transferred = 1544788 (179254 hex)
</pre>

you can then commence booting via
<pre>
QT2410# bootm 0x32000000
</pre>

Neo FreeRunner

2008-02-09T16:21:58Z

Tommy: /* What are the specs */ Corrected language.

The Neo FreeRunner (internal codename GTA02) is the second phone designed to run Openmoko software and is the direct descendant of the earlier [[FIC]] [[Neo1973]]. It has not yet been released - if you want to buy an Openmoko phone now then see the [[Neo1973]].

=== Finding out status before FreeRunner is released ===

To be emailed when it is released sign up to the announce mail list here http://lists.openmoko.org/mailman/listinfo/announce. For frequently asked questions please check [[FAQ]]. Approximately, twice a month an Openmoko team member writes an update to the project here [[Community Updates]].

No official launch date will be given until the phone is ready.

=== Intended use and users ===

The Neo FreeRunner is a linux based touch screen smart phone aimed at general consumer use as well as linux desktop users and linux software developers.

General phone users will appreciate the high spec and performance of the phone and the wide range of free and custom software packages that you are free to install to make the maximum use of the hardware for your particular needs. Note that software tweaks and improvements will continue after launch as both the Openmoko team developers and the wider linux community work together.

Linux users and software developers will appreciate the total freedom they have to use and design software for the FreeRunner

=== What are the specs ===

The specs share some features with the previous [[Neo1973]] such as

* A very high resolution touch screen (1.7" x 2.27" - 43mm x 58mm) 480x640 pixels
* 128MB SDRAM memory to allow operation of many applications at once
* Internal GPS module for map and tracking programs
* Bluetooth for local data exchange
* Physical appearance will be the same as the Neo1973. See openmoko.com for more.

but will gain the additional features of

* 802.11 b/g WiFi for fast web browsing and data transfer
* A faster 400Mhz processor (up from 266MHz)
* A hardware Graphics Accelerator chip allowing fast graphics including video playback
* 2 accelerometers so that the phone can know its orientation for example switching to landscape mode automatically
* 2 LEDs illuminating the two buttons on the rim of the case
* Tri-band GSM and GPRS for North America (850/1800/1900 Mhz) and the rest of the world (900/1800/1900 Mhz)
* USB Host function with 100mA power allowing you to power USB devices for short periods (will drain the FreeRunner battery faster)

A full list of the hardware specs and components of the Neo FreeRunner (internal codename GTA02xxx) can be found here [[Neo FreeRunner GTA02 Hardware]]

A comparison between Neo 1973 and Neo FreeRunner is [[Neo1973: GTA01Bv4 versus GTA02 comparison|here]]

=== What is the price? ===

It will be available in two versions
* FreeRunner Base (for almost all users) and
* Freerunner Advanced (for some software developers).
Further details to follow

We will sell this device through multiple channels. Direct from openmoko.com, the price will be $450 for the FreeRunner Base and $600 for the FreeRunner Advanced.

Hardware:Neo1973:Alternate Cases:Solar power

2008-01-21T21:49:15Z

Tommy:

Alternate case for the Neo1973, with a solar panel for recharging the battery.

==Design options==
The panel could be mounted on some or all of the six sides of the phone, depending upon the amount of power needed, the environment and the power produced by the panel.

==Rendered images==

==3D model==

==Materials==

==Processes==
Stereolithography

==Components==
Solar panel

==Interest==
Leave your nickname here if you are interested in having one made. This is not an order form, but is intended to gauge interest before effort is expended designing the case.<br>

{|
!No !! Nick !!
|-
|1. [[User:Tetraden|Tetraden]]
|-
|2. [[User:ruskie|ruskie]]
|-
|3. [[User:Denis std|Denis]]
|-
|4. [[User:sin|sin]]
|-
|5. [[User:Filippo|Filippo]]
|-
|6. [[User:Deedend|Deedend]]
|-
|7. [[User:Wedge|Wedge]]
|-
|8. [[User:Fradeve11|Fradeve11]]
|-
|9. [[User:Aeshaettr|Aeshaettr]]
|-
|10. [[User:Madoon|Madoon]]
|-
|11. [[User:larstobi|larstobi]]
|-
|12. [[User:KlaymenDK|KlaymenDK]]
|-
|13. [[User:oz1lln|oz1lln]]
|-
|14. [[User:Aztlek|Aztlek]]
|-
|15. [[User:Kelvan|Kelvan]]
|-
|16. [[User:Tommy|Tommy]] That would be wonderful. I'd rather buy a first version without the solar panel quick and then also buy the next version, than have to wait even more if you were to include the solar panel on the first mass market version. But if you could hire someone else to do it for you and the decision would only affect the price and not the release date I would want you to include it in the first mass market version.
|}

[[Category:Neo1973_alternate_cases]]

GPS Sight

2008-01-21T21:42:25Z

Tommy: Corrected language and spelling.

[[Image:Gpv 0 0 screen shot.png|frame|right|The program, running on the mobile phone, but visible on a desktop machine via X. As GPS does not work indoors, only the time field shows the value]]
The GPS preview is a GTK based project to create a usable GUI tool with the simple output (no maps). It is built and tested around the gllin driver but should work with any other driver via pipe at /tmp/nmeaNP. It detects GPRMC and GPGGA messages and constantly shows the following data on the screen:

* Location.
* Speed in kilometers per hour (converts from knots).
* Altitude
* Curved distance from the initially marked point (uses advanced IERC 2003 geodetic reference to convert degrees into kilometers).
* Number of the satellites.
* Time (UTM, not a local time).

The source code of this project is available in the project page (http://projects.openmoko.org/projects/gpv/), under LGPL. The project uses GTK framework and C programming language.

The most interesting part of this project was to keep the external driver thread and GUI thread sufficiently happy together. We cannot just read from the pipe in a loop as this blocks the GUI repainting! Instead, the code schedules the GTK timer, and then it needs to check if any input from the pipe is available - again, without blocking the current thread for too long. This is done using select function which can check the given stream for the availability of input, passing the certain time-out duration. This time-out seems also tricky: if the value or 0.1 s or less is passed on the Neo, function never reports any input present. However too large values block GUI in the input check step. The code now has a kind of adaptation, gradually increasing the duration of this check if there is no input available for a while.

The GPS Preview program (gpv) is released either in .ipk file or in the form of the source code. The released installer still needs the gllin to run, but, if needed, can start it itself.

[[Category:GPS]]

FAQ

2008-01-08T17:36:53Z

Tommy: /* Q: What will it do? */ Release date is not March 2008. It is "spring of 2008".

Frequently Asked Questions... with answers included!

==Introduction==

=== Q: What is OpenMoko? What is Neo1973? ===
A: [[OpenMoko]] is a software platform, an attempt to create the world's first completely open mobile phone software stack. The [[FIC]] [[Neo1973]] is the first fully supported OpenMoko phone.

=== Q: I'm a ____ expert, can I join/help OpenMoko? ===

We would love to hear from you.

If you are interested in joining OpenMoko, please visit http://www.openmoko.com/contact-index.html and send us an e-mail. Or simply post a message to our community list if you just want to help.

=== Q: When can I buy a [[Neo1973]]? ===

A: Now - from https://direct.openmoko.com/. But please see "What will it do?" below first.

=== Q: Where can I buy a [[Neo1973]]? ===

How do I buy a cell phone that runs Linux?[http://blog.syntaxpolice.org/isaac/technology/linuxPhones.html]

A: From https://direct.openmoko.com/. But please see "What will it do?" below first.

=== Q: How much? ===

A: Neo1973 GTA01B_v04: $300 for Neo Base, $399 for Neo Advanced. Available now. See [[Neo1973]] for what is included.

A: Neo1973 GTA02: $450 for Neo Base, $600 for Neo Advanced. Planned to be available March 2008. See [[Neo1973]] for list of hardware.

=== Q: What will it do? ===

A: For long answer see [[Developer preview]]

A: The Phase 1 phone is aimed at developers only. It is not suitable for end users, it will have basic functionality as a touchscreen phone. Little else will work, software development will continue till mass market release.

Those interested should:

* Know that there will be a device with faster cpu, gsm system etc in the spring of 2008.
* Have fun hacking devices.
* Be able to find their way through prototype software and hardware without much documentation.
* Share the dream of a device powered by free software.
* Not expect a consumer-level device.
* Come up with new ideas for exploring the age of mobile computing.
* Have $300.

Ideally they also:

* Can spot bugs and submit patches.
* Love to cooperate with a community improving the software.

=== Q: Do I need Neo Advanced? ===

With Neo Base you can do:
* Kernel development.
* Application development.
* Updating u-boot (equivalent to PC BIOS) using a tested image.
* Replace a non-booting kernel and/or rootfs using [[Dfu-util]].

With Neo Advanced you can additionally do:
* U-boot development.
* Use the kernel console.
* Unbrick your device if you flash a wrong or non-working u-boot image.

=== Q: I have a shipping related question ===

See [[SH1_FAQ|Shipment 1 FAQ]].

=== Q: What will the [[Neo1973]] look like? ===

See the proposed [[Artwork|artwork]].

==Software==

=== Q: Can the software do/connect to/... ===
A: At the moment, the answer is in almost all cases no. The phone is at the moment a small linux box with a touchscreen, a working dialer and some prototype apps.
Most do not function in any way that would be suitable for users.
If you want to add a feature or application request, then look over the existing applications and either add one, or add a feature request to the applications page.

===What software is on the phone?===
At the moment, almost no 'end-user' applications are present and working in a usable state.
It is possible to make and receive calls in some software revisions, this frequently breaks though.

====What software can be installed on the phone?====

=== Q: Is there description and list of OpenMoko software? ===

A: See [[OpenMoko]] and [[OpenMokoFramework]]

=== Q: Is it completely free software/open source? ===

A: User space [[Gpsd]] will use binary plugin (to be released soon) for [[:Category:Neo1973 Hardware#AGPS|Hammerhead AGPS]] and [[:Category:Neo1973 Hardware#GSM.2FGPRS|GSM modem]] is separate subsystem connected to S3C2410 UART1. Otherwise it is completely free software. See [[MokoMakefile]] and [[Development resources]].

=== Q: How do I install and manage software on OpenMoko? ===

A: ipkg: http://handhelds.org/moin/moin.cgi/Ipkg

=== Q: How can I compile programs for the Neo1973? ===

A: See [[Toolchain]].

=== Q: Is there an emulator available for OpenMoko? ===

For a lot of testing and development work, you don't actually need emulation as you can run OpenMoko on a normal PC too. The emulators also aren't 100% accurate. That being said, there are several emulation options as described in the following.

====QEMU====
QEMU can now emulate the Neo1973 device. The [[MokoMakefile]] has support for automatically building, flashing, and running [[OpenMoko under QEMU|the Neo1973 emulator]].

“make qemu” will build qemu-neo1973, download the latest official openmoko images, flash the images into the virtual NAND flash, and run the emulator.

====Xoo====
Another is [http://projects.o-hand.com/xoo Xoo]. Koen says: "Xoo should be enough for most apps people will develop, since most don't need access to the gsm uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".

Update: Stefan Schmidt has resized the [[Neo1973]] Mock-up and written a small description for xoo. In his words:

It's not really useable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.

http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2

Start with 'xoo --device /path/to/neo1973.xml'

Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].

====Xephyr====
Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):
Xephyr -screen 480x640 -nolisten tcp -ac :1 &
export DISPLAY=:1
export LD_LIBRARY_PATH=/usr/local/lib
matchbox-window-manager -display $DISPLAY -use_titlebar no \
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \
-use_cursor yes &
matchbox-panel --geometry=480x44 --end-applets=clock &
openmoko-footer &
openmoko-taskmanager &

=== Q: Where can I find some type of tutorial for a 'Hello, world' on OpenMoko? ===

A: This should get you started:
http://www.gtk.org/tutorial/

=== Q: Can PalmOS apps applications be ported to run on OpenMoko? ===

A: Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux
is decidedly non-trivial.

PalmOS apps are in general very hard to simply 'port'. Particularly well-designed programs may make it possible.

The ACCESS Linux Platform will include Garnet on Host (GHost), a PalmOS emulator that will support M6800 (68k) and ARM PalmOS applications. This part (GarnetVM and the .prc loader) will however be closed-source and likely under a restrictive license (fact confirmed by ACCESS Co. employees), making it rather unusable. In addition GarnetVM depends on Hiker and other packages.

It is possible that POSE, an emulator that simulates a Palm device on a Linux host could be used to allow 68k based applications to run. This emulator has been around a long time; one expects that it will also run on OpenMoko, but this has to be considered a short-term bandaid rather than a long-term solution.

The soon-to-be-released [http://www.palm.com/foleo/ Palm Foleo], which runs a Linux port developed by Palm Inc. independently of ALP, contains a PalmOS compatibility environment that runs PalmOS apps, supposedly all of them and supposedly seamlessly. Little is known about how it works but if it's not too kludgy it should run unmodified on any ARM linux. It is not known what license it will be distributed under.

Hopefully emulation will be necessary only for M68000 code (pre-PalmOS 5) while native ARM programs can run natively under Linux, provided a proper set of PalmOS libraries and a .prc executable loader.

=== Q: Does it have Java? ===
A: It will have eventually, if you help us to get it working. Some good places to keep track of would be [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] and [https://phoneme.dev.java.net/ PhoneME].

Project [[https://wiki.evolvis.org/jalimo/index.php/Jalimo Jalimo]] is a project aiming to provide a Java stack on mobile devices. This project supports OpenMoko.

=== Q: What are the relevant X11 details? ===

A: See [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].

=== Q: Does OpenMoko run on any other hardware? ===

You can run it on your [[How_to_run_OpenMoko_Apps_on_PC|PC]]. There is work going on with [http://www.datenfreihafen.org/~stefan/weblog//archives/2007/02/#e2007-02-18T15_27_07.txt OpenEZX and HTC]. It's running on [http://dominion.kabel.utwente.nl/koen/cms/openmoko-running-on-an-ipaq iPaq hx4700], on a [http://hackndev.com/node/701 Palm TX] and on [http://blog.mikeasoft.com/2007/07/01/openmoko-on-a-treo-650/ PalmOne's Treo 650].

=== Q: What are the requirements to the hardware to run OpenMoko? (Would it run on the IXI ogo?) ===

=== Q: Why do you not build on top of the Maemo platform instead? ===

While I can't speak for the OpenMoko team, it's worth noting that maemo is fixed resolution only. That will, I've heard, change in the future, but it hasn't yet. Maemo's current layout is also optimized for wide screens, not tall narrow ones. Most third party maemo applications that are out there will need to be modified to work at different sizes. Finally, a number of the software components of the Nokia 770 and N800 are not open source. --gopi

To add up on that, according to Nokia, Maemo is designed to bring the "Desktop" experience to an Internet Tablet. A lot of Desktop paradigms just won't work on a phone. However, we really share a lot of the base-technology (gtk, dbus, eds, gconf, to name a few) with Maemo, so we are definitely not a reinvent-the-wheel team.

=== Q: Will it be possible to use popular VoIP applications such as Skype on the OpenMoko platform? ===

A: Perhaps. Hardware issues mean that it won't work well on the Neo1973. (the typical latency of GPRS is far too high). Also, Skype is a closed source application, which does not provide binaries that would be suitable to run on OpenMoko. Skype's vendor could of course choose to provide binaries for OpenMoko phones. However, many telephone providers' terms of service agreements preclude running VoIP over their baseline GSM service.

=== Q: Same question for Instant Messaging applications such as MSN Messenger? ===

A: Very probably. MSN is closed source and will only run where Microsoft wants you to run it. But there are many Open Source IM clients, many of which have a plugin architecture and so support the use of more than one IM protocol, even simultaneously. One example is [http://www.pidgin.im Pidgin, formerly called GAIM]. GPRS does induce a certain amount of latency but that should not be a problem for simple, text-oriented chat between parties. And the GTA02's WiFi will make it even better.

==Neo1973 Hardware==

=== Q: Is there description of [[:Category:Neo1973 Hardware | Neo1973 Hardware]] ? ===

A: See [[:Category:Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]]

=== Q: What are the dimensions? ===

A: 120.7 x 62 x 18.5 mm, It would fit entirely in a coke can. (4.75 * 2.4 * 0.72 ")

=== Q: How heavy is it? ===

A: 185g, (6.5 ounces).

=== Q: Does it have a camera? ===

A: No, see [[:Category:Neo1973 Hardware | Neo1973]] for details on what it does include (and [[Wish List - Hardware]] for what some want in the future.) See also [[FAQ#USB]].

=== Q: Does it have Wifi? ===

A: The currently available [[Neo1973]] does not have WiFi. There was no suitable Wifi device available when it was designed. The next version will have WiFi. See also [[FAQ#USB]].

=== Q: Does it have bluetooth? ===

A: Yes! Bluetooth 2.0.

=== Q: Does it come with a stylus? ===

A: Yes, but there's no holder for it on the phone.

=== Q: Where are the buttons? ===

[[Neo1973 Power Button|The power button]] is a small circular button, just next to the USB connector.
[[Neo1973 AUX Button|The Auxiliary button]] is a rectangular button on the top left of the edge of the phone. (on black phones it looks just like an IRDA port).

=== Q: How do I input text? ===

A: Use provided keyboard app.

A: Use Bluetooth keyboard.

A: For more methods and ideas see [[Wishlist:Text_Input]].

=== Q: Can I record calls and/or play audio files in calls? ===

A: Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing an [[Answering Machine]] is possible. Also using text->speech should be possible or modifying outgoing voice. Currently there is no software bundled in phone to do this.
There are only 2 A/D inputs and three D/A outputs (one dedicated to the earpiece). This means that stereo audio playback cannot happen at the same time as the [[Answering Machine]] functionality, amongst other things. See the audio page. [[Neo1973_Audio_Subsystem|Neo1973 Audio Subsystem]]

=== Q: What is the battery life? ===

A: There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].

=== USB ===

==== Q: What can I do with the USB port on the Neo1973? ====
A: Charge the phone, communicate with it over USB-serial, or USB-networking.

A: Plug external devices, such as wifi, cameras, or mass-storage devices in. The "Mass Market" version of the phone will have wifi integrated.

==== Q: What can't I do with the USB? ====

The only limitation on current hardware seems to be no usb 2.0 support, which means slower communication with 2.0 devices.

==== Q: Why is only USB 1.1 provided? ====

A: The processor has USB 1.1 built in. One with USB2 built in would have been more expensive.

==== Q: Can the Neo charge and use devices on a USB hub at the same time? ====

A:
*When the Neo is connected to a device port on a USB hub, it will start charging. If the hub is a powered hub, then it will charge fast (3h), otherwise around 12h.

*If you plug the Neo into the host port of a USB hub you can use devices on that hub but the Neo will not charge. (Some/many USB hubs will not accept an unpowered host as valid, hence the need for the below cable.)
*This is because the host socket on USB hubs is not powered.

FIC product development is looking into providing something that
conveniently solves this problem.

The USB port on the Neo is not a properly compliant USB host port, all USB host ports must provide 5V - though powered devices or hubs may not draw any current from this, they may refuse to work. (The Belkin Tetrahub is an example of a hub that will not work.)

One solution is a three headed cable.

One end plugs into the Neo. One end plugs into a device port of a powered hub, or the Neo charger. One end plugs into the host port of a hub.

The Charger/USB device plug only has +5V and 0V connected in the simple cable, which are connected to the other ends.

For a more complex cable, when the host socket is not plugged in, the cable acts as a simple USB cable.

==== Q: What are the details of the USB port on the [[Neo1973]]? How does it compare to USB On-The-Go? ====

A: The [[Neo1973]] will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just
a AB socket, but also electrical and software components which cannot be provide by the S3C2410.

You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).

=== Q: Are there any LEDs on the Neo 1973? ===

A: The [[Neo1973]] P1/P2 will have no LEDs besides the screen backlight.

=== Q: Will a JTAG port be made available? ===

A: Included with purchase of The "Hacker's Lunchbox" (Advanced version).

There are [[Neo1973_Hardware#Changes_from_GTA01Bv3|exposed I2C, SPI and debug board connectors]] inside case in all versions and [[Debug Board|Debug Board v2]] (JTAG and serial console) in Advanced version. [[Connecting Neo1973 with Debug Board v2]] explains how to connect it to the phone.

=== Q: Will the JTAG interface that comes with GTA01 be compatible with GTA02? ===

A: Yes

=== Q: What can we expect in future versions? ===

A: A faster CPU, faster GSM (EDGE?) perhaps even powered USB port, USB2, wifi, and camera. No details have been released yet. More details of hardware upgrades should be available sometime in May. There will also be 5 more OpenMoko devices - some not phones in the traditional sense - announced by FIC in September.

==Networking/Connectivity==

=== Q: What kind of connectivity? ===

A: Tri-band GSM (commonly known as "European tri-band", 900/1800/1900 MHz), GPRS Class12/CS4 2.5G (Not EDGE), Bluetooth 2.0 EDR, USB in all versions. WiFi: Atheros AR6K in [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]. (No 3G in year 2007 models)

=== Q: Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ===

A: Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].

=== Q: What providers provide the GSM required for Neo1973? ===

A: See [[Neo1973 compatible cellphone providers]]

=== Q: Will OpenMoko "Just Work" with Mac OS X? ===

A: There has been some discussion of this on the mailing list. There is motivation, and there are interested developers.
Not being a Mac OS X user, I don't know enough
to summarize the discussion to answer this question. Can someone please fill in?

A: For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the OpenMoko.

A: It is expected that (Bluetooth/UB) SyncML based interoperation for
contacts and events can easily be achieved by a patch
to the Apple iSync configuration tables.

A: There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of
PPC/x86/ARM universal binaries) on OpenMoko devices: mySTEP.

==Misc==

=== Q: On the lists on lists.openmoko.org, should replies be added above or below the original text? ===

A: Please reply UNDER post.

=== Q: How can I find out if a question or topic has already been discussed on the mailing lists? ===

A: By searching the mailing list archives. For example, using Google searches:

site:openmoko.org text

For example, to search for accelerometer:

site:openmoko.org accelerometer

If you only want to read the "official" mails from FIC people or from OpenMoko people:

site:openmoko.org text "at fic.com.tw"
site:openmoko.org text "at openmoko.org"

For example to search for "release date" from FIC people:

site:openmoko.org "release date" "at fic.com.tw"

Alternatively you can use the [http://www.google.com/coop/cse?cx=018430699993342716089%3Aszsaurhronw custom OpenMoko search engine] that is using [http://www.google.com/coop/ Google Co-op].

=== Q: how many dead pixels may the LCM have before calling it defect? ===

A: the answer for the display used in GTA01 and GTA02 is '2'

=== Q: Can I has some money for a Neo1973? ===

A: No.

{{Languages|FAQ}}

[[Category:Information]]

Wish List

2008-01-08T16:48:22Z

Tommy: /* Emergency call */ forgot to sign

This article is a place to collect various thoughts about the future of the [[OpenMoko]] software platform. Most wish list ideas have been linked from this page, but you may also wish to check all pages [http://wiki.openmoko.org/wiki/Category:Ideas that have a category of 'Ideas'].

== Development ==
=== Painless SDK installation & Setup ===
Our goal should be a completely painless setup for somebody wanting to develop using [[OpenMoko]]

* one command for installation (apt-get install openmoko)
* one command to start Xnest (openmoko-xephyr?)
* one command to start an i386 shell (openmoko-386-shell)
* one command to start an armel shell (openmoko-armel-shell)

No extra configuration required.

==== IDE Plugins ====
People like to see plugins for
* [http://anjuta.sourceforge.net Anjuta]
* [http://www.eclipse.org Eclipse]
* [http://www.netbeans.org NetBeans]
* Game engine - Game Creation plugins
evaluate eclipse project [http://www.eclipse.org/dsdp/index.php Device Software Development Platform Project from eclipse] and subproject [http://www.eclipse.org/proposals/tml/ Tool for Mobile Linux]
* [http://www.kdevelop.org KDevelop]
* [http://developer.apple.com/tools/xcode/ XCode]
* [http://msdn.microsoft.com/vstudio/ Microsoft Visual Studio 2005]

==== UI Designer ====
Glade code generation is deprecated, so we don't want to use it. The Gtk+ powers told me that the plan is to have gtk 2.12 (out early 2007) with support for GtkBuilder, a libglade derivative which breaks a bit the XML definition in order to support all the new widgets and properties; as soon as it's in the other ui builders will add support for this format. See also [http://bugzilla.gnome.org/show_bug.cgi?id=172535 the relevant bug entry]
* Possibly a Landscape (rotated) view for the screen (480x640 *or* 640x480)?

==== Built-in Scripting Language ====
{{Main|Wishlist:BuiltInScriptingLanguage}}
There was a [http://lists.openmoko.org/pipermail/community/2007-January/001909.html fruitful discussion about a built-in scripting language on the mailing list in January.] Many people feel that it is very important for OpenMoko to choose a scripting language to ship as default in the standard OpenMoko firmware.
==== Easy build of the existing autotools - based packages ====
In the ideal case OpenMoko should exist on the top of the usual ./configure - make workflow which is typical for the majority of the C/C++ based open source projects. It should not require to rewrite or even replace the existing Makefile.am files of the project being ported, and it should allow to pass the needed parameters to the project configure script. Maybe OpenMoko project could be a bigger project having one or more (if some are libraries) autotools - based packages in its separate folders and include the proper documentation how to "wire" the standard autotools based package to the OpenMoko infrastructure.

===Foreign Widget Set Bindings ===
==== Qt Integration ====
The Trolltech folks have a great widget library. I'd like to interface OpenMoko with Qt4, so that we can write Qt4 applications for the phone which don't look alienated.

==== Maemo Integration ====
The Maemo folks have created a successful standard for Webpad applications. I'd like to have a set of MaemoMoko and MokoMaemo wrapper classes that allow me add support for running OpenMoko applications on Maemo and vice versa. Perhaps we can get help from the Nokia OSS folks for that.

==== wxWidgets Integration ====
wxWidgets is a cross-platform application framework that's very popular (I'd say, #3 after Qt and Gtk+). On Linux, wxWidgets uses Gtk+ to implement the widgets. It shouldn't be hard to add support for the additional OpenMoko classes to wxWidgets hence supporting the native OpenMoko look and feel for wxWidgets applications.

wxWidgets team wants OpenMoko classes too and we (wxWidgets) plan to include this project as one of our ideas for [http://google-code-updates.blogspot.com/2007/02/speaking-of-summer.html GSoC 2007]

==== SDL Integration ====
SDL is ''the'' game developer library. There are tons of SDL games out there. We should add OpenMoko support into SDL.

=== Software: Language bindings ===
==== Python bindings ====
Python bindings seem to be a commonly requested feature.

[[User:Mickey]] says, "They are kind of usable on the [http://www.maemo.org Nokia 770], but it's at the lower end of being bearable. We should keep this in mind -- Gtk+ already comes with Python Bindings, so we "just" would need to wrap libmoko*. I would prefer to leave this to the community do though, since it doesn't make sense to start wrapping the API until we have a stable API -- and I can imagine it will take us a couple of months after going open until we can start with stabilizing the libmoko API."

==== C++ bindings ====
There is a whole skilled C++ community coming from the [http://qtopia.net Qtopia] and [http://opie.handhelds.org Opie] projects. If we would consider basing OpenMoko C++ Bindings on [http://www.gtkmm.org/ Gtkmm], then we could drag these guys in.

==== Ruby bindings ====
Ruby and ruby-(gtk|glade) already ported to OpenMoko according to [http://lists.openmoko.org/pipermail/openmoko-apps/2007-May/000040.html this ] and [http://groups.google.de/group/comp.lang.ruby/browse_thread/thread/6bee9970cf055504 this] mesages. It just have to be included to distribution (only 4.9 MB!)

==== Other bindings ====
* Perl
* C#
* I think you could skip a bunch of these by binding to Dbus; most languages already have Dbus bindings

== Community Support ==

=== [http://projects.openmoko.org projects.openmoko.org] ===
Infrastructure for developers with
* One bugzilla for all projects (makes moving bugs forth and backwards between projects ''very'' easy)
* One mailing list for project

== Platform ==
=== Community Images ===
In the future there could be complete, unofficial "product images" that are created by the community, for example maybe one that incorporates only free software (in the GNU or OSI sense). Or images build with a particular niche market in mind -- a student for example.

=== Wishlist voting ===
There could be a kind of voting system like they have at one of those big computer manufacturers homepage. Then the community could vote for the ideas that are most important to them. This would especially make sense for the hardware wishlist, because the hardware is still the part which can't be done by the community that easily.

Here: [http://www.fevote.com/openmoko OpenMoko suggestion board]

== Software: Additional features ==

===PDA Mode===

There are times when you wish to power up the device and not power up the gsm/cellphone portion of the phone. For example in meetings you might wish to access the PDA side with wifi as is the case for example on an aircraft. On booting some method of booting to pda mode would be good - several other phones offer this feature.

===Driving Mode===

It may be forbidden in many countries, but many people use their cell phones while driving. With the touchscreen phones
this is very dangerous: You have to stare at the tiny numbers on the screen and try to hit them with your thumb or try to decipher tiny script of contacts, while steering with the other hand. There should be a configurable driving mode where the interface has a reduced functionality (e.g. only contacts and dialing) with HUGE interface buttons that are easy to use with limited attention.

===Calling===

==== Mask ID based on dialed numbers ====
It would be nice if my number only showed up when I call people in my address book and was otherwise masked. The phone I have now either always shows my number or never or can be set on a per call basis. Having it done automatically based on the number dialed would be good.

==== Use calling cards and similar routing techniques for lower-cost calling ====
Many people use calling cards, low-cost numbers and similar ways of reducing the costs of their calls. It would be nice to have a single panel that would allow you to configure the rules of dialing a number taking in to account such systems.

==== Outgoing black/white lists ====
The ability to allow or deny outoging calls to certain numbers can be useful in a number of situations (e.g. the holder of the 'phone is a child, untrusted, etc.). This could be related to entries in the contact list, for example a user is only allowed to call people who are in their contact list.

Also lists for incoming calls? Some friends always come through, unknown numbers get rejected automatically.

==== Time-based blocking/unblocking of calls ====
Allowing or disallowing outgoing calls at certain times of the day could be useful, e.g. blocking a business phone from making calls outside of business hours.

====Speaker-phone====
* A speaker-phone 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. This software has not been written.

====Advanced Airtime Tracking====
Many phone users have complicated plans, things like unlimited incoming, 100 anytime minutes, 1000 evening minutes, etc. It would be nice if a user could input the various monthly airtime chunks their plan gives them, and then the phone could track how much is left in each chunk, i.e. How much anytime minutes are left this month? Optionally, the software could warn when someone is close to the monthly limit, to help avoid bigger bills.
On (at least some) prepaid [http://en.wikipedia.org/wiki/Unstructured_Supplementary_Service_Data USSD] can be used to check current balance.

==== Anti-stutter software ====
Delayed Auditory Feedback (DAF) has shown to reduce stuttering in individuals by 70%. By using the microphone, it should be pretty simple to implement this on the OpenMoko. The DAF functionality should also be present during phone calls. See http://en.wikipedia.org/wiki/Delayed_auditory_feedback for more information.

====Minimize In-Call mode (check address book while in call)====
On my locked phones I always find it annoying that one can not use other features while a call is in progress. In particular, I'd like to access the address book so that we can (1) give a caller someone else's phone number (or other info) and (2) lookup a phone number when using a calling card or some other proxy.

Similar request when using the browser (lookup passwords, todo list, etc).

====Hold Music (Ringback Tone)====
On some cellphone networks you can pay to change the normal [http://en.wikipedia.org/wiki/Ringback_tone Ringback Tone] that the caller hears when ringing, to a customised sound.
This can partially be implemented on the phone.
Issues are:
*In countries where callers pay, this will make you unpopular.
*In countries where the called party pays, it will use your minutes, or cost you money.
**A list of people to activate this function for would alleviate this.
*[[GPRS]] internet connection will stall while the hold music is being played.
*Extra battery used when playing music.

Also see [[Answering Machine]].

====Play sound clips over the air====
Dialer could have a tab with big buttons which, when push, send sound clips over GSM to the person on the other end of the call. This feature is included in GizmoProject and is called sound blasts: http://support.gizmoproject.com/index.php?_a=knowledgebase&_j=questiondetails&_i=104
The buttons can have default sounds, but also have the ability to be customized.

It would also be useful for notifying people why you can't talk (for example, having an "I can't talk tight now - I'm in the library - this is a pre-recorded message" would be good. Also perhaps you could loop a pre-recorded sound in the background so you can lie about where you are, and have the ability to simulate a really bad connection.

==== DTMF Landline Dialing ====
The ability to hold the Neo near the microphone of a landline handset and have the Neo dial the landline by sounding DTMF tones. The DTMF tones could be generated in software or be pre-recorded files.

Graphically this could be done by adding a 'DTFM dial' button to a context menu. The user would select a contact then presses the 'DTMF dial' button to start the process. A small delay could also be added to allow time to put the Neo near the landline handset.

For the Neo to know which area code to use (or not use) the current or last GPS coordinates could be utilised.

==== Conversation Recorder ====

An option to record phone conversations. Would be helpful to have the device always recording for every call, with the sound data encoded to low quality Ogg Vorbis or SPEEX and stored in RAM. At the end of the conversation the user would have the option to save to flash or discard the conversation. This idea could also be applied to voicemail so you could save voicemails locally.

====Unlicensed Mobile Access (UMA)====
T-Mobile recently rolled out a UMA service that hands off calls between the GSM network and WiFi access points. Only a few phones support it right now, this could be a rather unique feature if OpenMoko can implement it.

This can be combined with a GPS map to show where local free hubs are.

==== Ignore-Call Button ====
{{Main|Wishlist:Ignore Call Button}}

Shut up a ringing phone, without accepting or rejecting the call.

Another alternative might be to use microphone to recognize when the user gives an audible "Shhh!" command. This could prove difficult to determine with the simultaneous ringing, and possible in-pocket shuffling noises.

A really usable feature is to "reject with SMS/text message" - letting the user reply the caller choosing a previously setup template or typical response: "I'm in a meeting - I'll call you later" or "Can't take your call now, please call back in 10 minutes". This feature typically is a much better way to get your co-workers (ie boss) to back off, than to silently ignore the call.

==== Voice Mailbox ====
{{Main|Voice Mailbox}}
On-Phone voice mailbox that records calls on the phone and retrieves voice messages from your mobile service provider's voice mailbox and saves them locally.
Can act profile-dependent.

==== Hold Button ====

Similar to mute, but plays a sound file for the user on the other end while they wait. The sound file could be chosen in some setup beforehand.

==== Unanswered Call, Fast Call ====

In Greece because of the various bill programs some people call a mobile phone, rings one time and then hangup.
Then the user of the mobile phone calls the other user(using the CallerID recognition).

===Audio===

==== Ambient Noise Detection ====
{{Main|Wishlist:Software:Ambient Noise Detection}}

Using the microphone to detect ambient noise the ringtone volume could be adjusted automatically.

Detection of ambient noise could also be used to subtract the noise from the audio signal. However this approach is best performed using two Microphones, one for the voice and the other to detect the noise.

==== Active noise control ====

Using the microphone to do [http://en.wikipedia.org/wiki/Anti-noise active noise control] on media player playback or telephone calls. This should be an independent module/library which can be used by any application which might require this feature. also provide a way to easily alter the parameters of the active noise control.

==== Hear Impaired Mode ====

Hearing impaired people need louder speaker(but with less volume than hands free) and equalized sound, based on their hearing problems(example 20dB hearing loss from 2KHz to 4KHz).
Older people 50+ years old need slower speech rate(time stretch, cut the big speech gups) and cleaner voice.

Please note also the Hearing Aid Compatibility regulations in the US. I have tried to summarize and clarify them [http://quux.wiki.zoho.com/WhereAreHACphones.html here]. I haven't yet discovered whether the FIC device is M or T rated. For many hearing impaired users, a tcoil coupling to their hearing aid (t3/T4 rating) would be preferable to manipulating sound output in other ways.

==== Mute Button ====

Button to temporarily disable microphone while talking for applications such as telephone, audio recording and (when available) movie recording.

===Web Browser===

==== Full-page Zoom Support ====
Full page zoom is a very good feature. If possible, people would want to browse the internet with normal layout than a distorted one. It's best if I could double-tap a text or image block and zoom to a fit size.

The [[BigPageWidget]] proposal suggests 'Full Page Zoom' should be implemented as a widget available to all applications.

* If the processor and memory could afford, it is good to just use [http://www.mozilla.org/projects/firefox/3.0a8/releasenotes/ Firefox 3] in OpenMoko. It has implemented latest gecko's full-page-zoom ability. With certain modification, we could do the same zoom like iPhone's Safari.
* Firefox 3 may be a big eater. A cut-down version of it may be good enough.
* If this is not practical, Minimo with full-page-zoom ability is good.

==== Plugins Support ====
* While an extensive browser plugin system would be costly to the efficacy of the platform three particular browser plugins as poplularized by Mozilla firefox should be adapted to the web-browser, namely: [http://noscript.net/ noscript], [http://adblockplus.org/en/ adblock plus], [http://www.greasespot.net/ greasemonkey] and [http://www.foxmarks.com/ foxmarks].
* Careful use of these can dramatically reduce bandwidth, page space, and rendering costs even if it comes at the risk of some hard drive space in the form of block lists.
* Greasemonkey, in particular, gives users control to set up scripts for commonly traveled pages to further reduce unnecessary or unwanted content.

==== Widget support ====
Built-in browser with the ability to install widget shortcuts (aka links) in the main phone menu, also some apis for interfacing with the other functionality of the phone like adding contacts, reading contacts, reading gps-psoition etc.. (maybe there is some defacto widget standard that could be used)

There is a [http://www.w3.org/TR/widgets/ W3C spec] being developed, which may not be exactly what the original proposal had in mind, but it is about writing simple applications with HTML, SVG and JavaScript. It is mainly Opera's work, and while most [http://widgets.opera.com/ developed widgets are not very useful], there are some that are, and it creates a very nice development platform, especially for mobile devices. So, I think it makes an awful lot of sense for OpenMoko to support this spec.

===Media===
====Music/Video Software====
A real good programming area for competition with the iPhone, a singular video/music player would be great for multimedia. A seamless integration system, a la iTunes and iPod, would be extremely popular.

Using the Wi-Fi connectivity, a separate music program that supports wireless music sharing/ streaming (similar to what can be done when two computer running iTunes that are both on the same network) and that also supports internet radio.

It would also be nice to have some kind of "announce your musical taste" mode. This could be implemented using last.fm profiles, such that when e.g. in a crowded place a user nearby has a similar musical taste, both users get notified so they can share their music files with each other (perhaps using a photo for id). Great for discovering new music - and making friends!

- Possible copyright issues sharing music files?

Sure, but that's the user's concern, not the developer's. There's no way for us to know which audio files the user is permitted/not permitted to share.

==== Reading Support ====
It would be really great to be able to read :

*PDF
*Open Document files
*Text / RTF files
*MS Office files
*Aportis Doc (pdb)
*DjVu
*...

In both landscape and portrait

==== Wikipedia Mirror ====
{{Main|Wishlist:Wikipedia_Mirror}}

==== Blog ScribblePad ====

Draw an image (and maybe add some text), then post to your blog.

==== E-Book Reader ====
* Neos brilliant ultra-sharp screen makes for a very good e-book reading device. All it takes is a good e-book reader with touch-screen page turning / scrolling (see the [[BigPageWidget]] proposal). FBReader could probably be adjusted easily by an experienced GTK hacker. Note that e-book reading is different to pure text/pdf displaying as it requires at least auto-bookmarking of the last read page, proper text and image scaling and text formatting.

==== Personal Wiki ====
{{Main|Wishlist:PersonalWiki}}

Display the notes database as a Wiki. Inspiration: [http://www.acrocat.com/AcroWiki/default.asp?lang=en AcroWiki].

[http://www.didiwiki.org/ Didiwiki]

==== Dictionary, thesaurus, translator and flashcards ====
Native lookup dictionary and thesaurus and foreign translation dictionaries, also with support for Asian languages. Optional custom configurable (though preconfigured) interface with on-line versions of dictionaries, thesaurus and translation services.

'''Dictionary'''
Something like [http://www-user.tu-chemnitz.de/~fri/ding/ ding]:

advantages:
* small
* very efficient + useful
* only limited to really needed functions

Support for vocabulary training with flashcard system (also usable for other content than foreign language words!)

==== Flickr uploader ====
A simply, drag & drop uploader, tagger and organizer to upload images on phone to [http://flickr.com Flickr], with support for various languages. A good base could be the cross-platform uploader [http://juploadr.org/ jUploadr], written in Java and working on Windows, Mac and Linux. But, most of all, the best '''GPL''' program which actually do this work is '''[http://mobilepushr.jottit.com/ Mobile Pushr]''', written in C and Cocoa for iPhone, must be probably ported in python to work on OpenMoko.

===PIM (Personal Information Managment)===
====Context Sensitivity====
Any email or sms message or application that contains a telephone number should be click to dial, eg [http://123567890 1234567890]. Addresses link to mapping software too?

==== Notes ====

Something for taking notes would be a nice feature:
[http://www.gnome.org/projects/tomboy/ Tomboy] has some nice syncing features and is gtk based.

Some Screenshots are [http://www.gnome.org/projects/tomboy/images/ here].

==== Calendar ====

A nice calendar application should be implemented in OpenMoko. This tool should have a syncing feature with your desktop computer.
The tool should have a reminder feature and other features like other mobile phones already have.

I think synchronization sould be handled by computer with opensync+syncml based tool, not by calendar itself. --[[User:Antono|Antono]] 12:25, 7 January 2008 (CET)

==== Address Book ====

* Option to search not just the stored list of addresses, but one or more of the online phonebooks. Probably should be modular to make adding/changing phonebook sites easy. Also allows for future integration with LDAP
servers or whatever.
* Also the possibility to search all info on the contact, like number, email, postal address and so on, in case someone asks you to identify a known number.
* Web-based map-lookup. 'How do I get there from here? (here = current GPS location)' This could also be done
by integrating with whatever on-phone GPS mapping software the Neo ends up using.
* Random text input 'notes' about a contact
* Overall, this should more resemble a Palm-pilot's address-book than your average cellphone's
* Automated Daily backup of phone book to a website archive (similar to Verizon's Back-up Assistant
*Ability to integrate address book with web-based email (such as gmail) account, for those who use web based email as their primary account
* '''[[Wishlist:Tagging|Tagging]]''' Place tags for contacts. Enhance message application to send messages to all contacts tagged with ... . Enhance other application(GPS, ...) with tags.
* Support for:
**[http://en.wikipedia.org/wiki/SyncML SyncML]
**[http://en.wikipedia.org/wiki/Ldap LDAP] address book
**[http://en.wikipedia.org/wiki/LDIF LDIF], [http://en.wikipedia.org/wiki/Xml XML] and [http://en.wikipedia.org/wiki/Comma-separated_values CSV] export and import (when possible).
*Store Bluetooth IDs of friends and notify (configurable only on this device or on both devices) when a one of these Bluetooth ID has been detected (this is more a separate application but has requirements on the address book. Should also be able to create an address book entry from a Bluetooth ID. Could be used as a nice tool to detect people who you're avoiding.

==== Database/List Display/Edit ====
{{Main|Wishlist:PilotDB}}

One of the most useful apps on my Palm Pilot for me is [http://pilot-db.sourceforge.net/ pilot-db]. It's GPL'd.

==== Joe's Goals ====

It'd be nice to have something like [http://www.joesgoals.com Joe's Goals] always available, like my phone is, even when I'm disconnected from the net.

==== Workout ====

Use your phone instead of your notebook while at the gym, and get pretty graphs to admire after you're done.

==== Shopping List ====
keep Track of Prices in different shops and the products you have/don't have. Ideally using a barcode reader and gps.
If it was made aware of recipes it could even tell you what to buy without entering a shoppinglist manually.

==== Fuel Log ====
File data about fueling your car (date/time, liters, price, mileage, ...) and display some information (costs per month, average consumption, ...).
Advanced features could include:
* Automatically storing the GPS coordinates of the place where the car has been fueled (can be deactivated)
* Sending the data to a central server which collects the information
* Let the OpenMoko receive fuel logs per SMS (e.g. if my wife with a non-openmoko mobile fuels the car and wants to file the data using her mobile phone)
* Let the OpenMoko device act as SMS gateway for non-openmoko devices to easily send the data to the central server
* Also support for air log for divers. Not that you will take this device under water but for the crew at the surface.

==== Keep in touch reminder ====
A background application which keeps track of your friends and reminds you when you have not talked, SMS, IM or mailed a person for more than # days.

==== Menstruation period timer ====
Fill in statistics and compute probabilities for menstruation, fertility, mood.
See http://www.getjar.com/products/48/MyGirls

==== Tagging ====
{{Main|Wishlist:Tagging}}
Tags can be used by various applications. Requirement is interoperability for further enhancement.
Tags should be applied to calendar events, mail/sms, calls, places(GPS) and files.
http://tracker-project.org has all needed tagging-and-searching functionality and ready to be used on low-resourced devices.

==== Context based TO-DO list ====
{{Main|Wishlist:context based to-do list}}

If I arrive home and there are "@home" things in the to-do list, the Context based to-do list reminds me of that.

==== Exchange Integration ====

Once there is good TCP/IP connectivity on this phone, integration with corporate email/calendar/to do/etc servers would be a big advantage... near-real-time automatic email downloads and automatic bi-directional syncing are productivity boosters that you have to experience to appreciate. It turns your phone from a 'nice gadget to fiddle with' to a natural-feeling extension of your day-to-day life.

* Is the time right to name names ? Add as your liking...
** Plugin/integration to & from Kontact
** Same with Evolution - Thunderbird - Seamonkey
** ?? Google Calendars ?? (this one is tough)
** Ms Exchange

==== An electronic wallet ====

A database which stores securely PIN codes, login data, bank and email accounts, membership informations, and other valuable and private data. Entries can be ordered in a folder-like manner. Access to the database is given by a master password. The database as well as the master password are stored with strong encryption. For security reasons, the program asks again for entry of the master password after a certain period of inactivity. The database can be synchronized with a PC application (ideally written in Java for cross platform compatibility).

Examples: KWallet [http://docs.kde.org/stable/en/kdeutils/kwallet/index.html], Viskeeper [http://www.sfr-software.de/cms/EN/pocketpc/viskeeperpro/index.html], KeePass [http://keepass.info/]

==== Easy business card sharing for a small group (in the same room) over bluetooth or WIFI ====

Six Neo1973 owners are having a chat in a cafe. They agree to split but meet later. They want to exchange their numbers with each other before they go.... The normal way to do this is for a rather longwinded repeating of numbers to each other, or half the people manually inputting numbers before phoning/texting the other half to complete the process. All in all its a fair number of button presses to get it sorted.

Instead the NEO could have a small app where the phones link up in a small peer to peer Bluetooth network and share automatically with one person initiating a request and the other detected NEOS agreeing/acknowledging the share. The initiating NEO would then sync the mini-group automatically by interrogating each phone and then sending the table of results. The NEOs would have to be clever about checking for duplicates in the address book and offering a choice to the user if there are any conflicts.

PROS:
*genuine saving in time for social and business situations

CONS:
*I am sure there are some security hassles to be pondered....
*not going to be used every day... definitely not an immediate priority.....
*only at geek conferences will all have a neo....

==== SMS Counter ====

An application which shows on the today-screen how many SMS i've already sent in this actual month. Some have for example 150 free SMS to write each month. With that program you can see all the time how many SMS are left until the end of the period. As an alternative it could be a counter which counts backwards from a predefined number over a defined period.

===Profiles===
{{Main|Wishlist:Profiles}}

The Wishlist:Profiles page documents many possible profiles - ways to configure the phone. Including ways to respond to calls, wifi and GPS events.
And how to automatically switch between them.

===Text Messaging===
For '''Text Input related ideas''' see [[Wishlist:Text_Input]]. Bear in mind that T9 can not be included
For current development status of the messaging-app see: [[Messages]].

There are many useful options that now can be used to full capacity:
* '''Acknowledge/status SMS'''
In GSM networks so-called acknowledge-SMS are sent back to the SMS's dispatcher in order to indicate that the primal sms was received (as message delivery is only best effort and is not guaranteed). So in the SMS dialog there could be equal sized buttons with captions as 'send only', 'send and receive delivery status message' and 'send and notify (e.g. ring) when delivery succeeded'.
** '''Special handling of status-SMS'''
Related to the previous entry, these acknowledgment-sms' should be handled in a different way than normal SMS'. Most Motorola do this, while Samsung SGH series don't & clog the inbox, warn of a "new" message upon Status notification: Delivery Status Messages should be stored in a separate menu so they don't bloat the received-folder and you are able to quickly review the status of the messages you had sent.
* '''SMS at time/date''' You could be able to set up messages that are sent at a certain time/date
* '''Binary SMS''' Send binary SMS. Could be used to feign WAP pushes. [http://en.wikipedia.org/wiki/Multimedia_Messaging_Service] See:
** Resource for SMS encoding: [http://web.archive.org/web/20021016104345/www.dreamfabric.com/sms/] [http://web.archive.org/web/20060411222332/] [http://home.student.utwente.nl/s.p.ekkebus/portfolio/resource/sms_pdu.html] [http://www.ihub.com/Binary%20Messages.htm]
** [http://www.gammu.org www.gammu.org] - you can use Gammu/Gammu+ source for this software and/or understanding various SMS formats including EMS, WAP, Nokia Smart Messaging, Siemens & Alcatel encoding ([[User:Marcin|I could]] eventually help)
** Resource for SMS encoding (German): http://de.wikipedia.org/wiki/SMS-Kodierung
** The infamous pocketpc-attack: http://www.mulliner.org/pocketpc/
* '''Profile-override-SMS''' SMS that start with a certain code word override the silent profile and have the phone ring. So someone could alert you in case of some emergency.
* '''Codeword-SMS''' An expansion of the above: check for code words and allow selectable tones for matches. E.g. "Server Down!" has a loud klaxon, "Disk Warning" has a quiet chirp.
* '''(De-)Abreviation-script''' Implement a script that de-abbreviates: "hi m8 u k?-sry i 4gt 2 cal u lst nyt-y dnt we go c film 2moz" becomes "Hi mate. Are you okay? I am sorry that I forgot to call you last night. Why don't we go and see a film tomorrow?" (taken from: [http://en.wikipedia.org/wiki/SMS_language])
** Implement a script that abbreviates :-)
* '''Anti-Spam''' ...feature for SMS. May be it's possible to port some Bayesian based application like bogofilter.
* '''Rule based authorizations''' ...for received messages. For example, delete messages from one source between 9h00 and 18h00 (workday) allow them otherwise (to get alerting messages).
* '''Enable chat-like SMS-viewing''' SMS-Email-like: retain SMS app, but store 'conversations' rather than pile-up. Group/archive conversations by Caller Group (Work / Friends / Home / any user-defined Caller Group). Show appropriate icon from either Caller Group or Caller ID at the source of conversations panel
* '''Searching''' allow full-text search or string search.
* '''Massive SMS Deletion''' based on Conversation, author, before-date-xx.xx.xxxx, caller group, [[Wishlist:Tagging|tags]]...
* '''Call Back''' Prompt 'Call Back' alongside other first-line options (Delete, Save number,.. this kind of options) that appear when reading an SMS.
* '''Non-destructive deletion''', deleted messages goes to trash, and are recoverable.
* '''SMS-EMail-Gateway'''
SMS comes in, gets forward to your inbox, like any other piece of mail. Appropriate alerts and etc occur - again, just like for email. A simple SMTPD running on 127.0.0.1 that is hooked to an email-to-SMS translator that will send email addressed to 'SMS@localhost' (or whatever special address) out via SMS
* '''SMS-filter chain''', for stuff like Codeword-SMS above, Theft-mode activation, auto-response (reply with gsm-position for "Where are you?"), auto-substitution (like replace $POS with gsm-position in outgoing SMS).

=== Text input ===
{{Main|Wishlist:Text Input}}
There are many good suggestions for text input on the specific text input ideas page.

=== More/Custom Input Method Widgets ===
{{Main|Wishlist:More/Custom_Input_Method_Widgets}}
Additional and customizable Input Method Widgets (similar to virtual keyboard).
This could add soft-key functionality to games or other applications such as:
*D-Pads
*buttons
*virtual trackballs
*...
Personalized layouts could be associated with each application.

=== Games ===
{{Main|Wishlist:Games}}

=== Mesh Networking ===
{{Main|Wishlist:Mesh Networking}}

=== Printing Support ===
It would be really neat to be able to print over either bluetooth, Wifi, or USB. I can imagine wanting to print:

* Notes
* Maps
* Email
* Calendars
* ...

Cups contains a bluetooth printing backend, so (in theory) once you have your data in postscript format, you could hand it to cups and it'll do the rest. In practice, it depends on

# GTK+'s printing support
# Making cups run on a really small system

{{note| GTK+'s printing support seems to be very immature in 2.6 (which we need to use for some time). Gtk+ 2.10 contains much better printing support -- once we can use this, it should be more easy.}}

There's always the possibility to render postscript ourselves, but this is not a piece of cake -- in general, printing is much harder than one would imagine.

Further details:
* [http://groups.osdl.org/apps/group_public/download.php/2205/print-summit-gtk.pdf#search=%22gtk%2B%20printing%20API%22 osdl.org]
* [http://www.gnome.org/~alexl/presentations/guadec2006-printing.pdf#search=%22gtk%2B%20printing%20API%22 gnome.org]
* [http://www.j5live.com/?p=204 j5live.com]

===Misc Software===
====Clocks/timers/Activity meters====
===== Sport tracker =====
{{Main|Wishlist:Sport_tracker}}
Sport tracker can be used to measure the distance/velocity from point A to point B (or it could have several intermediate stopping points) using GPS. This would be extremely useful for running, biking, hiking, etc.

===== Standby clock =====
{{Main|Wishlist:Standby_clock}}
A quick way to see what time it is.

===== Egg Timer =====
{{Main|Wishlist:EggTimer}}

Very simple (one click) count up / count down timers are very useful.

===== Cycle Computer =====
As already mentioned by [http://wiki.openmoko.org/wiki/User_talk:Technil Technil], a cycle computer could be created using gps. The sensor at the bike's wheel could transmit data via bluetooth or some cable that would be attached to an openmoko device. In order to save power, one could switch off the gps and only use the bike's sensor.
* Just another idea that came to me: Why don't have sensor's transmit cable plug into the headphone/microphone plug? A tool reads the signals created by the induction of the passing magnet, then gives them to the cycle-computer-app :) --[[User:Minime|Minime]] 19:50, 12 April 2007 (CEST)

===== NTP Server =====

Run the [http://www.ntp.org NTP] daemon using the GPS chipset as a reference clock, so that the Neo would have a very accurate time-of-day clock and would be able to serve time to other networked devices.

I don't know what it would take to implement this. Items to consider would be the availability of a 1 pulse-per-second hardware signal, the accuracy of timestamps delivered in NMEA messags, etc. Dealing with power-management issues (such as the device going to sleep) would also be challenging.

Very simple (one click) count up / count down timers are very useful.

===== Reality check reminder =====
{{Main|Wishlist:Reality check reminder}}

A tool to [http://www.phrack.org/issues.html?issue=64&id=16 hack your brain]

====Calculators====
===== A Universal Unit Converter Tool =====

One never knows when one may have to convert acre-feet into deciliters. A unit conversion tool makes all engineers and engineer wannabes much happier. And not only the engineers.

Ideas what kind of conversions a converter tool could do:

Lenght
- Acceleration
- Angle
- Angular Velocity
- Area
- Capacitance
- Radioactivity
- Currency
- Charge
- Computer Memory
- Conductance
- Density
- Energy
- Illumination
- Power
- Force
- Flow
- Pressure
- Speed
- Temperature
- Time
- Torque
- Viscosity
- Volume
- Weight

Roman Numerals
- ASCII, Hex
- Cooking
- BMI
- Clothing Sizes

Money Converter based on current rates from Internet...
e. g. Dollar <-> Euro

Physical and Mathematical Constants
GPS conversions

- link to or integration of a scientific calculator
- link to or integration of a simple calculator

A good basis for such a converter tool could be the Palm program "units" from
François Pessaux [http://francois.pessaux.neuf.fr/files/units1_11.tgz]. The GPL'd program comes with full documentation.

For GPS conversions see gpsbabel [http://www.gpsbabel.org]

===== An Postfix Notation (RPN) calculator =====

Many engineers, computer scientists and other groups who have grown to enjoy the simplicity and ease of an postfix notation calculator will miss them when they give up other platforms to move to OpenMoko. A RPN calculator will increase adoption by providing one of the tools that other platforms have provided for many years.

==== Windows CE Emulator ====

On ARM machine, Windows CE API emulator, like Wine on x86 machines.

==== PalmOS Emulator ====

The Access group is probably coming out with their Linux platform any time soon. One of the components is a PalmOS emulator which I'd like to see working on OpenMoko as well. There are literally thousands of PalmOS apps.

I'd like to see a Windows CE Emulator with active sync support.

==== TV Guide/Remote Control ====

Use your Phone to easily program your VCR using EPGs.

==== Alcohol meter ====
Give the phone some info about your body (gender, size, weigth) and when/what you drink and it will compute an approximation of the amount of alcohol in your blood. Updates automatically, could have an alarm, when you are probably sober again.
See, for example (German text) http://www.misterio-online.de/promille.htm

==== Interaction with LEGO Mindstorm ====
With the accelerometers, GPS and good CPU, the phone could be used to control/serve as input with robots built with LEGO Mindstorm, which can be accessed by USB and Bluetooth.

==== Flashlight ====
Simple finger application that makes every pixel on the entire screen white to be as bright as possible until you tap the screen again to turn it off. This way, you can use your Neo as a (short term) flashlight!

==== Wii Controller Emulator ====
Use the accelerometers and buttons on screen to work as a Wii controller via Bluetooth.

==== FUSE support ====
Ability to use FUSE to mount larger file systems over wireless. (even gmailfs, sshfs, etc.)

=== Accessibility ===
Accessibility features for the visually impaired.
* High Contrast Themes.
* Screen Magnifier. Features should include automatic cursor tracking when navigating menus and entereing text and provide manual controls to zoom in on other section of the screen.
* Text to speech. The software should read out menu item ,contact lists ,text messages etc. Would also be useful for operating the phone while driving. see: [[Wishlist:Speech synthesis]]

==== VOIP ====
Ability to use the phone for VOIP over wi-fi such as Vonage. They currently have 2 different pieces of software for pc . Basically software creates a mac address which is paired with your Vonage account. Skype could also be implemented but I prefer Vonage. Only available when connected to wi-fi with a good connection. Phone treats calls the same as a cellular call, could keep a separate log of minutes, ability to record conversations, etc. Option to use VOIP if connection is available automaticly or manually. Small icon to show when call is using VOIP.
* A standard SIP client would probably fit better into the "free and open" philosophy.
* Ideally a SIP client that includes ZRTP/SRTP for secure communications.
(Note: Vonage will not give you your SIP credentials, so you cannot log into their network with a non-approved softphone. Other VoIP providers have different policies.)

''This seems very similar to what [http://en.wikipedia.org/wiki/Generic_Access_Network UMA] offers.''

Asterisk is a great communication platform that can run on small devices. I have an Asterisk server running on a Nokia 770 and I read about running Asterisk on an iPhone. With the crosscompiler available it sould be possible to compile it and run Asterisk on an openmoko phone and let it take care of almost everything on the wishlist below.
Edw/

==== Power Meter ====
If the power bar is clicked on it will show time left on charge and if charging it will show time until full.

=== Accelerometer wishes ===
==== Flick interface ====
Ability to "flick" the phone for page up/down by simply and rapidly tilting the phone back-and-forth for up and forth-and-back for down. The same motion can be implemented for sideways motion. This will take advantage of the 2 3d accelerators.

Sensitivity of the scrolling should be configurable and a test option provided.

==== Reading navigation of documents enhanced by accelerometers ====
If the two accelerometers in Neo1973 allows it, it will be nice if when you're reading, give a newspaper, you can move up, down, left and to the right the viewing of the document just moving the phones to the corresponding direction.

I don't know if this is possible (haven't seen the project in detail yet) but this feature could be very attractive for final users (and this is good). (sorry for my english but i'm italian)

==== Wand UI ====
In keeping with the requests to think outside of the box... the dual 3d accelerometers should enable a 'magic wand'-style UI for certain uses. Macros could be recorded and edited, or presets could be used. For example, flipping the device playfully could initiate a game mode or could signal the end of the work day.

==== Shake-to-Wake ====
Giving the phone a shake enables voice commands for a few seconds.
Usage Examples:

* {Shake} "Call" ''ContactName'' ''PhoneType''
* {Shake} "Call John Mobile" (Calls John's mobile)
* {Shake} ''ApplicationName''
* {Shake} "Reader" (Opens the e-book application)

Would require a method of inputting voice tags for applications and contacts and obviously will only work for P2 (accelerometers)
But lets get voice command functionality working before P2 (just by pressing a button on the screen instead of shaking)

I think that is possibly to replace "Shake" with double hit with finger in the side of phone. Proper algorithms(with accelerometers) should recognize any similar activities.

==== Emergency call ====
When the accelerometer detects a great acceleration (i.e. 5G) start a countdown sequence, if it is not stopped make a call to a preconfigured emergency number. If the data from the GPS is accurate give it.

A first version could use a recorded message (an audio file). In next version it could use a synthesizer, so it can give more information (add GPS information when it is ready).

:I would worry that most such events would be false positives, and hard to distinguish from the real thing. A user dropping their phone (an event very common in the life of any cellphone) is far more likely than a user being in a car accident with their phone, and the clatter of a cell phone on asphalt could reach 5G. Additionally, it has to be very hard to distinguish hitting pavement from hitting a windshield, as from a physics standpoint the two are the same thing. [[User:Hashbrowncipher|Hashbrowncipher]] 02:06, 26 October 2007 (CEST)
::It could use the gps data to calculate the speed it is traveling with. Let's say it has been moving for more than 50 km/h for more than 10 seconds. Then it could activate the "emergency call if more than 5g" function. Aside from the countdown timer, it could increase the volume to max and warn the user that an automatic emergency call will take place in x seconds. While it is counting down it could listen for "Never mind, I'm fine, phone" and stop the countdown in case it hears that. It could also output the warning sound to the attached bluetooth headset and let the user talk to emergency services if the user is still conscious. [[User:Tommy|Tommy]] 17:48, 8 January 2008 (CET)

==== Movement detection ====
By detecting that the owner is walking a user defined profile can be activated with a specific set of notification settings. For example you may wish to use a cheap old sounding ringtone so you don't attract attention from muggers. Or you may wish to have a louder ringtone if you carry your phone in a bag where it can't be so easily heard.

==== Games ====
Imagine a first person shooter that you look around by turning your body.

==== Sloshing battery indicator ====
Shaking the phone will produce a sloshing sound, as if it contained a liquid. As the battery loses charge, so the sound produced on being shaken, will replicate a decreasingly empty container. [http://mobile.slashdot.org/article.pl?sid=07/11/28/1342248] for an example.

==== Others ====
Also see the pages[[Wishlist:Auto Align Map]], [[Wishlist:Determine Position]], [[Distance Measuring]], [[Wishlist:Computer Mouse]], [[Wishlist:Dynamic Screen Orientation]].

=== Connectivity ===

==== VNC client ====
A good, stylus friendly VNC client/host combo would be easy to add and terribly useful.

==== Networked X-Windows ====

Whether it's running true X-Windowing over the network, or your bog-standard VNC connection as mentioned above, the ability to have your phone's screen available on your laptop or palmtop would be most desirable.

==== NX client ====

A form of X-windows forwarding optimized for performance over slow, or high-latency links, which could prove extremely useful. Capable of streaming a good quality, full desktop session over modem speeds. The protocol and at least one implementation is gpl'd. [http://en.wikipedia.org/wiki/NX_technology wikipedia]

==== OpenOffice Presenter Control ====

I Think it is a good idea to control your OO Presentation with Openmoko about WLAN or Bluetooth.
I think it needs some buttons to go back or forward and control the mouse to show something and take normal mouse clicks.
But with the mouse clicks I think that we need a short time between the clicks in example 1 second. Because when you make a mouse
click than to fast than you must go back.

==== Amarok and other Media Player remote control ====

Control Amarok or any other Media Player with OpenMoko (as a remote control). Bluetooth or WLAN could be used as protocol to send and receive the data. Maybe a WebInterface of Amarok is a start. Can be used on parties for a mobile music management.

=== Security ===

==== General Filesystem Encryption ====

If anyone wants to get your private data saved on your OpenMoko device, he should have to get through a high security mechanism like dm-crypt. The question is how much CPU power would be needed.
Would it be an idea to encrypt only the private data like phone numbers, preferences, address book etc. (like /home/$USER).

http://luks.endorphin.org

==== My Account ====
{{Main|My Account}}
A way to securely store information about the phone, and ensure that a phone you may be considering purchasing is not stolen.

==== [http://zfoneproject.com/ Zfone] or similar ====

Something that allows the user to speak with another person securely.

==== GSM Encryption ====

This software application would allow GSM encrypted calls to be made using the GSM Data Call Channel.

[[OSvS]]

==== My Voice is my Passport ====
Use voice recognition to unlock the phone. "Hi. My name is ... My voice is my passport. Verify me."

==== Firewall ====
A network firewall

==== Full Mac Support ====
Full mac support, preferably with full software and full sync capabilities with iCal and iMail

==== Anti Theft Application ====

This application would enter the phone into an [[Anti-Theft Mode]] which activates particular security features to reduce the risk of theft and also to ensure a higher probability of recovery of a stolen handset.

====RFID based personal alerts====
Assuming an RFID reader is available: You'd put an RFID tag on your keys, wallet, etc and train a program on the phone to give you a soft or hard alert when one of them leaves detection range. That way, if you're walking away from one of them, the phone could alert you.

====OpenVPN Client====
This application allows to configure the device as an OpenVPN client using the GUI including support for X.509 certificates.

=== Integrated Help System ===

A help system that is either on or off. It could be activated and deactivated by a [[five-second-press]] on a button, for example the AUX button. When the help system is activated, it will explain the use of any item you touch on screen (with stylus or finger). Example: if you touch the battery icon, it will explain that this shows battery level / remaining time. If you touch the date / time icon, it will explain that this icon shows date and time, and that if you press it, you can set date and time. Primarily, this help system should be able to explain all user interface elements in the main screen, but if it proves popular, it could be expanded to cover other applications as well.

===Performance optimisation===
==== Use DMA engine in CPU for blitter ====
The DMA engine in the CPU can substantially speed up moving of large areas of screen in some cases.

==== Use virtual screen to optimise scrolling ====
In some other cases, the hardware supported virtual screen may also speed it up.
===Reusable Display/UI Widgets===
====Use BigPage for full page zoom, scroll, scale in many apps====
The [[BigPageWidget]] Page decribes a widget that could bring full natural page viewing, scaling, scrolling to the OM platform - allowing all applications to make intuitive UIs. A good way to read documents of any type without reformatting them massively increases the utility of a device with a small screen

==Bluetooth==

=== Voice Dialing ===

Dial by voice commands.
<br>Dial by dictating phone number. This way we can voice dial any number even if not in our contact list.

=== Music through Bluetooth Headset ===

Music can be played through a Bluetooth headset, but would stop playing when a call comes in.

=== Walkie Talkie ===

Let OpenMoko devices connect to one another via bluetooth or another connection method (GPRS for long distance but high latency, probably Wifi on P2), and hold a conversation.

Features for this applications can be:
* Push To Talk (PTT) button
* Voice Activated Control (VAC) which will set it in transmit mode when input has is detected above a certain predefined level.
* Optionally a full duplex mode
* Different channels to choose from
* Monitor different (preselected or all) channels for traffic.
* Content encryption
* Active noise control
* Allow zero config use (units can talk without any access point helping)
* Overview of all connected people trough sending GPS data to everyone who is in the Walkie Talkie channel

Local (non-GPRS) use cases include chatting while biking
or motorcycling in a group; perhaps also in a car caravan.
This application could also be used as a baby-phone to monitor your siblings.

This would be more useful if the Neo had Class 1 bluetooth, though probable Wifi on P2 will also offer more range.

(One thumbs up from me) Jackcday

=== Automatic Sync ===

Automatically synchronize with desktop computer (or with any [http://en.wikipedia.org/wiki/SyncML SyncML] server) when within range based on user profile. This may require the use of a secure data transfer.

=== GPS Assisted Bluetooth Management ===

Allow Bluetooth to automatically turn off after loosing connectivity and to automatically turn back on based upon GPS location.

A Bluetooth device is configured for automatic reacquisition based on the following profiles:
* Manual - only when Bluetooth is on
* Non-mobile - the target device is not mobile, periodically attempt reacquisition when in the general area of the device.
* Mobile - the target device is mobile, periodically attempt reacquisition when in the general area of the device.

Each target device is configured as follows:
* Automatic acquisition at last known location: enable/disable
* Automatic acquisition at these locations: list of nickname + coordinates + range

==== Non-mobile devices ====

Examples devices include: computers

The location and range of the target device is determined via training. Periodically, the current GPS coordinates and Bluetooth signal strength are logged. Additionally, connectivity loss events are logged. An algorithm uses these logs to determine the device location and range.

Connection attempts are made when in a configurable proximity to the device. The first attempt when entering the proximity and further attempts at a configurable interval.

==== Mobile devices ====

Example devices include: automobiles

Mobile devices are configured to have two types of locations:
# Last known location
# Non-mobile locations (homes)

===== Last known location =====

A car is mobile, ideally, when you leave your car, the phone should note the car's location when connectivity is lost and then attempt to reacquire the car when you return to the location of the car.

===== Non-mobile locations (homes) =====

As mobile devices may have multiple users, it is not sufficient to always use the last known location. In this case, the device may additionally have multiple homes. For example, a car might have as its homes: home garage and work parking lot.

=== Bluetooth neighbor detection and multiuser apps ===

Like the [http://en.wikipedia.org/wiki/One_laptop_per_child one laptop per child] (OLPC) interface, keep a number in the status bar that represents a count of other openmoko or compatible bluetooth devices in the area. Allow for the spontaneous initiation of a chatroom or multiplayer game or file trading with any moko in the area.

=== Bluetooth environment detection ===

Capability to detect when a predetermined bt device enters/leaves bt range and launch a system-wide event accordingly. This would feed not only the "Neighbour detection" idea described above, but also the "Profiles", "Context based TO-DO list" and "Location-based reminders" ideas. Reminders could be set to trigger in the presence of a specific person X (with BT device Y). Profiles can take into account which devices are present around the phone (car kit, for ex.). To-do list could also change according to present devices.

=== Remote control ===

==== Wireless presenter ====
Use the phone to run your OpenOffice.org Impress presentation remotely using Bluetooth. Cool features:
* Display the text notes for the presenter on the phone's display and update it whenever the slide is changing.
** OO.org has implemented support for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 dual monitor]/[http://www.openoffice.org/issues/show_bug.cgi?id=18486 presenter mode] that can be used as a starting point
* A small timer showing the time passed (and perhaps remaining if the presentation app supports such a feature).
* If you want to be super-cool, you give a preview of the notes of the next slide in the show.
* At the end of a presentation, a "navigator" could allow to easily jump to any slide in the presentation by clicking on it on the phone.
** When you right-click in a running OO.org Impress presentation, you can choose "got o slide..." and select any slide to jump to.

==== Initiated from another device ====
Remote control over Bluetooth from other devices to control media player (play, pause, next, previous, volume control), camera (capture image), etc.
==== Directed at another device ====
Remote control over Bluetooth to other devices to control media player, lights in your house, etc.

[http://mjr.iki.fi/software/remote-0.9.0.tar.gz Remote] is my draft of a python-based remote control app that allows you to define button sets and commands to run on the local or a remote host (through ssh, for instance). Error handling and command interface need work.--[[User:Mjr|Mjr]] 11:14, 18 October 2007 (CEST)

Z-wave uses web-browser control of devices that is said to be compatible with mobile phone browsers so should work with openmoko browser. [http://www.z-wave.com www.z-wave.com]

=== Bluetooth Car Connection ===

Have a deeper connection to the car than just handsfree speakerphone. For instance a transceiver with challenge/response systems to open, possibly even start the car. Possibly go as far as OBD connection to monitor car status on screen/log for later.

Could be done with a port of [https://garage.maemo.org/projects/carman/ Carman] or similar that can connect to an OBD2 adapter via USB or Bluetooth and display various information collect from the car, GPS, and accelerometers. --[http://wiki.openmoko.org/wiki/User:Bmk789 bmk789]

==== Dude, Where's My Car? ====

When in range of the car navigation system, remember the position (perhaps check with the car GPS). When not in range, assumme that you are not in the car, and offer the opportunity to navigate to the car's last known position. That way, you can find your car e.g. on a large parking lot.

=== [[Bluetooth powered Multi-SIM support]] ===

As the Neo1971 does not come with dual-SIM support this could be solved by joining your old bluetooth-enabled mobile to your OpenMoko-phone.

Let SIM card A be in your OpenMoko-phone and SIM card B in your old mobile:
* Incoming call on SIM card B - the OpenMoko-phone acts as a headset(Bluetooth Headset profile)
* Calling out via SIM card B - the OpenMoko-phone acts again as a headset
* Same for Short Messages/MMS/Internet
This way you'd have your old phone switched silent and connected to your OpenMoko-phone that handles all the calls and one can select which SIM card to use.
Advantage: No 'switching' between cards
Disadvantage: Second mobile needs to be in range(e.g. handbag) and charged every once in a while.

===Internet Gateway===

If the device could function as a Bluetooth router/gateway to the internet via the GPRS/data connector, then you could use it to get network connectivity from your laptop and other devices while on the road. Many smartphones can be configured as modems via Bluetooth for use as Dial-Up Networking connectors, and that should be the minimum target. Ideally, if the WiFi functionality was used so the OpenMoko could be an 802.11 router or peer to peer gateway for a laptop, this would be even better. The full bandwidth of GPRS or whatever network is available would then be available.

=== Social Networking ===

Anybody running the social networking app will be broadcasting a profile, and when certain keywords are matched with other users who are also running the application, an alert is sounded. Each mokoid can be added as a hexstring to a profile page, and xml filters can be developed for each social service to convert various keywords and interests to moko-friendly format.

=== Give userspace api control over bluetooth signal strength ===

I have tried bluetooth handsfree sets with other phones and don't get perfect reception due to low signal strength. I suppose the reason the signal is so weak is because the manufacturer wants the battery to last long on its latest charge. Can you please make the strength setting configurable by the user of the phone through an api and perhaps even through the phones gui? I would gladly waste some battery time in exchange for stronger bluetooth signal strength.

== WiFi ==

=== Industrial grade Wifi management ===
One annoyance I've had with Wifi enabled gadgets is that they simply keep the connections in a dumb list. What I'd like to see is more granular connection management, which enables me to specify whether a given connection is friend & family (mom's place), professional client (joe's copies and coffee), commercially available (panera), onetime use, or anything else, as well as managing router config backups, firmware images, and security keys.
=== Captive portal auto-login support ===
Having a nice front-end to some sort of script that checks the authenticity of a captive portal login page (SSL cert), then passes your username and password login information to automatically log you into your account would be very nice as well. This can be done with curl, but it is difficult to make it work on all captive portals out there. Perhaps just a field that you can specify "once I am connected to this AP, run this script: ".

== Wireless Piggyback ==

HSDPA support and the like, so that users can connect directly with the internet with G3/G4 mobile service providers at speeds at or above 3.6 Mb/s.

== Other ==

=== Auto Update ===

A small tool which is configurable to download the latest OpenMoko and OpenMoko related software. Maybe if any internet connection is available or a minimum of bandwith is available then the auto update would download only security related or the whole system etc. .

=== Vibrate Pattern Recorder ===

An application that would allow the user to define their own vibration patterns, and possibly link them to audio files. Recording would be done in real time initiated with a "Record" button, optionally playing the associated sound file in sync with recording). While recording, the user would press and hold a button to define the timing and duration of vibration. The user would press "Stop" when finished. Vibration patterns would have the option of being looped(would terminate at some global ringtone length maximum).

One simple suggested vibration file format would be a sort of run-length encoding: First byte defines the length of a "time-slice" in milliseconds, which would determine the overall tempo(actually the inverse of tempo). The next byte would define the number of time-slices to leave the vibration on, and then another byte for how long to pause after. Continue alternating these on/off bytes until the entire pattern is defined.

- or just use MIDI, using a separate channel for the vibrator.

An implementation of RTTL could also be used to define vibration patterns.

=== PC Input Device ===

Provide a method to use the touchscreen as input device for a nearby desktop machine. Could connect over USB or bluetooth.

=== Advanced Notification And Ringtone Manager ===
{{Main|Wishlist-ANARM}}

ANARM would be an application for handling all event-based audible notifications from an OpenMoko device.

=== Location based reminders ===
{{Main|Wishlist:Location_based_reminders}}
Location based reminders can be used to notify users of various events or reminders that are location based.

=== Synergy Client ===
A synergy client would enable the user to place the device next to a desktop PC and share the desktop`s mouse, keyboard and clipboard over a TCP/IP network. [http://synergy2.sourceforge.net/ Synergy]

== GPS Software ==
*Providing GPS Support also for outdoor users in addition to ordinary street navigation features
** Overlay of satellite images with existing streetmaps
** Incorporating SRTM digital elevation model: for example using the VRML/X3D as data format (see http://www.ai.sri.com/geovrml/) which is interesting for e.g. mountaineering: using a 3d browser rendering VRML/X3D Model, displaying the current position and track (possibly also other gps-tracks of the different routes to a summit downloaded before could be mapped onto the 3d model), (what about 3d hardware support? there is nothing written in the hardware specs about graphics: thinking of OpenGL for embedded systems (see http://www.khronos.org/opengles/)
** Using sth like a tracking mode to allow certain people to determine the current position and track (for rescue missions - like they have for example at http://www.steiger-stiftung.de (a German beneficence for rescue issues) There you can register your mobile phone so the rescue service is able to track you immediately if necessary. The interesting thing: It seems like some mobile phones with GPS have special support for this issue. If your phone is registered, the rescue service is able to get your GPS coordinates directly from the phone without any user assistance. Openmoko should also support this! )
* Implementation of 3dTracking's (http://free.3dtracking.net/) tracking software or equivalent.
* "Geomark" function: if you have to save the current time with your current location, only hit one button...
** You also should be able to navigate with a small "compass" and the distance should be displayed to your saved point (maybe where you parked your car on a big car parking area)...
* '''Measure the distance between two points (air line or walked way) -> no need for a tape measure'''
**I think it would be good if you could either use Bluetooth, GPRS or AdHoc Wifi, and see near Neo1972 on the GPS map so you could see where your friends are, e.g "You want to know if you friend is on the bus behind" You would need a strong wifi and GPRS would be too expensive.
*A bicycle sat-nav would be cool, speciayl designed for bicycles, e.g. cycle routes

<br>[[Community Based Traffic Information]]

== Hardware ==
{{Main|Wish List - Hardware}}

It could be use for beepway Online service too
[http://www.beepway.com]

=== Tactile feedback via buzzer ===
Assuming the hardware has a vibrator/buzzer for silent calls, use a lightly pulsed version of that to simulate tactile feedback when dragging finger across buttons on-screen. Implemented properly, it would almost feel as if the buttons were real.
: 25 ms bump on the buzzer feels about right. Does this harm the vibrator motor? --[[User:Sagacis|Sagacis]] 05:15, 2 October 2007 (CEST)
:: Created a patch to do this [[User:Sagacis/ForceFeedback]] --[[User:Sagacis|Sagacis]] 05:05, 3 October 2007 (CEST)

=== Detachable keyboard ===
Hardware keyboard that can be attached with magnets to a future version of the Neo.

=== SD Slot ===
I think the Neo1973 should have a normal SD card slot as the micro is too small, and the SDs have more space.

: This is not true. Now you can find 2GB micros at the price of 20-30 euros. Too small for what?? --[[User:V0n0|V0n0]] 22:06, 28 December 2007 (CET)

=== IR port ===
Remote control applications
Would be great to use openmoko as a Hamony remote controller.

[[Category:User]]
[[Category:Ideas| ]]

Wish List

2008-01-08T16:47:53Z

Tommy: /* Emergency call */ +ideas.

This article is a place to collect various thoughts about the future of the [[OpenMoko]] software platform. Most wish list ideas have been linked from this page, but you may also wish to check all pages [http://wiki.openmoko.org/wiki/Category:Ideas that have a category of 'Ideas'].

== Development ==
=== Painless SDK installation & Setup ===
Our goal should be a completely painless setup for somebody wanting to develop using [[OpenMoko]]

* one command for installation (apt-get install openmoko)
* one command to start Xnest (openmoko-xephyr?)
* one command to start an i386 shell (openmoko-386-shell)
* one command to start an armel shell (openmoko-armel-shell)

No extra configuration required.

==== IDE Plugins ====
People like to see plugins for
* [http://anjuta.sourceforge.net Anjuta]
* [http://www.eclipse.org Eclipse]
* [http://www.netbeans.org NetBeans]
* Game engine - Game Creation plugins
evaluate eclipse project [http://www.eclipse.org/dsdp/index.php Device Software Development Platform Project from eclipse] and subproject [http://www.eclipse.org/proposals/tml/ Tool for Mobile Linux]
* [http://www.kdevelop.org KDevelop]
* [http://developer.apple.com/tools/xcode/ XCode]
* [http://msdn.microsoft.com/vstudio/ Microsoft Visual Studio 2005]

==== UI Designer ====
Glade code generation is deprecated, so we don't want to use it. The Gtk+ powers told me that the plan is to have gtk 2.12 (out early 2007) with support for GtkBuilder, a libglade derivative which breaks a bit the XML definition in order to support all the new widgets and properties; as soon as it's in the other ui builders will add support for this format. See also [http://bugzilla.gnome.org/show_bug.cgi?id=172535 the relevant bug entry]
* Possibly a Landscape (rotated) view for the screen (480x640 *or* 640x480)?

==== Built-in Scripting Language ====
{{Main|Wishlist:BuiltInScriptingLanguage}}
There was a [http://lists.openmoko.org/pipermail/community/2007-January/001909.html fruitful discussion about a built-in scripting language on the mailing list in January.] Many people feel that it is very important for OpenMoko to choose a scripting language to ship as default in the standard OpenMoko firmware.
==== Easy build of the existing autotools - based packages ====
In the ideal case OpenMoko should exist on the top of the usual ./configure - make workflow which is typical for the majority of the C/C++ based open source projects. It should not require to rewrite or even replace the existing Makefile.am files of the project being ported, and it should allow to pass the needed parameters to the project configure script. Maybe OpenMoko project could be a bigger project having one or more (if some are libraries) autotools - based packages in its separate folders and include the proper documentation how to "wire" the standard autotools based package to the OpenMoko infrastructure.

===Foreign Widget Set Bindings ===
==== Qt Integration ====
The Trolltech folks have a great widget library. I'd like to interface OpenMoko with Qt4, so that we can write Qt4 applications for the phone which don't look alienated.

==== Maemo Integration ====
The Maemo folks have created a successful standard for Webpad applications. I'd like to have a set of MaemoMoko and MokoMaemo wrapper classes that allow me add support for running OpenMoko applications on Maemo and vice versa. Perhaps we can get help from the Nokia OSS folks for that.

==== wxWidgets Integration ====
wxWidgets is a cross-platform application framework that's very popular (I'd say, #3 after Qt and Gtk+). On Linux, wxWidgets uses Gtk+ to implement the widgets. It shouldn't be hard to add support for the additional OpenMoko classes to wxWidgets hence supporting the native OpenMoko look and feel for wxWidgets applications.

wxWidgets team wants OpenMoko classes too and we (wxWidgets) plan to include this project as one of our ideas for [http://google-code-updates.blogspot.com/2007/02/speaking-of-summer.html GSoC 2007]

==== SDL Integration ====
SDL is ''the'' game developer library. There are tons of SDL games out there. We should add OpenMoko support into SDL.

=== Software: Language bindings ===
==== Python bindings ====
Python bindings seem to be a commonly requested feature.

[[User:Mickey]] says, "They are kind of usable on the [http://www.maemo.org Nokia 770], but it's at the lower end of being bearable. We should keep this in mind -- Gtk+ already comes with Python Bindings, so we "just" would need to wrap libmoko*. I would prefer to leave this to the community do though, since it doesn't make sense to start wrapping the API until we have a stable API -- and I can imagine it will take us a couple of months after going open until we can start with stabilizing the libmoko API."

==== C++ bindings ====
There is a whole skilled C++ community coming from the [http://qtopia.net Qtopia] and [http://opie.handhelds.org Opie] projects. If we would consider basing OpenMoko C++ Bindings on [http://www.gtkmm.org/ Gtkmm], then we could drag these guys in.

==== Ruby bindings ====
Ruby and ruby-(gtk|glade) already ported to OpenMoko according to [http://lists.openmoko.org/pipermail/openmoko-apps/2007-May/000040.html this ] and [http://groups.google.de/group/comp.lang.ruby/browse_thread/thread/6bee9970cf055504 this] mesages. It just have to be included to distribution (only 4.9 MB!)

==== Other bindings ====
* Perl
* C#
* I think you could skip a bunch of these by binding to Dbus; most languages already have Dbus bindings

== Community Support ==

=== [http://projects.openmoko.org projects.openmoko.org] ===
Infrastructure for developers with
* One bugzilla for all projects (makes moving bugs forth and backwards between projects ''very'' easy)
* One mailing list for project

== Platform ==
=== Community Images ===
In the future there could be complete, unofficial "product images" that are created by the community, for example maybe one that incorporates only free software (in the GNU or OSI sense). Or images build with a particular niche market in mind -- a student for example.

=== Wishlist voting ===
There could be a kind of voting system like they have at one of those big computer manufacturers homepage. Then the community could vote for the ideas that are most important to them. This would especially make sense for the hardware wishlist, because the hardware is still the part which can't be done by the community that easily.

Here: [http://www.fevote.com/openmoko OpenMoko suggestion board]

== Software: Additional features ==

===PDA Mode===

There are times when you wish to power up the device and not power up the gsm/cellphone portion of the phone. For example in meetings you might wish to access the PDA side with wifi as is the case for example on an aircraft. On booting some method of booting to pda mode would be good - several other phones offer this feature.

===Driving Mode===

It may be forbidden in many countries, but many people use their cell phones while driving. With the touchscreen phones
this is very dangerous: You have to stare at the tiny numbers on the screen and try to hit them with your thumb or try to decipher tiny script of contacts, while steering with the other hand. There should be a configurable driving mode where the interface has a reduced functionality (e.g. only contacts and dialing) with HUGE interface buttons that are easy to use with limited attention.

===Calling===

==== Mask ID based on dialed numbers ====
It would be nice if my number only showed up when I call people in my address book and was otherwise masked. The phone I have now either always shows my number or never or can be set on a per call basis. Having it done automatically based on the number dialed would be good.

==== Use calling cards and similar routing techniques for lower-cost calling ====
Many people use calling cards, low-cost numbers and similar ways of reducing the costs of their calls. It would be nice to have a single panel that would allow you to configure the rules of dialing a number taking in to account such systems.

==== Outgoing black/white lists ====
The ability to allow or deny outoging calls to certain numbers can be useful in a number of situations (e.g. the holder of the 'phone is a child, untrusted, etc.). This could be related to entries in the contact list, for example a user is only allowed to call people who are in their contact list.

Also lists for incoming calls? Some friends always come through, unknown numbers get rejected automatically.

==== Time-based blocking/unblocking of calls ====
Allowing or disallowing outgoing calls at certain times of the day could be useful, e.g. blocking a business phone from making calls outside of business hours.

====Speaker-phone====
* A speaker-phone 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. This software has not been written.

====Advanced Airtime Tracking====
Many phone users have complicated plans, things like unlimited incoming, 100 anytime minutes, 1000 evening minutes, etc. It would be nice if a user could input the various monthly airtime chunks their plan gives them, and then the phone could track how much is left in each chunk, i.e. How much anytime minutes are left this month? Optionally, the software could warn when someone is close to the monthly limit, to help avoid bigger bills.
On (at least some) prepaid [http://en.wikipedia.org/wiki/Unstructured_Supplementary_Service_Data USSD] can be used to check current balance.

==== Anti-stutter software ====
Delayed Auditory Feedback (DAF) has shown to reduce stuttering in individuals by 70%. By using the microphone, it should be pretty simple to implement this on the OpenMoko. The DAF functionality should also be present during phone calls. See http://en.wikipedia.org/wiki/Delayed_auditory_feedback for more information.

====Minimize In-Call mode (check address book while in call)====
On my locked phones I always find it annoying that one can not use other features while a call is in progress. In particular, I'd like to access the address book so that we can (1) give a caller someone else's phone number (or other info) and (2) lookup a phone number when using a calling card or some other proxy.

Similar request when using the browser (lookup passwords, todo list, etc).

====Hold Music (Ringback Tone)====
On some cellphone networks you can pay to change the normal [http://en.wikipedia.org/wiki/Ringback_tone Ringback Tone] that the caller hears when ringing, to a customised sound.
This can partially be implemented on the phone.
Issues are:
*In countries where callers pay, this will make you unpopular.
*In countries where the called party pays, it will use your minutes, or cost you money.
**A list of people to activate this function for would alleviate this.
*[[GPRS]] internet connection will stall while the hold music is being played.
*Extra battery used when playing music.

Also see [[Answering Machine]].

====Play sound clips over the air====
Dialer could have a tab with big buttons which, when push, send sound clips over GSM to the person on the other end of the call. This feature is included in GizmoProject and is called sound blasts: http://support.gizmoproject.com/index.php?_a=knowledgebase&_j=questiondetails&_i=104
The buttons can have default sounds, but also have the ability to be customized.

It would also be useful for notifying people why you can't talk (for example, having an "I can't talk tight now - I'm in the library - this is a pre-recorded message" would be good. Also perhaps you could loop a pre-recorded sound in the background so you can lie about where you are, and have the ability to simulate a really bad connection.

==== DTMF Landline Dialing ====
The ability to hold the Neo near the microphone of a landline handset and have the Neo dial the landline by sounding DTMF tones. The DTMF tones could be generated in software or be pre-recorded files.

Graphically this could be done by adding a 'DTFM dial' button to a context menu. The user would select a contact then presses the 'DTMF dial' button to start the process. A small delay could also be added to allow time to put the Neo near the landline handset.

For the Neo to know which area code to use (or not use) the current or last GPS coordinates could be utilised.

==== Conversation Recorder ====

An option to record phone conversations. Would be helpful to have the device always recording for every call, with the sound data encoded to low quality Ogg Vorbis or SPEEX and stored in RAM. At the end of the conversation the user would have the option to save to flash or discard the conversation. This idea could also be applied to voicemail so you could save voicemails locally.

====Unlicensed Mobile Access (UMA)====
T-Mobile recently rolled out a UMA service that hands off calls between the GSM network and WiFi access points. Only a few phones support it right now, this could be a rather unique feature if OpenMoko can implement it.

This can be combined with a GPS map to show where local free hubs are.

==== Ignore-Call Button ====
{{Main|Wishlist:Ignore Call Button}}

Shut up a ringing phone, without accepting or rejecting the call.

Another alternative might be to use microphone to recognize when the user gives an audible "Shhh!" command. This could prove difficult to determine with the simultaneous ringing, and possible in-pocket shuffling noises.

A really usable feature is to "reject with SMS/text message" - letting the user reply the caller choosing a previously setup template or typical response: "I'm in a meeting - I'll call you later" or "Can't take your call now, please call back in 10 minutes". This feature typically is a much better way to get your co-workers (ie boss) to back off, than to silently ignore the call.

==== Voice Mailbox ====
{{Main|Voice Mailbox}}
On-Phone voice mailbox that records calls on the phone and retrieves voice messages from your mobile service provider's voice mailbox and saves them locally.
Can act profile-dependent.

==== Hold Button ====

Similar to mute, but plays a sound file for the user on the other end while they wait. The sound file could be chosen in some setup beforehand.

==== Unanswered Call, Fast Call ====

In Greece because of the various bill programs some people call a mobile phone, rings one time and then hangup.
Then the user of the mobile phone calls the other user(using the CallerID recognition).

===Audio===

==== Ambient Noise Detection ====
{{Main|Wishlist:Software:Ambient Noise Detection}}

Using the microphone to detect ambient noise the ringtone volume could be adjusted automatically.

Detection of ambient noise could also be used to subtract the noise from the audio signal. However this approach is best performed using two Microphones, one for the voice and the other to detect the noise.

==== Active noise control ====

Using the microphone to do [http://en.wikipedia.org/wiki/Anti-noise active noise control] on media player playback or telephone calls. This should be an independent module/library which can be used by any application which might require this feature. also provide a way to easily alter the parameters of the active noise control.

==== Hear Impaired Mode ====

Hearing impaired people need louder speaker(but with less volume than hands free) and equalized sound, based on their hearing problems(example 20dB hearing loss from 2KHz to 4KHz).
Older people 50+ years old need slower speech rate(time stretch, cut the big speech gups) and cleaner voice.

Please note also the Hearing Aid Compatibility regulations in the US. I have tried to summarize and clarify them [http://quux.wiki.zoho.com/WhereAreHACphones.html here]. I haven't yet discovered whether the FIC device is M or T rated. For many hearing impaired users, a tcoil coupling to their hearing aid (t3/T4 rating) would be preferable to manipulating sound output in other ways.

==== Mute Button ====

Button to temporarily disable microphone while talking for applications such as telephone, audio recording and (when available) movie recording.

===Web Browser===

==== Full-page Zoom Support ====
Full page zoom is a very good feature. If possible, people would want to browse the internet with normal layout than a distorted one. It's best if I could double-tap a text or image block and zoom to a fit size.

The [[BigPageWidget]] proposal suggests 'Full Page Zoom' should be implemented as a widget available to all applications.

* If the processor and memory could afford, it is good to just use [http://www.mozilla.org/projects/firefox/3.0a8/releasenotes/ Firefox 3] in OpenMoko. It has implemented latest gecko's full-page-zoom ability. With certain modification, we could do the same zoom like iPhone's Safari.
* Firefox 3 may be a big eater. A cut-down version of it may be good enough.
* If this is not practical, Minimo with full-page-zoom ability is good.

==== Plugins Support ====
* While an extensive browser plugin system would be costly to the efficacy of the platform three particular browser plugins as poplularized by Mozilla firefox should be adapted to the web-browser, namely: [http://noscript.net/ noscript], [http://adblockplus.org/en/ adblock plus], [http://www.greasespot.net/ greasemonkey] and [http://www.foxmarks.com/ foxmarks].
* Careful use of these can dramatically reduce bandwidth, page space, and rendering costs even if it comes at the risk of some hard drive space in the form of block lists.
* Greasemonkey, in particular, gives users control to set up scripts for commonly traveled pages to further reduce unnecessary or unwanted content.

==== Widget support ====
Built-in browser with the ability to install widget shortcuts (aka links) in the main phone menu, also some apis for interfacing with the other functionality of the phone like adding contacts, reading contacts, reading gps-psoition etc.. (maybe there is some defacto widget standard that could be used)

There is a [http://www.w3.org/TR/widgets/ W3C spec] being developed, which may not be exactly what the original proposal had in mind, but it is about writing simple applications with HTML, SVG and JavaScript. It is mainly Opera's work, and while most [http://widgets.opera.com/ developed widgets are not very useful], there are some that are, and it creates a very nice development platform, especially for mobile devices. So, I think it makes an awful lot of sense for OpenMoko to support this spec.

===Media===
====Music/Video Software====
A real good programming area for competition with the iPhone, a singular video/music player would be great for multimedia. A seamless integration system, a la iTunes and iPod, would be extremely popular.

Using the Wi-Fi connectivity, a separate music program that supports wireless music sharing/ streaming (similar to what can be done when two computer running iTunes that are both on the same network) and that also supports internet radio.

It would also be nice to have some kind of "announce your musical taste" mode. This could be implemented using last.fm profiles, such that when e.g. in a crowded place a user nearby has a similar musical taste, both users get notified so they can share their music files with each other (perhaps using a photo for id). Great for discovering new music - and making friends!

- Possible copyright issues sharing music files?

Sure, but that's the user's concern, not the developer's. There's no way for us to know which audio files the user is permitted/not permitted to share.

==== Reading Support ====
It would be really great to be able to read :

*PDF
*Open Document files
*Text / RTF files
*MS Office files
*Aportis Doc (pdb)
*DjVu
*...

In both landscape and portrait

==== Wikipedia Mirror ====
{{Main|Wishlist:Wikipedia_Mirror}}

==== Blog ScribblePad ====

Draw an image (and maybe add some text), then post to your blog.

==== E-Book Reader ====
* Neos brilliant ultra-sharp screen makes for a very good e-book reading device. All it takes is a good e-book reader with touch-screen page turning / scrolling (see the [[BigPageWidget]] proposal). FBReader could probably be adjusted easily by an experienced GTK hacker. Note that e-book reading is different to pure text/pdf displaying as it requires at least auto-bookmarking of the last read page, proper text and image scaling and text formatting.

==== Personal Wiki ====
{{Main|Wishlist:PersonalWiki}}

Display the notes database as a Wiki. Inspiration: [http://www.acrocat.com/AcroWiki/default.asp?lang=en AcroWiki].

[http://www.didiwiki.org/ Didiwiki]

==== Dictionary, thesaurus, translator and flashcards ====
Native lookup dictionary and thesaurus and foreign translation dictionaries, also with support for Asian languages. Optional custom configurable (though preconfigured) interface with on-line versions of dictionaries, thesaurus and translation services.

'''Dictionary'''
Something like [http://www-user.tu-chemnitz.de/~fri/ding/ ding]:

advantages:
* small
* very efficient + useful
* only limited to really needed functions

Support for vocabulary training with flashcard system (also usable for other content than foreign language words!)

==== Flickr uploader ====
A simply, drag & drop uploader, tagger and organizer to upload images on phone to [http://flickr.com Flickr], with support for various languages. A good base could be the cross-platform uploader [http://juploadr.org/ jUploadr], written in Java and working on Windows, Mac and Linux. But, most of all, the best '''GPL''' program which actually do this work is '''[http://mobilepushr.jottit.com/ Mobile Pushr]''', written in C and Cocoa for iPhone, must be probably ported in python to work on OpenMoko.

===PIM (Personal Information Managment)===
====Context Sensitivity====
Any email or sms message or application that contains a telephone number should be click to dial, eg [http://123567890 1234567890]. Addresses link to mapping software too?

==== Notes ====

Something for taking notes would be a nice feature:
[http://www.gnome.org/projects/tomboy/ Tomboy] has some nice syncing features and is gtk based.

Some Screenshots are [http://www.gnome.org/projects/tomboy/images/ here].

==== Calendar ====

A nice calendar application should be implemented in OpenMoko. This tool should have a syncing feature with your desktop computer.
The tool should have a reminder feature and other features like other mobile phones already have.

I think synchronization sould be handled by computer with opensync+syncml based tool, not by calendar itself. --[[User:Antono|Antono]] 12:25, 7 January 2008 (CET)

==== Address Book ====

* Option to search not just the stored list of addresses, but one or more of the online phonebooks. Probably should be modular to make adding/changing phonebook sites easy. Also allows for future integration with LDAP
servers or whatever.
* Also the possibility to search all info on the contact, like number, email, postal address and so on, in case someone asks you to identify a known number.
* Web-based map-lookup. 'How do I get there from here? (here = current GPS location)' This could also be done
by integrating with whatever on-phone GPS mapping software the Neo ends up using.
* Random text input 'notes' about a contact
* Overall, this should more resemble a Palm-pilot's address-book than your average cellphone's
* Automated Daily backup of phone book to a website archive (similar to Verizon's Back-up Assistant
*Ability to integrate address book with web-based email (such as gmail) account, for those who use web based email as their primary account
* '''[[Wishlist:Tagging|Tagging]]''' Place tags for contacts. Enhance message application to send messages to all contacts tagged with ... . Enhance other application(GPS, ...) with tags.
* Support for:
**[http://en.wikipedia.org/wiki/SyncML SyncML]
**[http://en.wikipedia.org/wiki/Ldap LDAP] address book
**[http://en.wikipedia.org/wiki/LDIF LDIF], [http://en.wikipedia.org/wiki/Xml XML] and [http://en.wikipedia.org/wiki/Comma-separated_values CSV] export and import (when possible).
*Store Bluetooth IDs of friends and notify (configurable only on this device or on both devices) when a one of these Bluetooth ID has been detected (this is more a separate application but has requirements on the address book. Should also be able to create an address book entry from a Bluetooth ID. Could be used as a nice tool to detect people who you're avoiding.

==== Database/List Display/Edit ====
{{Main|Wishlist:PilotDB}}

One of the most useful apps on my Palm Pilot for me is [http://pilot-db.sourceforge.net/ pilot-db]. It's GPL'd.

==== Joe's Goals ====

It'd be nice to have something like [http://www.joesgoals.com Joe's Goals] always available, like my phone is, even when I'm disconnected from the net.

==== Workout ====

Use your phone instead of your notebook while at the gym, and get pretty graphs to admire after you're done.

==== Shopping List ====
keep Track of Prices in different shops and the products you have/don't have. Ideally using a barcode reader and gps.
If it was made aware of recipes it could even tell you what to buy without entering a shoppinglist manually.

==== Fuel Log ====
File data about fueling your car (date/time, liters, price, mileage, ...) and display some information (costs per month, average consumption, ...).
Advanced features could include:
* Automatically storing the GPS coordinates of the place where the car has been fueled (can be deactivated)
* Sending the data to a central server which collects the information
* Let the OpenMoko receive fuel logs per SMS (e.g. if my wife with a non-openmoko mobile fuels the car and wants to file the data using her mobile phone)
* Let the OpenMoko device act as SMS gateway for non-openmoko devices to easily send the data to the central server
* Also support for air log for divers. Not that you will take this device under water but for the crew at the surface.

==== Keep in touch reminder ====
A background application which keeps track of your friends and reminds you when you have not talked, SMS, IM or mailed a person for more than # days.

==== Menstruation period timer ====
Fill in statistics and compute probabilities for menstruation, fertility, mood.
See http://www.getjar.com/products/48/MyGirls

==== Tagging ====
{{Main|Wishlist:Tagging}}
Tags can be used by various applications. Requirement is interoperability for further enhancement.
Tags should be applied to calendar events, mail/sms, calls, places(GPS) and files.
http://tracker-project.org has all needed tagging-and-searching functionality and ready to be used on low-resourced devices.

==== Context based TO-DO list ====
{{Main|Wishlist:context based to-do list}}

If I arrive home and there are "@home" things in the to-do list, the Context based to-do list reminds me of that.

==== Exchange Integration ====

Once there is good TCP/IP connectivity on this phone, integration with corporate email/calendar/to do/etc servers would be a big advantage... near-real-time automatic email downloads and automatic bi-directional syncing are productivity boosters that you have to experience to appreciate. It turns your phone from a 'nice gadget to fiddle with' to a natural-feeling extension of your day-to-day life.

* Is the time right to name names ? Add as your liking...
** Plugin/integration to & from Kontact
** Same with Evolution - Thunderbird - Seamonkey
** ?? Google Calendars ?? (this one is tough)
** Ms Exchange

==== An electronic wallet ====

A database which stores securely PIN codes, login data, bank and email accounts, membership informations, and other valuable and private data. Entries can be ordered in a folder-like manner. Access to the database is given by a master password. The database as well as the master password are stored with strong encryption. For security reasons, the program asks again for entry of the master password after a certain period of inactivity. The database can be synchronized with a PC application (ideally written in Java for cross platform compatibility).

Examples: KWallet [http://docs.kde.org/stable/en/kdeutils/kwallet/index.html], Viskeeper [http://www.sfr-software.de/cms/EN/pocketpc/viskeeperpro/index.html], KeePass [http://keepass.info/]

==== Easy business card sharing for a small group (in the same room) over bluetooth or WIFI ====

Six Neo1973 owners are having a chat in a cafe. They agree to split but meet later. They want to exchange their numbers with each other before they go.... The normal way to do this is for a rather longwinded repeating of numbers to each other, or half the people manually inputting numbers before phoning/texting the other half to complete the process. All in all its a fair number of button presses to get it sorted.

Instead the NEO could have a small app where the phones link up in a small peer to peer Bluetooth network and share automatically with one person initiating a request and the other detected NEOS agreeing/acknowledging the share. The initiating NEO would then sync the mini-group automatically by interrogating each phone and then sending the table of results. The NEOs would have to be clever about checking for duplicates in the address book and offering a choice to the user if there are any conflicts.

PROS:
*genuine saving in time for social and business situations

CONS:
*I am sure there are some security hassles to be pondered....
*not going to be used every day... definitely not an immediate priority.....
*only at geek conferences will all have a neo....

==== SMS Counter ====

An application which shows on the today-screen how many SMS i've already sent in this actual month. Some have for example 150 free SMS to write each month. With that program you can see all the time how many SMS are left until the end of the period. As an alternative it could be a counter which counts backwards from a predefined number over a defined period.

===Profiles===
{{Main|Wishlist:Profiles}}

The Wishlist:Profiles page documents many possible profiles - ways to configure the phone. Including ways to respond to calls, wifi and GPS events.
And how to automatically switch between them.

===Text Messaging===
For '''Text Input related ideas''' see [[Wishlist:Text_Input]]. Bear in mind that T9 can not be included
For current development status of the messaging-app see: [[Messages]].

There are many useful options that now can be used to full capacity:
* '''Acknowledge/status SMS'''
In GSM networks so-called acknowledge-SMS are sent back to the SMS's dispatcher in order to indicate that the primal sms was received (as message delivery is only best effort and is not guaranteed). So in the SMS dialog there could be equal sized buttons with captions as 'send only', 'send and receive delivery status message' and 'send and notify (e.g. ring) when delivery succeeded'.
** '''Special handling of status-SMS'''
Related to the previous entry, these acknowledgment-sms' should be handled in a different way than normal SMS'. Most Motorola do this, while Samsung SGH series don't & clog the inbox, warn of a "new" message upon Status notification: Delivery Status Messages should be stored in a separate menu so they don't bloat the received-folder and you are able to quickly review the status of the messages you had sent.
* '''SMS at time/date''' You could be able to set up messages that are sent at a certain time/date
* '''Binary SMS''' Send binary SMS. Could be used to feign WAP pushes. [http://en.wikipedia.org/wiki/Multimedia_Messaging_Service] See:
** Resource for SMS encoding: [http://web.archive.org/web/20021016104345/www.dreamfabric.com/sms/] [http://web.archive.org/web/20060411222332/] [http://home.student.utwente.nl/s.p.ekkebus/portfolio/resource/sms_pdu.html] [http://www.ihub.com/Binary%20Messages.htm]
** [http://www.gammu.org www.gammu.org] - you can use Gammu/Gammu+ source for this software and/or understanding various SMS formats including EMS, WAP, Nokia Smart Messaging, Siemens & Alcatel encoding ([[User:Marcin|I could]] eventually help)
** Resource for SMS encoding (German): http://de.wikipedia.org/wiki/SMS-Kodierung
** The infamous pocketpc-attack: http://www.mulliner.org/pocketpc/
* '''Profile-override-SMS''' SMS that start with a certain code word override the silent profile and have the phone ring. So someone could alert you in case of some emergency.
* '''Codeword-SMS''' An expansion of the above: check for code words and allow selectable tones for matches. E.g. "Server Down!" has a loud klaxon, "Disk Warning" has a quiet chirp.
* '''(De-)Abreviation-script''' Implement a script that de-abbreviates: "hi m8 u k?-sry i 4gt 2 cal u lst nyt-y dnt we go c film 2moz" becomes "Hi mate. Are you okay? I am sorry that I forgot to call you last night. Why don't we go and see a film tomorrow?" (taken from: [http://en.wikipedia.org/wiki/SMS_language])
** Implement a script that abbreviates :-)
* '''Anti-Spam''' ...feature for SMS. May be it's possible to port some Bayesian based application like bogofilter.
* '''Rule based authorizations''' ...for received messages. For example, delete messages from one source between 9h00 and 18h00 (workday) allow them otherwise (to get alerting messages).
* '''Enable chat-like SMS-viewing''' SMS-Email-like: retain SMS app, but store 'conversations' rather than pile-up. Group/archive conversations by Caller Group (Work / Friends / Home / any user-defined Caller Group). Show appropriate icon from either Caller Group or Caller ID at the source of conversations panel
* '''Searching''' allow full-text search or string search.
* '''Massive SMS Deletion''' based on Conversation, author, before-date-xx.xx.xxxx, caller group, [[Wishlist:Tagging|tags]]...
* '''Call Back''' Prompt 'Call Back' alongside other first-line options (Delete, Save number,.. this kind of options) that appear when reading an SMS.
* '''Non-destructive deletion''', deleted messages goes to trash, and are recoverable.
* '''SMS-EMail-Gateway'''
SMS comes in, gets forward to your inbox, like any other piece of mail. Appropriate alerts and etc occur - again, just like for email. A simple SMTPD running on 127.0.0.1 that is hooked to an email-to-SMS translator that will send email addressed to 'SMS@localhost' (or whatever special address) out via SMS
* '''SMS-filter chain''', for stuff like Codeword-SMS above, Theft-mode activation, auto-response (reply with gsm-position for "Where are you?"), auto-substitution (like replace $POS with gsm-position in outgoing SMS).

=== Text input ===
{{Main|Wishlist:Text Input}}
There are many good suggestions for text input on the specific text input ideas page.

=== More/Custom Input Method Widgets ===
{{Main|Wishlist:More/Custom_Input_Method_Widgets}}
Additional and customizable Input Method Widgets (similar to virtual keyboard).
This could add soft-key functionality to games or other applications such as:
*D-Pads
*buttons
*virtual trackballs
*...
Personalized layouts could be associated with each application.

=== Games ===
{{Main|Wishlist:Games}}

=== Mesh Networking ===
{{Main|Wishlist:Mesh Networking}}

=== Printing Support ===
It would be really neat to be able to print over either bluetooth, Wifi, or USB. I can imagine wanting to print:

* Notes
* Maps
* Email
* Calendars
* ...

Cups contains a bluetooth printing backend, so (in theory) once you have your data in postscript format, you could hand it to cups and it'll do the rest. In practice, it depends on

# GTK+'s printing support
# Making cups run on a really small system

{{note| GTK+'s printing support seems to be very immature in 2.6 (which we need to use for some time). Gtk+ 2.10 contains much better printing support -- once we can use this, it should be more easy.}}

There's always the possibility to render postscript ourselves, but this is not a piece of cake -- in general, printing is much harder than one would imagine.

Further details:
* [http://groups.osdl.org/apps/group_public/download.php/2205/print-summit-gtk.pdf#search=%22gtk%2B%20printing%20API%22 osdl.org]
* [http://www.gnome.org/~alexl/presentations/guadec2006-printing.pdf#search=%22gtk%2B%20printing%20API%22 gnome.org]
* [http://www.j5live.com/?p=204 j5live.com]

===Misc Software===
====Clocks/timers/Activity meters====
===== Sport tracker =====
{{Main|Wishlist:Sport_tracker}}
Sport tracker can be used to measure the distance/velocity from point A to point B (or it could have several intermediate stopping points) using GPS. This would be extremely useful for running, biking, hiking, etc.

===== Standby clock =====
{{Main|Wishlist:Standby_clock}}
A quick way to see what time it is.

===== Egg Timer =====
{{Main|Wishlist:EggTimer}}

Very simple (one click) count up / count down timers are very useful.

===== Cycle Computer =====
As already mentioned by [http://wiki.openmoko.org/wiki/User_talk:Technil Technil], a cycle computer could be created using gps. The sensor at the bike's wheel could transmit data via bluetooth or some cable that would be attached to an openmoko device. In order to save power, one could switch off the gps and only use the bike's sensor.
* Just another idea that came to me: Why don't have sensor's transmit cable plug into the headphone/microphone plug? A tool reads the signals created by the induction of the passing magnet, then gives them to the cycle-computer-app :) --[[User:Minime|Minime]] 19:50, 12 April 2007 (CEST)

===== NTP Server =====

Run the [http://www.ntp.org NTP] daemon using the GPS chipset as a reference clock, so that the Neo would have a very accurate time-of-day clock and would be able to serve time to other networked devices.

I don't know what it would take to implement this. Items to consider would be the availability of a 1 pulse-per-second hardware signal, the accuracy of timestamps delivered in NMEA messags, etc. Dealing with power-management issues (such as the device going to sleep) would also be challenging.

Very simple (one click) count up / count down timers are very useful.

===== Reality check reminder =====
{{Main|Wishlist:Reality check reminder}}

A tool to [http://www.phrack.org/issues.html?issue=64&id=16 hack your brain]

====Calculators====
===== A Universal Unit Converter Tool =====

One never knows when one may have to convert acre-feet into deciliters. A unit conversion tool makes all engineers and engineer wannabes much happier. And not only the engineers.

Ideas what kind of conversions a converter tool could do:

Lenght
- Acceleration
- Angle
- Angular Velocity
- Area
- Capacitance
- Radioactivity
- Currency
- Charge
- Computer Memory
- Conductance
- Density
- Energy
- Illumination
- Power
- Force
- Flow
- Pressure
- Speed
- Temperature
- Time
- Torque
- Viscosity
- Volume
- Weight

Roman Numerals
- ASCII, Hex
- Cooking
- BMI
- Clothing Sizes

Money Converter based on current rates from Internet...
e. g. Dollar <-> Euro

Physical and Mathematical Constants
GPS conversions

- link to or integration of a scientific calculator
- link to or integration of a simple calculator

A good basis for such a converter tool could be the Palm program "units" from
François Pessaux [http://francois.pessaux.neuf.fr/files/units1_11.tgz]. The GPL'd program comes with full documentation.

For GPS conversions see gpsbabel [http://www.gpsbabel.org]

===== An Postfix Notation (RPN) calculator =====

Many engineers, computer scientists and other groups who have grown to enjoy the simplicity and ease of an postfix notation calculator will miss them when they give up other platforms to move to OpenMoko. A RPN calculator will increase adoption by providing one of the tools that other platforms have provided for many years.

==== Windows CE Emulator ====

On ARM machine, Windows CE API emulator, like Wine on x86 machines.

==== PalmOS Emulator ====

The Access group is probably coming out with their Linux platform any time soon. One of the components is a PalmOS emulator which I'd like to see working on OpenMoko as well. There are literally thousands of PalmOS apps.

I'd like to see a Windows CE Emulator with active sync support.

==== TV Guide/Remote Control ====

Use your Phone to easily program your VCR using EPGs.

==== Alcohol meter ====
Give the phone some info about your body (gender, size, weigth) and when/what you drink and it will compute an approximation of the amount of alcohol in your blood. Updates automatically, could have an alarm, when you are probably sober again.
See, for example (German text) http://www.misterio-online.de/promille.htm

==== Interaction with LEGO Mindstorm ====
With the accelerometers, GPS and good CPU, the phone could be used to control/serve as input with robots built with LEGO Mindstorm, which can be accessed by USB and Bluetooth.

==== Flashlight ====
Simple finger application that makes every pixel on the entire screen white to be as bright as possible until you tap the screen again to turn it off. This way, you can use your Neo as a (short term) flashlight!

==== Wii Controller Emulator ====
Use the accelerometers and buttons on screen to work as a Wii controller via Bluetooth.

==== FUSE support ====
Ability to use FUSE to mount larger file systems over wireless. (even gmailfs, sshfs, etc.)

=== Accessibility ===
Accessibility features for the visually impaired.
* High Contrast Themes.
* Screen Magnifier. Features should include automatic cursor tracking when navigating menus and entereing text and provide manual controls to zoom in on other section of the screen.
* Text to speech. The software should read out menu item ,contact lists ,text messages etc. Would also be useful for operating the phone while driving. see: [[Wishlist:Speech synthesis]]

==== VOIP ====
Ability to use the phone for VOIP over wi-fi such as Vonage. They currently have 2 different pieces of software for pc . Basically software creates a mac address which is paired with your Vonage account. Skype could also be implemented but I prefer Vonage. Only available when connected to wi-fi with a good connection. Phone treats calls the same as a cellular call, could keep a separate log of minutes, ability to record conversations, etc. Option to use VOIP if connection is available automaticly or manually. Small icon to show when call is using VOIP.
* A standard SIP client would probably fit better into the "free and open" philosophy.
* Ideally a SIP client that includes ZRTP/SRTP for secure communications.
(Note: Vonage will not give you your SIP credentials, so you cannot log into their network with a non-approved softphone. Other VoIP providers have different policies.)

''This seems very similar to what [http://en.wikipedia.org/wiki/Generic_Access_Network UMA] offers.''

Asterisk is a great communication platform that can run on small devices. I have an Asterisk server running on a Nokia 770 and I read about running Asterisk on an iPhone. With the crosscompiler available it sould be possible to compile it and run Asterisk on an openmoko phone and let it take care of almost everything on the wishlist below.
Edw/

==== Power Meter ====
If the power bar is clicked on it will show time left on charge and if charging it will show time until full.

=== Accelerometer wishes ===
==== Flick interface ====
Ability to "flick" the phone for page up/down by simply and rapidly tilting the phone back-and-forth for up and forth-and-back for down. The same motion can be implemented for sideways motion. This will take advantage of the 2 3d accelerators.

Sensitivity of the scrolling should be configurable and a test option provided.

==== Reading navigation of documents enhanced by accelerometers ====
If the two accelerometers in Neo1973 allows it, it will be nice if when you're reading, give a newspaper, you can move up, down, left and to the right the viewing of the document just moving the phones to the corresponding direction.

I don't know if this is possible (haven't seen the project in detail yet) but this feature could be very attractive for final users (and this is good). (sorry for my english but i'm italian)

==== Wand UI ====
In keeping with the requests to think outside of the box... the dual 3d accelerometers should enable a 'magic wand'-style UI for certain uses. Macros could be recorded and edited, or presets could be used. For example, flipping the device playfully could initiate a game mode or could signal the end of the work day.

==== Shake-to-Wake ====
Giving the phone a shake enables voice commands for a few seconds.
Usage Examples:

* {Shake} "Call" ''ContactName'' ''PhoneType''
* {Shake} "Call John Mobile" (Calls John's mobile)
* {Shake} ''ApplicationName''
* {Shake} "Reader" (Opens the e-book application)

Would require a method of inputting voice tags for applications and contacts and obviously will only work for P2 (accelerometers)
But lets get voice command functionality working before P2 (just by pressing a button on the screen instead of shaking)

I think that is possibly to replace "Shake" with double hit with finger in the side of phone. Proper algorithms(with accelerometers) should recognize any similar activities.

==== Emergency call ====
When the accelerometer detects a great acceleration (i.e. 5G) start a countdown sequence, if it is not stopped make a call to a preconfigured emergency number. If the data from the GPS is accurate give it.

A first version could use a recorded message (an audio file). In next version it could use a synthesizer, so it can give more information (add GPS information when it is ready).

:I would worry that most such events would be false positives, and hard to distinguish from the real thing. A user dropping their phone (an event very common in the life of any cellphone) is far more likely than a user being in a car accident with their phone, and the clatter of a cell phone on asphalt could reach 5G. Additionally, it has to be very hard to distinguish hitting pavement from hitting a windshield, as from a physics standpoint the two are the same thing. [[User:Hashbrowncipher|Hashbrowncipher]] 02:06, 26 October 2007 (CEST)
::It could use the gps data to calculate the speed it is traveling with. Let's say it has been moving for more than 50 km/h for more than 10 seconds. Then it could activate the "emergency call if more than 5g" function. Aside from the countdown timer, it could increase the volume to max and warn the user that an automatic emergency call will take place in x seconds. While it is counting down it could listen for "Never mind, I'm fine, phone" and stop the countdown in case it hears that. It could also output the warning sound to the attached bluetooth headset and let the user talk to emergency services if the user is still conscious.

==== Movement detection ====
By detecting that the owner is walking a user defined profile can be activated with a specific set of notification settings. For example you may wish to use a cheap old sounding ringtone so you don't attract attention from muggers. Or you may wish to have a louder ringtone if you carry your phone in a bag where it can't be so easily heard.

==== Games ====
Imagine a first person shooter that you look around by turning your body.

==== Sloshing battery indicator ====
Shaking the phone will produce a sloshing sound, as if it contained a liquid. As the battery loses charge, so the sound produced on being shaken, will replicate a decreasingly empty container. [http://mobile.slashdot.org/article.pl?sid=07/11/28/1342248] for an example.

==== Others ====
Also see the pages[[Wishlist:Auto Align Map]], [[Wishlist:Determine Position]], [[Distance Measuring]], [[Wishlist:Computer Mouse]], [[Wishlist:Dynamic Screen Orientation]].

=== Connectivity ===

==== VNC client ====
A good, stylus friendly VNC client/host combo would be easy to add and terribly useful.

==== Networked X-Windows ====

Whether it's running true X-Windowing over the network, or your bog-standard VNC connection as mentioned above, the ability to have your phone's screen available on your laptop or palmtop would be most desirable.

==== NX client ====

A form of X-windows forwarding optimized for performance over slow, or high-latency links, which could prove extremely useful. Capable of streaming a good quality, full desktop session over modem speeds. The protocol and at least one implementation is gpl'd. [http://en.wikipedia.org/wiki/NX_technology wikipedia]

==== OpenOffice Presenter Control ====

I Think it is a good idea to control your OO Presentation with Openmoko about WLAN or Bluetooth.
I think it needs some buttons to go back or forward and control the mouse to show something and take normal mouse clicks.
But with the mouse clicks I think that we need a short time between the clicks in example 1 second. Because when you make a mouse
click than to fast than you must go back.

==== Amarok and other Media Player remote control ====

Control Amarok or any other Media Player with OpenMoko (as a remote control). Bluetooth or WLAN could be used as protocol to send and receive the data. Maybe a WebInterface of Amarok is a start. Can be used on parties for a mobile music management.

=== Security ===

==== General Filesystem Encryption ====

If anyone wants to get your private data saved on your OpenMoko device, he should have to get through a high security mechanism like dm-crypt. The question is how much CPU power would be needed.
Would it be an idea to encrypt only the private data like phone numbers, preferences, address book etc. (like /home/$USER).

http://luks.endorphin.org

==== My Account ====
{{Main|My Account}}
A way to securely store information about the phone, and ensure that a phone you may be considering purchasing is not stolen.

==== [http://zfoneproject.com/ Zfone] or similar ====

Something that allows the user to speak with another person securely.

==== GSM Encryption ====

This software application would allow GSM encrypted calls to be made using the GSM Data Call Channel.

[[OSvS]]

==== My Voice is my Passport ====
Use voice recognition to unlock the phone. "Hi. My name is ... My voice is my passport. Verify me."

==== Firewall ====
A network firewall

==== Full Mac Support ====
Full mac support, preferably with full software and full sync capabilities with iCal and iMail

==== Anti Theft Application ====

This application would enter the phone into an [[Anti-Theft Mode]] which activates particular security features to reduce the risk of theft and also to ensure a higher probability of recovery of a stolen handset.

====RFID based personal alerts====
Assuming an RFID reader is available: You'd put an RFID tag on your keys, wallet, etc and train a program on the phone to give you a soft or hard alert when one of them leaves detection range. That way, if you're walking away from one of them, the phone could alert you.

====OpenVPN Client====
This application allows to configure the device as an OpenVPN client using the GUI including support for X.509 certificates.

=== Integrated Help System ===

A help system that is either on or off. It could be activated and deactivated by a [[five-second-press]] on a button, for example the AUX button. When the help system is activated, it will explain the use of any item you touch on screen (with stylus or finger). Example: if you touch the battery icon, it will explain that this shows battery level / remaining time. If you touch the date / time icon, it will explain that this icon shows date and time, and that if you press it, you can set date and time. Primarily, this help system should be able to explain all user interface elements in the main screen, but if it proves popular, it could be expanded to cover other applications as well.

===Performance optimisation===
==== Use DMA engine in CPU for blitter ====
The DMA engine in the CPU can substantially speed up moving of large areas of screen in some cases.

==== Use virtual screen to optimise scrolling ====
In some other cases, the hardware supported virtual screen may also speed it up.
===Reusable Display/UI Widgets===
====Use BigPage for full page zoom, scroll, scale in many apps====
The [[BigPageWidget]] Page decribes a widget that could bring full natural page viewing, scaling, scrolling to the OM platform - allowing all applications to make intuitive UIs. A good way to read documents of any type without reformatting them massively increases the utility of a device with a small screen

==Bluetooth==

=== Voice Dialing ===

Dial by voice commands.
<br>Dial by dictating phone number. This way we can voice dial any number even if not in our contact list.

=== Music through Bluetooth Headset ===

Music can be played through a Bluetooth headset, but would stop playing when a call comes in.

=== Walkie Talkie ===

Let OpenMoko devices connect to one another via bluetooth or another connection method (GPRS for long distance but high latency, probably Wifi on P2), and hold a conversation.

Features for this applications can be:
* Push To Talk (PTT) button
* Voice Activated Control (VAC) which will set it in transmit mode when input has is detected above a certain predefined level.
* Optionally a full duplex mode
* Different channels to choose from
* Monitor different (preselected or all) channels for traffic.
* Content encryption
* Active noise control
* Allow zero config use (units can talk without any access point helping)
* Overview of all connected people trough sending GPS data to everyone who is in the Walkie Talkie channel

Local (non-GPRS) use cases include chatting while biking
or motorcycling in a group; perhaps also in a car caravan.
This application could also be used as a baby-phone to monitor your siblings.

This would be more useful if the Neo had Class 1 bluetooth, though probable Wifi on P2 will also offer more range.

(One thumbs up from me) Jackcday

=== Automatic Sync ===

Automatically synchronize with desktop computer (or with any [http://en.wikipedia.org/wiki/SyncML SyncML] server) when within range based on user profile. This may require the use of a secure data transfer.

=== GPS Assisted Bluetooth Management ===

Allow Bluetooth to automatically turn off after loosing connectivity and to automatically turn back on based upon GPS location.

A Bluetooth device is configured for automatic reacquisition based on the following profiles:
* Manual - only when Bluetooth is on
* Non-mobile - the target device is not mobile, periodically attempt reacquisition when in the general area of the device.
* Mobile - the target device is mobile, periodically attempt reacquisition when in the general area of the device.

Each target device is configured as follows:
* Automatic acquisition at last known location: enable/disable
* Automatic acquisition at these locations: list of nickname + coordinates + range

==== Non-mobile devices ====

Examples devices include: computers

The location and range of the target device is determined via training. Periodically, the current GPS coordinates and Bluetooth signal strength are logged. Additionally, connectivity loss events are logged. An algorithm uses these logs to determine the device location and range.

Connection attempts are made when in a configurable proximity to the device. The first attempt when entering the proximity and further attempts at a configurable interval.

==== Mobile devices ====

Example devices include: automobiles

Mobile devices are configured to have two types of locations:
# Last known location
# Non-mobile locations (homes)

===== Last known location =====

A car is mobile, ideally, when you leave your car, the phone should note the car's location when connectivity is lost and then attempt to reacquire the car when you return to the location of the car.

===== Non-mobile locations (homes) =====

As mobile devices may have multiple users, it is not sufficient to always use the last known location. In this case, the device may additionally have multiple homes. For example, a car might have as its homes: home garage and work parking lot.

=== Bluetooth neighbor detection and multiuser apps ===

Like the [http://en.wikipedia.org/wiki/One_laptop_per_child one laptop per child] (OLPC) interface, keep a number in the status bar that represents a count of other openmoko or compatible bluetooth devices in the area. Allow for the spontaneous initiation of a chatroom or multiplayer game or file trading with any moko in the area.

=== Bluetooth environment detection ===

Capability to detect when a predetermined bt device enters/leaves bt range and launch a system-wide event accordingly. This would feed not only the "Neighbour detection" idea described above, but also the "Profiles", "Context based TO-DO list" and "Location-based reminders" ideas. Reminders could be set to trigger in the presence of a specific person X (with BT device Y). Profiles can take into account which devices are present around the phone (car kit, for ex.). To-do list could also change according to present devices.

=== Remote control ===

==== Wireless presenter ====
Use the phone to run your OpenOffice.org Impress presentation remotely using Bluetooth. Cool features:
* Display the text notes for the presenter on the phone's display and update it whenever the slide is changing.
** OO.org has implemented support for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 dual monitor]/[http://www.openoffice.org/issues/show_bug.cgi?id=18486 presenter mode] that can be used as a starting point
* A small timer showing the time passed (and perhaps remaining if the presentation app supports such a feature).
* If you want to be super-cool, you give a preview of the notes of the next slide in the show.
* At the end of a presentation, a "navigator" could allow to easily jump to any slide in the presentation by clicking on it on the phone.
** When you right-click in a running OO.org Impress presentation, you can choose "got o slide..." and select any slide to jump to.

==== Initiated from another device ====
Remote control over Bluetooth from other devices to control media player (play, pause, next, previous, volume control), camera (capture image), etc.
==== Directed at another device ====
Remote control over Bluetooth to other devices to control media player, lights in your house, etc.

[http://mjr.iki.fi/software/remote-0.9.0.tar.gz Remote] is my draft of a python-based remote control app that allows you to define button sets and commands to run on the local or a remote host (through ssh, for instance). Error handling and command interface need work.--[[User:Mjr|Mjr]] 11:14, 18 October 2007 (CEST)

Z-wave uses web-browser control of devices that is said to be compatible with mobile phone browsers so should work with openmoko browser. [http://www.z-wave.com www.z-wave.com]

=== Bluetooth Car Connection ===

Have a deeper connection to the car than just handsfree speakerphone. For instance a transceiver with challenge/response systems to open, possibly even start the car. Possibly go as far as OBD connection to monitor car status on screen/log for later.

Could be done with a port of [https://garage.maemo.org/projects/carman/ Carman] or similar that can connect to an OBD2 adapter via USB or Bluetooth and display various information collect from the car, GPS, and accelerometers. --[http://wiki.openmoko.org/wiki/User:Bmk789 bmk789]

==== Dude, Where's My Car? ====

When in range of the car navigation system, remember the position (perhaps check with the car GPS). When not in range, assumme that you are not in the car, and offer the opportunity to navigate to the car's last known position. That way, you can find your car e.g. on a large parking lot.

=== [[Bluetooth powered Multi-SIM support]] ===

As the Neo1971 does not come with dual-SIM support this could be solved by joining your old bluetooth-enabled mobile to your OpenMoko-phone.

Let SIM card A be in your OpenMoko-phone and SIM card B in your old mobile:
* Incoming call on SIM card B - the OpenMoko-phone acts as a headset(Bluetooth Headset profile)
* Calling out via SIM card B - the OpenMoko-phone acts again as a headset
* Same for Short Messages/MMS/Internet
This way you'd have your old phone switched silent and connected to your OpenMoko-phone that handles all the calls and one can select which SIM card to use.
Advantage: No 'switching' between cards
Disadvantage: Second mobile needs to be in range(e.g. handbag) and charged every once in a while.

===Internet Gateway===

If the device could function as a Bluetooth router/gateway to the internet via the GPRS/data connector, then you could use it to get network connectivity from your laptop and other devices while on the road. Many smartphones can be configured as modems via Bluetooth for use as Dial-Up Networking connectors, and that should be the minimum target. Ideally, if the WiFi functionality was used so the OpenMoko could be an 802.11 router or peer to peer gateway for a laptop, this would be even better. The full bandwidth of GPRS or whatever network is available would then be available.

=== Social Networking ===

Anybody running the social networking app will be broadcasting a profile, and when certain keywords are matched with other users who are also running the application, an alert is sounded. Each mokoid can be added as a hexstring to a profile page, and xml filters can be developed for each social service to convert various keywords and interests to moko-friendly format.

=== Give userspace api control over bluetooth signal strength ===

I have tried bluetooth handsfree sets with other phones and don't get perfect reception due to low signal strength. I suppose the reason the signal is so weak is because the manufacturer wants the battery to last long on its latest charge. Can you please make the strength setting configurable by the user of the phone through an api and perhaps even through the phones gui? I would gladly waste some battery time in exchange for stronger bluetooth signal strength.

== WiFi ==

=== Industrial grade Wifi management ===
One annoyance I've had with Wifi enabled gadgets is that they simply keep the connections in a dumb list. What I'd like to see is more granular connection management, which enables me to specify whether a given connection is friend & family (mom's place), professional client (joe's copies and coffee), commercially available (panera), onetime use, or anything else, as well as managing router config backups, firmware images, and security keys.
=== Captive portal auto-login support ===
Having a nice front-end to some sort of script that checks the authenticity of a captive portal login page (SSL cert), then passes your username and password login information to automatically log you into your account would be very nice as well. This can be done with curl, but it is difficult to make it work on all captive portals out there. Perhaps just a field that you can specify "once I am connected to this AP, run this script: ".

== Wireless Piggyback ==

HSDPA support and the like, so that users can connect directly with the internet with G3/G4 mobile service providers at speeds at or above 3.6 Mb/s.

== Other ==

=== Auto Update ===

A small tool which is configurable to download the latest OpenMoko and OpenMoko related software. Maybe if any internet connection is available or a minimum of bandwith is available then the auto update would download only security related or the whole system etc. .

=== Vibrate Pattern Recorder ===

An application that would allow the user to define their own vibration patterns, and possibly link them to audio files. Recording would be done in real time initiated with a "Record" button, optionally playing the associated sound file in sync with recording). While recording, the user would press and hold a button to define the timing and duration of vibration. The user would press "Stop" when finished. Vibration patterns would have the option of being looped(would terminate at some global ringtone length maximum).

One simple suggested vibration file format would be a sort of run-length encoding: First byte defines the length of a "time-slice" in milliseconds, which would determine the overall tempo(actually the inverse of tempo). The next byte would define the number of time-slices to leave the vibration on, and then another byte for how long to pause after. Continue alternating these on/off bytes until the entire pattern is defined.

- or just use MIDI, using a separate channel for the vibrator.

An implementation of RTTL could also be used to define vibration patterns.

=== PC Input Device ===

Provide a method to use the touchscreen as input device for a nearby desktop machine. Could connect over USB or bluetooth.

=== Advanced Notification And Ringtone Manager ===
{{Main|Wishlist-ANARM}}

ANARM would be an application for handling all event-based audible notifications from an OpenMoko device.

=== Location based reminders ===
{{Main|Wishlist:Location_based_reminders}}
Location based reminders can be used to notify users of various events or reminders that are location based.

=== Synergy Client ===
A synergy client would enable the user to place the device next to a desktop PC and share the desktop`s mouse, keyboard and clipboard over a TCP/IP network. [http://synergy2.sourceforge.net/ Synergy]

== GPS Software ==
*Providing GPS Support also for outdoor users in addition to ordinary street navigation features
** Overlay of satellite images with existing streetmaps
** Incorporating SRTM digital elevation model: for example using the VRML/X3D as data format (see http://www.ai.sri.com/geovrml/) which is interesting for e.g. mountaineering: using a 3d browser rendering VRML/X3D Model, displaying the current position and track (possibly also other gps-tracks of the different routes to a summit downloaded before could be mapped onto the 3d model), (what about 3d hardware support? there is nothing written in the hardware specs about graphics: thinking of OpenGL for embedded systems (see http://www.khronos.org/opengles/)
** Using sth like a tracking mode to allow certain people to determine the current position and track (for rescue missions - like they have for example at http://www.steiger-stiftung.de (a German beneficence for rescue issues) There you can register your mobile phone so the rescue service is able to track you immediately if necessary. The interesting thing: It seems like some mobile phones with GPS have special support for this issue. If your phone is registered, the rescue service is able to get your GPS coordinates directly from the phone without any user assistance. Openmoko should also support this! )
* Implementation of 3dTracking's (http://free.3dtracking.net/) tracking software or equivalent.
* "Geomark" function: if you have to save the current time with your current location, only hit one button...
** You also should be able to navigate with a small "compass" and the distance should be displayed to your saved point (maybe where you parked your car on a big car parking area)...
* '''Measure the distance between two points (air line or walked way) -> no need for a tape measure'''
**I think it would be good if you could either use Bluetooth, GPRS or AdHoc Wifi, and see near Neo1972 on the GPS map so you could see where your friends are, e.g "You want to know if you friend is on the bus behind" You would need a strong wifi and GPRS would be too expensive.
*A bicycle sat-nav would be cool, speciayl designed for bicycles, e.g. cycle routes

<br>[[Community Based Traffic Information]]

== Hardware ==
{{Main|Wish List - Hardware}}

It could be use for beepway Online service too
[http://www.beepway.com]

=== Tactile feedback via buzzer ===
Assuming the hardware has a vibrator/buzzer for silent calls, use a lightly pulsed version of that to simulate tactile feedback when dragging finger across buttons on-screen. Implemented properly, it would almost feel as if the buttons were real.
: 25 ms bump on the buzzer feels about right. Does this harm the vibrator motor? --[[User:Sagacis|Sagacis]] 05:15, 2 October 2007 (CEST)
:: Created a patch to do this [[User:Sagacis/ForceFeedback]] --[[User:Sagacis|Sagacis]] 05:05, 3 October 2007 (CEST)

=== Detachable keyboard ===
Hardware keyboard that can be attached with magnets to a future version of the Neo.

=== SD Slot ===
I think the Neo1973 should have a normal SD card slot as the micro is too small, and the SDs have more space.

: This is not true. Now you can find 2GB micros at the price of 20-30 euros. Too small for what?? --[[User:V0n0|V0n0]] 22:06, 28 December 2007 (CET)

=== IR port ===
Remote control applications
Would be great to use openmoko as a Hamony remote controller.

[[Category:User]]
[[Category:Ideas| ]]

User:Tommy

2007-11-06T23:59:26Z

Tommy:

http://neo101.org/public/tommy/spam_this.png

User:Tommy

2007-11-06T23:56:14Z

Tommy:

andersonthomas at gmail

Talk:November 6, 2007 Community Update

2007-11-06T23:53:14Z

Tommy:

How many of you must have 850 MHz support, and would be satisfied with an 850/1800/1900MHz variant, and how many of you must have full quad-band?

Note that by asking this question we do not promise to provide these options.

Please put your answers below:

'''Must have an 850/1800/1900MHz variant'''
* -- [[User:Mwester]] 06:46, 6 November 2007 (CST) - This thing is nothing but an extremely expensive PDA without 850 support. It should do what it was claimed it could do when it was sold (quad-band), but I can live with taking a real phone with me when travelling internationally.
* -- [[User:ShakataGaNai|ShakataGaNai]] 03:34, 6 November 2007 (CET)
* -- [[User:Aking|Aking]] 21:55 EST, 2007-11-05 - Live/work in a Rogers 850 only zone
* -- [[User:Matt|Mattdawg]] 19:57 MST, 6 November 2007
* -- [[User:Writchie|Wally Ritchie]] 10:02 EST, 6 November 2007 - GTA02 MUST support largest US GSM carrier.
* -- [[User:Digger|Digger]] 04:15, 6 November 2007 (CET) - But for the money would prefer quad-band
* -- [[User:Wisp|wisp]] 04:29, 6 November 2007 (CET) - But for the money would greatly prefer quad-band
* -- [[User:WJCarpenter|WJCarpenter]] 19:45, 6 November 2007 (PST)
* -- [[User:Angus|Angus]] 20:59, 5 November 2007 (MST) - Required for Rogers in Canada
* -- [[User:Montgoss|Montgoss]] 22:34 CST, 5 November 2007 - Frequently in areas that use 850 band.
* -- [[User:Xaid|Xaid]] 21:12, November 5th, 2007 (MST) - Rogers Wireless in Edmonton uses both 850/1900 bands.
* -- [[User:Mmontour|Mmontour]] 06:45, 6 November 2007 (CET) - So far I've been able to use my phone with 1900 only (Fido in Vancouver, BC) but I do sometimes travel to 850-only areas.
* -- [[User:Romulus|Romulus]] 07:31, November 6th, 2007 (PST) - I'm with Rogers and will need 850 when on the road.
* -- [[User:Mary|Mary]] 11:24, November 6th, 2007 (EST)
* -- [[User:Algo|Algo]] 13:17, November 6th, 2007 (EST) - I'm with Rogers too and i need the 850 band to get a full coverage. It's a no go no show until the phone can support it.
* -- [[User:GaidinTS|GaidinTS]] 13:52, November 6th, 2007 (CST) - I'd have to start looking for a new phone, if this one didn't support 850.
* -- [[User:wurp|wurp]] 14:27, November 6th, 2007 (CST)
* -- [[User:Techiem2|Techiem2]] 16:03, November 6th, 2007 (EST) - This would be the minimum for me to use as a phone as I live in an 850 /1900 area. Ideally quad band so I could use it if I ever travel.
* -- [[User:LeeColleton]] 14:35, November 6th, 2007 (PDT) - I won't buy the phone without 850 support, but I'm hesitant to get such an expensive tri-band phone.

'''Is OK with the current 900/1800/1900MHz variant'''
* -- [[User:BlueStar88|BlueStar88]] 11:50, 6 November 2007 (CET) - 900 (D1-, D2- and O2-Network) and 1800 (E- and O2-Network) are essential in Germany
* -- (Most of Europe? From my quick bit of research, it seems 850Mhz is only needed for the US, Canada, Anguilla, Ecuador, Montserrat, Panama, St. Kitts and Nevis, Turks and Caicos Islands )
* -- [[User:C.M|C.M]] 06:44 CST, 6 November 2007 - 850 would be nice, but I don't need it.
* -- [[User:Avanc|Avanc]] 08:52 CET, 6 November 2007 - 850 would be nice, but I don't want to miss 900
* -- [[User:PT|PT]] 08:27 GMT, 6 November 2007 - 850 would be nice but the other three are more important for me
* -- [[User:s.decken|s.decken]] 10:49 GMT, 6 November 2007 - 850 would be nice but not required
* -- [[User:PiotrDuda|_alcik_]] 11:55 GMT, 6 November 2007 - I really need the 900.
* -- [[User:Mic|Mic]] 12:15 CET, 6 November 2007 - in Europe is 900 essential
* -- [[User:Mockenh|Mockenh]] 12:45 CET, 6 November 2007 - need 900 (Germany)
* -- [[User:Psmears|Psmears]] 14:55, 6 November 2007 (CET) 900/1800 covers most of the world; 1900 covers enough of USA/Canada to be useful for short trips.
* -- [[User:Placid|Placid]] 18:52, 6 November 2007 (CET) - UK, T-Mobile, OK with tri-band.
* -- [[User:Vegar|Vegar]] 16:46, 6 November 2007 (CET) - 850 would be nice, but the other three are much more important
* -- [[User:einalex|einalex]] 17:04 CET, 6 November 2007 - in Germany/Europe GSM 900 is a must-have. For me, 850 is optional.
* -- [[User:PBeck|PatrickBeck]] 17:45, 6 November 2007 (CET) I live in germany, so is 850 optional for me. But quadband would be nice.
* -- [[User:AVee]] Same as above, having a hardware/software switch for 850/900 would help as well.
* -- [[User:Dread|Dread]] I'm from Germany too, for me, 850 is optional.
* -- [[User:Haakeyar|Haakeyar]] 19:42, 6 November 2007 (CET) I live in Norway.
* -- [[User:Henrikw|Henrikw]] 20:57, 6 November 2007 (CET) I live in Norway.
* -- [[User:lizardb0y|lizardb0y]] 08:35, 7 November 2007 (NZDT) I could personally live with the 900/1800/1900 variant but this would limit it's use to 1 of 2 New Zealand GSM providers. Being able to switch between 850/900 would be extremely beneficial to the NZ market as we have providers on both. See [http://www.gsmworld.com/roaming/gsminfo/cou_nz.shtml] for details.

'''Must have full quad-band support''' (note that this is not for GTA01 or GTA02)
* -- [[User:Elektrolott|Elektrolott]] 18:45 (PST), 2007-11-05 - I live in the US and travel to Europe, so Quad Band is a must. As you noted this will not be for GTA02, so when (if at all) can we expect the promised 4 Band?
* -- [[User:ClashTheBunny|ClashTheBunny]] 04:03, 6 November 2007 (CET) - Right now I live on the North Shore of Boston and most places are 850
* -- [[User:Sagacis|Sagacis]] 04:16, 6 November 2007 (CET) - The phone is a brick to me without 850. International travel means I need all four bands.
* -- [[User:Davemaster|Davemaster]] 21:47, 5 November 2007 (ET) - International travelers, Me and my group (company) deals all over. We need all four bands.
*-- [[User:Rakshat|Rakshat]] 05:40, 6 November 2007 (CET) - For travel in the US, otherwise I am ok with the 900/1800/1900Mhz variant
* --[[User:NeilenMarais|NeilenMarais]] 15:37, 6 November 2007 (CET) - For travel to US also
* -- [[User:Jaebird|Jaebird]] 09:00, 6 November 2007 (CST) - The phone should be refundable to me without 850 (It was sold as a quad band phone, it is NOT). International travel means I need all four bands.
* -- [[User:Mmanjos|Mmanjos]] 21:25, 6 November 2007 (CET) - I absolutely need 850 or else the phone is useless to me, but for the money, it should support quad-band.
* -- [[User:Friedrij|MacNorth]] 15:46, 6 November 2007 (CST) - I travel internationally often and need a phone that works everywhere GSM can be found.
* -- [[User:Tommy|Tommy]] 00:53, 7 November 2007 (CET) - I want to get a copy of this mobile as soon as it is finished and released. If I however would have to wait a reasonable extra amount of time to get a quad-band instead of tri-band version, I would prefer to wait. I will very likely not buy a tri-band version.

Neo 1973

2007-10-19T16:29:51Z

Tommy: /* Estimated time line */ What was the flaw?

[[Image:FIC-neo1973 small.jpg|120px|right]]
The [[Neo1973 Hardware | Neo1973]] is the first phone designed to run [[OpenMoko]].
It is a phone that can be used with any [[GSM]] operator, and it is manufactured by [[FIC]] who instigated the [[OpenMoko]] project.

If you just received a Neo1973 here are some suggestions for [[Getting_Started_with_your_Neo1973 | getting started]].

[[Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]] have more information on the hardware.

See [[OpenMoko]], [[OpenMokoFramework]], [[MokoMakefile]] and [[Development resources]] for more information about source code.

See [[FAQ]] for other Frequently Asked Questions.

There is some SVG [[ClipArt]] for simple illustrative purposes.

== Phase 0 (GTA01Bv3) ==
:''Main article [[Neo1973 Phase 0]]
:''See also [[Wishlist:Neo1973_P0_Review]]
36 developers have received their devices. [http://lists.openmoko.org/pipermail/announce/2007-March/000006.html]

== Phase 1 (GTA01Bv4) ==
:''Main article [[Neo1973 Phase 1]]
You can order from https://direct.openmoko.com/ now. See also the [[Group Order]] page.

The Neo Base costs $300, the Neo Advanced costs $450.

See [[Neo1973_Hardware#GTA01Bv4|Neo1973 Hardware]] for what components GTA01B_v04 contains.

Neo Base -- everything the mobile application developer needs to enjoy
the benefits of the first freed phone, the Neo1973:

* Neo1973 (GTA01B_v4)
* Battery (1200mAh)
* Stylus
* Headset
* Phone Pouch
* Lanyard
* SanDisk 512MB MicroSD Card
* Mini USB Connectivity Cable

Neo Advanced -- everything the mobile device hacker wants to get down
and dirty with the first freed phone, the Neo1973:

* Neo1973 (GTA01B_v4)
* Battery (1200mAh) (2x)
* Stylus
* Headset
* Phone Pouch
* Lanyard
* SanDisk 512MB MicroSD Card (2x)
* Mini USB Connectivity Cable (2x)
* Debug Flex Cable
* Debug Board v2 (JTAG and serial console)
* Ruggedized Toolbox with shoulder strap
* Guitar Pick (for opening case)
* Torx T6 screwdriver

You do not need the Advanced package to do normal kernel, or application development, only perhaps hacking on [[u-boot]].

As described in [http://lists.openmoko.org/pipermail/community/2007-June/006005.html Sean's post on mailing list] (with some adjustments/corrections).

== "Phase 2" (GTA02, "Mass Market") ==
The device will hopefully go on sale for developers in December, with mass-market to follow when the software is ready. (Seemingly confirmed at OpenExpo, see [[Talk:Neo1973|Talk page]])

=== Estimated time line ===

* Sep 20 - GTA02v3 design finalized.
* Sep 25 - GTA02v3 [[serious flaw found]], GTA02v4 needed.
* Oct 15 - GTA02v4 design finalized.
* Oct 30 - GTA02v4 design produced, and shipped to qualified developers.
* Nov 20 - GTA02v4 design verified through testing by developers.
* Dec 10 - GTA02v4 produced in moderate volume
* Dec 20 - GTA02v4 goes on sale
* Dec 25 - GTA02v4 arrives. See [[Santa's Sleigh Package Service]].

It will have the following new hardware components:[http://lists.openmoko.org/pipermail/community/2007-July/008458.html]

* 802.11 b/g WiFi
* Samsung 2442 SoC
* SMedia 3362 Graphics Accelerator
* 2 3D Accelerometers
* 256MB Flash
* 1700mAh Battery
* Faster CPU - S3C2442/400
* LEDs illuminating the two buttons.

It will also lose:
* One speaker, becoming mono.

We will sell this device through multiple channels. Direct from
openmoko.com, the price will be $450 for the Neo Base and $600 for Neo Advanced.

Adds to the Phase 1 phone (see [[Neo1973:_GTA01Bv4_versus_GTA02_comparison|side by side comparison]]):
* 2D/3D-Graphics-Accelerator
* 2 Accelerometers (model and number is uncertain)
* Faster CPU - S3C2442/400
* WiFi: [http://lists.openmoko.org/pipermail/announce/2007-April/000012.html Atheros AR6K] (see also [http://lists.openmoko.org/pipermail/community/2007-April/004934.html])
** Above from [http://sicherheitsschwankung.de/gallery/v/openmoko/IMG_8662-slide.JPG.html] '' and other sources
* There will be no changes in the external housing, but internal plastics change. http://lists.openmoko.org/pipermail/community/2007-July/008458.html] [[http://lists.openmoko.org/pipermail/community/2007-March/004255.html]

<span id="bottom"></span>

{{Languages|Neo1973}}

[[Category:Neo1973 Hardware| ]]
[[Category:Neo1973_Phase_0_related| ]]
[[Category:Neo1973_Phase_1_related| ]]
[[Category:Neo1973_Phase_2_related| ]]

Wishlist/Accessories

2007-08-23T01:34:08Z

Tommy: /* Wishlist */ Added section Make a VGA and/or DVI out connector

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

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

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

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

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

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

Wish List - Hardware

2007-08-23T01:21:27Z

Tommy: /* Input devices */ Added section: Make ''all'' unlocking of phone, password protected

This page details hardware features which some would like to go into future phones similar to the [[Neo1973]].

Related pages are:
*[[Wishlist - Hardware - Novel Devices]] - openmoko will run on a large number of devices in the future, some of which may be DVD players, cameras, or convergance devices.
*[[Wishlist:Unlikely]] - Hardware that is unlikely to appear in any OpenMoko device, due to it being impossible to fabricate with near-term technology, or for other reasons.
*[[Wishlist:Accessories]] - Accessories that people would like, that connect easily to the phone - initially primarily for the Neo1973
*[[Wishlist:Expansion]] - add-ons to the phone, maybe involving hardware changes, and software and hardware protocols to implement these.

This page is rather long. Before adding a new idea, please read through this page and the above pages, to make sure your idea has not been suggested before.

==Processor==
===AT91CAP9S500A (ARM9 + FPGA-port)===
Take a look at this microcontroller, that integrates an ARM9 microcontroller and a dedicated FPGA port: AT91CAP9S500A. It has "only" a max. clock at 200MHz, but can use a FPGA for hardware acceleration, that could be used for video (de)compression, [http://en.wikipedia.org/wiki/AacPlus_v2 aacPlus v2]/[http://en.wikipedia.org/wiki/HE-AAC_v2 HE-AAC v2] sound (de)compression and many other things. HE-AAC v2 is better than [http://en.wikipedia.org/wiki/MP3 MP3].
*[http://www.atmel.com/dyn/products/product_card.asp?family_id=689&family_name=AT91CAP+Microcontrollers&part_id=4137 AT91CAP9S500A] Quote: "...The AT91CAP9S500A is built around a 12-layer bus matrix, allowing a maximum internal bandwidth of twelve 32-bit buses. Its distributed DMA architecture enables multiple data transfers to take place between the processor, memories and peripherals with minimal processor overhead...".
*[http://www.atmel.com/dyn/resources/prod_documents/doc6310.pdf GNU-Based Software Development on AT91SAM Microcontrollers]
*Maybe this is a good tool?: [http://www.jhdl.org/ BYU JHDL, Open Source FPGA CAD Tools]
*[http://www.eetimes.com/showArticle.jhtml;?articleID=197002705 02/05/2007, FPGA tool bottleneck stalls HPC] Quote: "...Current FPGA synthesis, placement and routing tools are written for hardware designers, not software programmers simply trying to accelerate an algorithm..."

This seems to be a good hardware mix (ARM+FPGA). It does [http://en.wikipedia.org/wiki/Theora Ogg Theora] or [http://en.wikipedia.org/wiki/MJPEG MJPEG] in the FPGA with 1 million gates:
*http://sourceforge.net/projects/elphel, [http://wiki.elphel.com/index.php?title=10353 board 10353], [http://wiki.elphel.com/index.php?title=Camera_hardware camera hardware], [http://wiki.elphel.com/index.php?title=Main_Page Main page], [http://www.elphel.com/articles/index.html Imaging solutions with Free software and open hardware]

Just another FPGA+microcontroller example:
*[http://melzer.ch/html/body_alya.html The Alya Project] ([http://home.nikocity.de/andymon/hfg/Alya/alya.html old page])
*[http://melzer.ch/ALYA.ASM PIC assembler source code], [http://melzer.ch/ALYA.TDF Altera FPGA code]. Schematic: [http://melzer.ch/Schaltplan1.gif], [http://melzer.ch/Schaltplan2.gif], [http://melzer.ch/Schaltplan3.gif]
*[http://hardware.silicon.com/servers/0,39024647,39166443,00.htm?r=1 20 March 2007 Green supercomputer is 'go' in Scotland]

==Possible FPGA==
This FPGA is just an example:
*[http://www.xilinx.com/products/silicon_solutions/fpgas/spartan_series/spartan3an_fpgas/capabilities/index.htm Spartan-3AN FPGA Capabilities] Quote: "...Simple and secure embedded application storage with up to 11Mb of integrated user Flash...Enable simple arithmetic and math functions as well as advanced DSP functions to derive over 330 Giga MACs/sec...Up to 32 18 x 18 embedded multipliers support 18-bit signed or 17-bit unsigned multiplication, and can be cascaded to support wider bits..."
**XC3S1400AN-4FGG676CES $91
**XC3S200AN-4FTG256CES $25.87

Tool for FPGAs:
*[http://www.xilinx.com/ise/logic_design_prod/webpack.htm xilinx.com: ISE WebPACK is the industry´s only FREE, fully featured front-to-back FPGA design solution for Linux, Windows XP, and Windows Vista]
==Internal Memory==
===RAM===
128MB Dedicated for open files, running software etc. not for storage.

===ROM===
Enough to Hold O/S and a fair number of applications and their settings. Persistent Storage with XIP capability
===Storage===
An internal Micro SDHC should be used for users' files and additional software

==Wireless data networking==

===WiMAX support===
[http://en.wikipedia.org/wiki/Wimax WiMAX] is a high-speed data service, similar to wifi, though longer range and newer. Where service is available, this would complement WiFi. Unfortunately, unlike wifi, frequencies vary worldwide, so global usage may be complex.

===Emerging Protocols===
*[http://en.wikipedia.org/wiki/Near_Field_Communication Near Field Communication] has a few centimeter range, useable for keys, ID badges, pairing bluetooth devices and similar uses. Mentioned in newer bluetooth and SD standards. (No products.)
*[http://en.wikipedia.org/wiki/ZigBee ZigBee] is designed for connecting sensors and switches in buildings, with many options including mesh networks and aggressive power saving compared to bluetooth. (Almost no products available.)
*The [http://en.wikipedia.org/wiki/ANT_%28network%29 ANT network] is for connecting worn devices. Similar to ZigBee, but much simpler and maybe lower power. ([http://www.thisisant.com/?section=9 Short list] of products.)

==Camera==

* A camera that can take reasonable quality video and pictures is something many want. Applications vary from simple snapping, to gesture interfaces, video conferencing, barcode reading, buisness card reading, healthcare, servicing, 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 or leave the camera chip in place and have a removable lens assembly and replacement backcover.

* See [[Wishlist:Camera]] for a more detailed wishlist.

==Display==
===Multitouch screen===

''Main article: [[Wishlist:Spell_weaving|Spell weaving]]''

See also [http://pogue.blogs.nytimes.com/2007/03/27/the-multi-touch-screen/ this page] containing a link to a video demonstration.

A history of multitouch implementations is [http://billbuxton.com/multitouchOverview.html here] ([http://google.com/search?q=cache:billbuxton.com/multitouchOverview.html google cache version])

===Distance sensing touchscreen===
{{Main|Hardware:NearlyTouchScreen}}
TouchKo's (now Wacom Company Ltd.) spatial capacitive "touchscreen", can sense fingers at a small distance, so you do not get your display greasy, and can unlike some touchscreens, be operated with gloves.

===Video acceleration===
Hardware acceleration for video playback and 2D/3D accelleration will be present in [[Neo1973 GTA02]].

===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, lightweight, 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].

Pro: laserprinter like quality, glossy, very stable image, easy on the eyes. Electronics are similar to TFT. Very low power consumption.

Con: Black and grey only (like a newspaper, but glossy), although there were already color prototypes in 2005. low framerate (5fps). Can reflect light (like paper), backlight is impossible.

===Transreflective===
It would be nice to have (the option of) a transreflective display, which while being less bright, is readable without needing to power the backlight. Then again, it depends on how much power the backlight uses compared to everything else...

==="Slightly" Larger Screen===
43mm x 57mm (2.8inch diagonal) is tiny. A 53mm x 71mm (3.5 inch diagonal) like on the TD035STEE1 would be a nice improvement. A widescreen format at about 53mm x 82.5mminstead of the 3:4 aspect ratio would be even cooler (if one could be found).

===Second Display===
A 32x32 OLED display possibly on the back for camera framing or on an edge so it can be viewed like a pager.
This could be used to display any number of alerts (from any installed software) the alerts could have a dynamic prioritisation which means during the work day a message from the boss has high priority but lower at home (could be GPS/Time controlled?) multiple alerts shrink the icons to a 3x3 grid higher priority messages get more space.

==Input devices==

===No Dependence on Stylus===
The Neo's basic functionality should be completely usable without a stylus, Like the iPhone but with stylus use for precision work.

===A laser projection keyboard===
Similar to [http://www.thinkgeek.com/computing/input/8193/ this], except the device would be integrated into the phone itself. Setting the Neo up on a stand on a flat surface (perhaps a stand could be built into the back of the Neo itself, or into a case) would turn the Neo into a micro-laptop. There may be several issues with the inclusion of this technology, including patents, the space required to project the laser grids, and the power consumption. If possible, however, it would make text input a breeze.

===Just a few more Buttons===

2 buttons more, 3 buttons total, mounted sideways would be enough. You could use them for play/pause and loudness controll while the phone remains in your pocket (display locked, ...), reading mails, rss, ebooks,... without wasting display space and so on.

With 5 buttons in total you could possibly emulate a keyboard (2^5 = 32 combinations) for those who know how to play a flute. Useable onehanded, not wasting display space and faster than t9. (It's not faster than T9 - I've used this system with the microwriter agenda --[[User:Speedevil|Speedevil]] 00:00, 2 July 2007 (CEST)) Hopefully this is not patented already.

===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 best 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 good for many for emulation games.

Here is a concept drawing of a possible neo1973 gaming version:
(This has a 4-way direction pad, 8 way may be better for gaming)
<br/>
[[Image:Neogame90.jpg]]
<br/>
Shoulder buttons would be a great addition, too. It would be interesting if there was a total 4 of them, one for every corner. It would make the phone very flexible for rotating and 2 to 6 players playing on one device.
<br/>

===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
*One of the layouts proposed in [[Hardware:Keyboards]]
* What about virtual keyboard? [[http://www.extremetech.com/article2/0,3973,539778,00.asp Keyboard]]

===Analogue Controllers===

====Trackball====
A trackball would provide an efficient mouse-like interface in a very compact package. As exemplified in the newer Blackberry® models.
Maybe instead an optical sensor as are used in mice could be used so that the whole phone can be moved over a surface just like a mouse. (It could function as a Bluetooth mouse for other devices like laptop computers: see [[Bluetooth_Support#Acting_as_HID_device]]. Adding one other two-axis analogue input (possibly just the screen) would make the Neo usable as a TrackPoint or scroll-and-tilt mouse.) The same sensor might be usable as a barcode reader.

====Analog Joystick====
A joystick, or [http://www.extremetech.com/article2/0,1697,1772689,00.asp Rollermouse]-like device would provide additional control, compared with touchscreen only.
*A standard [http://en.wikipedia.org/wiki/Pointing_stick pointing stick (ie. TrackPoint)] might serve well. As a fairly standard part, might they be quite inexpensive?

====Dual analogues====
Dual analogue controllers (one trackball or joystick above, one below the screen, most likely) might even be feasible. That might be overkill since the accelerometers or touchscreen can be used to provide a second analogue input. But it would be nice to have four axes of analogue control without having to tilt the screen away from you or partly cover it with your hand.

===TV/radio receiver===
[[Digital Television]], [[Digital Radio]] or even normal analogue TV/radio is available widely in the world. Though unfortunately in various different forms. In markets where one standard is widespread, and hardware is suitable, it would be a great extension of the phone to a general entertainment device for when you're away from home. Multi standard devices would be ideal, but may not be small, low-power, or cheap.

===Accelerometer===
This enables the phone to sense which direction 'down' is, and to sense any movements the phone makes.

See [[Accelerometer Fundamentals]] for more information on accelerometers as they may be used in phones.

In some cases integrated gyroscopes may also be needed. A [[#Digital compass]] can even be of more use since it gives absolute rotation so slow rotations could also be measured. A 3D compass would be nicest, but a simple 2D compass already is a helpful addition to the accelerometers.

*[[Wishlist:3D Viewport|3D Viewport]]
*[[Wishlist:Computer Mouse|Computer Mouse]]
*[[Wishlist:Determine Position|Determine Position]]
*[[Wishlist:Dynamic Screen Orientation|Dynamic Screen Orientation]]
*Change media player playlist when jogging vs walking.
*Attempt to use to stabilise any future camera.

This feature is scheduled for inclusion in the phase 2 Neo1973, currently slated for release in October 2007.

===Side-Mounted Touch Strip===
Add a "touch strip" sensor onto the side of the phone which can be used to scroll. By having it on the side you can use your thumb to scroll comfortably while holding the phone one-handed. An 8-element capacitive sensor would work wonderfully and be easy to fab using either a Quantum QT411 (http://www.qprox.com/products/qslide_qt411.php) or Analog Devices AD7143 (http://www.analog.com/en/prod/0,2877,AD7143,00.html) controller. The Analog Devices chip seems better suited due to it's smaller allowable element size.
*With the AD7143 you can have an 8-element (128-position) 25mm long strip - Perfect!.
*With a few OLED screens beneath the strip it could be used as dynamic configurable buttons/alerts eg. zoom/flash/shutter with a camera application and SMS/Email/Voicemail alerts in standby

===Heart Rate Compatibility===

An RF interface to receive data from popular heart rate straps (Polar, Garmin, Sigma, Suunto, etc.). This would go along well with the existing GPS functionality and possible future Accelerometer functionality to make for a full-blown workout tool.

Software can be written to track heart rate along a running, cycling, skiing, swimming loop, to monitor max and min heart rate, to match heart rate data to GPS coordinates and print map data w/ relevant data.

===Digital compass===
A digital compass is useful for orienting maps to the terrain and other location/direction/orientation based applications (... is 300 meter that way) when the user is standing still (regardless of GPS reception) and for following a bearing when GPS reception is poor or speed is low. Also could be used to make the accelerometer data more exact.

Very small [[I2C]] sensors like [http://www.ssec.honeywell.com/magnetic/hmc6352.html Honeywell's HMC6352 2-Axis Digital Integrated Compass] (6.5 x 6.5 x 1.5 mm) are very appropriate for this.

*[[Wishlist:Auto Align Map]]

See [[Wishlist - Hardware: Digital compass]] for more information

===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].
(Could just be cheap and use the thermometer from the battery, thats how they did it in the nokia 5140's). Also is integrated in a barometer/altimeter like the SMD500 mentioned in [[Wish List - Hardware - Atmospheric]].

===Barometer and Variometer===

A Barometer measures air pressure. This can be used to give weather information, and also as a variometer, to sense relative altitude. Variometers are commonly used in flying microlight and ultralight aircraft, to get accurate relative altitude.

See [[Wish List - Hardware - Atmospheric]] for more information.

===Finger print sensor===
A 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].

Most fingerprint sensors in the embedded market include a navigation mode, where they work similar to either a touch-stick or touch-pad of a laptop.

===Barcode Scanner===
*less cpu intensive and more reliable than camera+ocr
*though, bluetooth-enabled readers are already available.

===Light Sensor===
Ability to sense ambient light, and act accordingly. i.e if it's 3am and LightValue<.1 then Ring Quietly.

===Wheel===
A navigation wheel like on a sony/ericsson 810i would be nice.

===Proximity Sensor===
Switch off backlight when you place the phone to your ear. Prevent accidental activation of speakerphone or other sounds when the phone is near the ear (prevent hearing damage). Possibly switch the speakerphone on or off automatically depending on if the phone is by your head or not.

=== Make ''all'' unlocking of phone, password protected===

When my (current non-neophone) phone is in my pocket and I have it locked, it sometimes accidentally unlocks itself since only two keystrokes in the correct order are necessary to unlock it. When it's unlocked and still in my pocket it sometimes calls someone without my knowledge. All phones I've seen today have a press-just-one-button bypass to answer an incoming call even when the phone is locked. I suggest making the locking mechanism let the user configure it so that the user has to enter a password even for answering incoming calls. The likeliness of the phone accidentally runbbing against my car keys, hitting a ten character long password, unlocking the phone without my knowledge and consent is low enough even for us most unlucky users.

==Expansion==
===Positioning of Buttons, Connections and ports===

Ideally any cable ports such as charging, USB, audio, docking should not get in the way of your hand or fingers when holding it in it's normal orientation. For the sake of SDIO cards an external SD slot should be on the top edge. IR for remote control software and ease of inter-device communication should be on the corner so that it is facing away from you for both orientations. Buttons obviously are positioned for finger control. An example of how '''not''' to do this would be the HTC Universal

===Storage===

====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 accessories, including SDIO accessories.
*Make externally available so that larger length SDIO cards can be used (thinking about SDIO WLAN here)
*[http://en.wikipedia.org/wiki/Secure_Digital_card#SDHC SDHC] compatible. It seems to already have the right hardware for it - see [[Neo1973_Hardware#microSD-Card]].

====Two SD slots====
*Micro SDHC for /home partition. Keep like current design underneath SIM card
*Hot swappable externally accessible normal size SDHC/SDIO slot

===Local Communication===

====USB====
* 5V Powered, to avoid having to carry around a hub for when you want to occasionally plug in a memory stick. Many powered hubs will not recognize a totally unpowered host. Provide a maximum current to drive a basic USB keyboard/memory stick(/mouse?). This could be done by adding a small cheap power converter like the [http://www.national.com/pf/LM/LM2753.html LM2753]
* USB 2.0
* Standard type A socket for quick & easy insertion of memory sticks etc.
* OTG (is this maybe supported already ?)
* Bootable USB device emulation: the possibility to boot any computer on a bootable flagged partition of the transflash.
* Protection against incorrectly wired USB ports: some USB ports are wired incorrectly; if the +5V and GND are swapped, the device would get -5V when it's expecting +5V, which could burn some chips. A reverse-biased diode between +5V and GND, D+ and GND, D- and GND, and (if used) ID and GND, with a low enough forward voltage drop (to limite the negative voltages to what the chips can withstand), would protect the device by tripping the port's short circuit protection.

====Wireless USB support====
[http://en.wikipedia.org/wiki/Wireless_USB Wireless USB] is the wireless version of USB offering data-rates up to 480 Mbit/s over short distances (<3 meter). Chipsets suitable for a phone are likely to take some time to be available.

====SIR/FIR transceiver (Serial Infrared) / IR remote control====
*An infrared transceiver is cheap, small, and useful for sync with many laptops and mobile phones.
*Replace/emulate all IR-based remote controls used for your tv, vcr, etc on your neo cell phone.
** replaces multiple 'dumb' devices with a single intelligent device (your neo) that you will probably carry with you at all times anyway.
**Command sets should be retrieved from a database or learned from other less intelligent remote control devices with macros.
**reduces clutter, particularly in the living room.
**inceases the neo's practical status as an 'always-have' device.

Other uses.
*Detecting reflections from inside of a caddy, and switching from active mode.
*FIR would be a nice option, as it's some 40 times faster than SIR.

===Other===

====Video Out====
*Through a docking port
**S-Video/Composite Out
**DVI Out

==Output devices==

===LED===
*The Neo1973 GTA02 will have LEDs of some sort behind at least one button. [http://lists.openmoko.org/pipermail/community/2007-July/008458.html]
*A blinking LED would be a cheap, low power way to inform the user of new SMS/Email....
**An alternative to this would be for one small part of the LCD to be separately backlit.
**This requires the CPU and LCD to be somewhat active, to keep the LCD refreshed, but gives much more information.
**A Small OLED Screen could be used and display much more information than a LED with minimal power usage.

*For example a multicolor LED which pulses yellow for GSM/GPRS transmit, blue for Bluetooth/Wifi, green to indicate non-urgent information - missed call etc, red to indicate battery low or other urgent notices.

**The LED and button ideas could be combined: illuminated buttons.
**It must be possible to completely disable the LED to save power or other personal preferences.

=== Flashlight ===
For finding keys, or any other application. May also optionally pulse in time with ring, to make phone more visible.
This is really well done in Nokia 5500.

=== FM transmitter ===
Small FM transmitter to output to car, and other nearby radios.

===HAC Compliance===
[http://quux.wiki.zoho.com/WhereAreHACphones.html Here] is some summary/discussion of how hearing aid compliance rules work in the US. Specifically it would be nice to see the phone include a [http://www.hearingresearch.org/Dr.Ross/telecoil_and_telephones.htm telecoil], which allows the phone to connect wirelessly to many standard hearing aids.

==Mobile Communication options==

===Generic Access Network / Unlicensed Mobile Access===
This technology requires cooperation from the cellular provider, but [http://en.wikipedia.org/wiki/Unlicensed_Mobile_Access UMA/GAN] is already offered by T-Mobile in the United States, and perhaps others in other countries. Allowing the user to roam from GSM to wifi, this technology can save the end user a significant amount of money, and also allow the user to deploy coverage where there was none before. There are only a few UMA capable phones currently, but it would be great if this could be made to work on a phase 2 type OpenMoko device.

Note that this features requires a more advanced access to the GSM modem. Special messages needs to be exchanged with the network.

===Faster/better mobile connectivity.===
[http://en.wikipedia.org/wiki/Gsm GSM]/[http://en.wikipedia.org/wiki/GPRS GPRS] is at best slow. An incremental improvement would be a radio with [http://en.wikipedia.org/wiki/EDGE EDGE ] support. EDGE is an evolved GSM standard and, like GPRS, it operates on the same frequency as voice. This means a quad-band EDGE radio will have near-complete worldwide coverage.

[http://en.wikipedia.org/wiki/UMTS UMTS] - which is widespread in Europe and being deployed in the US, [http://en.wikipedia.org/wiki/HSDPA HSDPA] (asia) and any other mobile standards would be nice for faster data connectivity and coverage.
It is unlikely that all of these will be supported initially, but it is a goal. These faster standards operate in different frequencies from GSM/GPRS/EDGE. Which frequency exactly will depend on the carrier and country. For UMTS in the US, AT&T uses 850/1900 MHz but T-Mobile will use 2100/1700 MHz for example.

Until that goal is reached, it is likely that some phones will be brought out for various specific markets - Europe, Asia, US.

===Ability to use multiple SIMs/networks===
* External SIM sockets are widely available in China, a dual external socket would be a very good solution.
* [http://www.fonefunshop.co.uk/dualsim/digital.htm Dual SIM card kit] - two SIMs are trimmed and combined, software supportwould be needed, and both can't be used at once...
* Some networks support multiple numbers on one SIM. Unfortunately this won't allow split networks.
* A second/dual GSM module would allow full use of both sims at all times.
* As a hack, [http://wiki.openmoko.org/wiki/Wish_List#Bluetooth_powered_Multi-SIM_support use another mobile via BT].
** As many as three SIM slots would be genuinely useful, especially for a 3G phone - some 3G data tariffs are only available on data-only SIMs. A user could quite reasonably have one SIM for data, once SIM for his personal voice calls, and a third SIM for his business number.

===PMR446/FRS Radio===
* Include a PMR/FRS Radio.
* A two-way walkie talkie lets you use the phone to communicate with friends without requiring a GSM connection (crowded networks at festivals, at locations with no GSM coverage).

===DECT/GAP===
* Include a DECT/GAP transceiver so you can use your home and/or office PSTN line
** Ability to use Alcatel phonebook stuff (like provided by the eventphone.de phone equipment) would be very nice too

==Casing==
See also: [[Alternate Neo1973 case designs]] for a list of cases being considered for design/manufacture by the community.

===[[Expansion Back]]===
* Replacement backs with additional features ranging from solar power, larger batteries, extra hardware, ...

===Space efficient Lanyard===
The hole at the bottom of the phone takes a lot of space. A Kensington Security Slot could be used instead.

=== Ruggedized version ===
We need something you can drop from 4 feet in to a puddle of dirty water on construction site. Sunlight readable display. The big ugly pseudo military version.

=== Transparent ===
Make a transparent, see-through casing. Why do we need a closed casing for open hardware and open software? Show the world it is a truly Free/Open source phone.

===[[Wishlist:Expansion Front|Expansion Front]]===
Replacement fronts with e.g. extra buttons.

==Misc==
===Galileo/GLONASS/GPS receiver===
*A multi-standard satellite positioning module would be nice eventually, it does not seem to be near-term due to chipset availability problems. Galileo is the to be launched (2011) European positioning system. GLONASS is the already existing Russian one.

===X10 RF Remote===
Many PC-based media centers are being equipped with an RF (433 MHz) / X10-based remote control. The [http://en.wikipedia.org/wiki/X10_(industry_standard) X10] protocol also facilitates home automation to control lamps, switches, etc.
The advantages of using RF for control instead of Infra-red this that it also works when furniture, walls, or doors are blocking the path between RF remote and the equipment or device. [http://www.lirc.org/ Lirc] supports X10-based RF remotes (but expects having an USB RF receiver attached to the media center).

===RFID tag/RFID Reader===
* Implementation/Cooperation with: [http://www.rfidguardian.org/ RFID-Guardian]
*An enable-able tag would be of use - for example being able to use the phone to open doors, or cars. Unfortunately, it's moderately hard to do secure programmable tags that are compatible with existing systems, for obvious reasons.

===Less weight===
* Work on the weight of the Neo1973 and following devices. At the present time the Neo1973 is just a moderate / normal business or multimedia phone. The ordinary "user" may want something lighter. Take a look at the following table, that's the Neo1973 compared with other common bussiness or multimedia phones.
{|border="1"
| Neo1973 || iPhone || Sony Ericsson P990i || Nokia E65
|-
| 184 g || 135 g || 150 g || 115 g
|-
|}

===Make it smaller===
* To stay within physical matters: Maybe the Neo1973 is also just a normal business/multimedia phone when looking at the size. It would be great the shrink it a bit. Especially the thickness of 18.5 mm could be worked on!

===Standard 3.5mm headphone jack===
The Neo1973 uses a 4-conductor 2.5mm jack for stereo headphones and a microphone. A 2.5mm jack is the most common for headsets.

There is an emerging convention used in the Nokia N800 and some other devices. A 4-conductor 3.5mm jack that can use a microphone with special headsets, but can also be used with off-the-shelf 3.5mm stereo headphones. Adapters to 2.5mm are of course available and this 3.5mm jack is much more robust.

Neglecting space limitations, multiple sockets - 2.5mm and 3.5mm would be nice. Probably not practical in a phone. Other expanded plugs might allow remote controls.

Other uses might be better met using bluetooth, or USB audio.

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

===Completely free hardware===
Consider selling one device with absolutely no non-free components in it, even if that means dropping the GSM support. I believe having one such device available would be good, because then it could be recommended by organizations like the FSF which typically never recommends anything if it has even a little non-free code in it.

=== Consider economy / inexpensive / less featured edition ===
Some people want less features, because they do not need them. Leaving out some features either lets the phone get smaller or possibly enhances battery live.

One big suggestion in this area is a b/w lower res display instead of the big color display.

=== Inductive Charger ===

It would be nice if it was possible to charge the phone without having to connect a cable. I'd like to have a simple docking station with an inductive charger like the type that's used for electric toothbrushes [http://home.howstuffworks.com/question292.htm ]. The charger itself could get its power from a standard wall-wart power supply, or it could be USB/Firewire powered.

==Related Hardware==
See [[Related Hardware]]

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

Wish List

2007-08-23T00:58:48Z

Tommy: /* Bluetooth */

This article is a place to collect various thoughts about the future of the [[OpenMoko]] software platform. Most wish list ideas have been linked from this page, but you may also wish to check all pages [http://wiki.openmoko.org/wiki/Category:Ideas that have a category of 'Ideas'].

== Development ==
=== Painless SDK installation & Setup ===
Our goal should be a completely painless setup for somebody wanting to develop using [[OpenMoko]]

* one command for installation (apt-get install openmoko)
* one command to start Xnest (openmoko-xephyr?)
* one command to start an i386 shell (openmoko-386-shell)
* one command to start an armel shell (openmoko-armel-shell)

No extra configuration required.

==== IDE Plugins ====
People like to see plugins for
* [http://anjuta.sourceforge.net Anjuta]
* [http://www.eclipse.org Eclipse]
* Game engine - Game Creation plugins
evaluate eclipse project [http://www.eclipse.org/dsdp/index.php Device Software Development Platform Project from eclipse] and subproject [http://www.eclipse.org/proposals/tml/ Tool for Mobile Linux]
* [http://www.kdevelop.org KDevelop]
* [http://developer.apple.com/tools/xcode/ XCode]
* [http://msdn.microsoft.com/vstudio/ Microsoft Visual Studio 2005]

==== UI Designer ====
Glade code generation is deprecated, so we don't want to use it. The Gtk+ powers told me that the plan is to have gtk 2.12 (out early 2007) with support for GtkBuilder, a libglade derivative which breaks a bit the XML definition in order to support all the new widgets and properties; as soon as it's in the other ui builders will add support for this format. See also [http://bugzilla.gnome.org/show_bug.cgi?id=172535 the relevant bug entry]
* Possibly a Landscape (rotated) view for the screen (480x640 *or* 640x480)?

==== Built-in Scripting Language ====
{{Main|Wishlist:BuiltInScriptingLanguage}}
There was a [http://lists.openmoko.org/pipermail/community/2007-January/001909.html fruitful discussion about a built-in scripting language on the mailing list in January.] Many people feel that it is very important for OpenMoko to choose a scripting language to ship as default in the standard OpenMoko firmware.

===Foreign Widget Set Bindings ===
==== Qt Integration ====
The Trolltech folks have a great widget library. I'd like to interface OpenMoko with Qt4, so that we can write Qt4 applications for the phone which don't look alienated.

==== Maemo Integration ====
The Maemo folks have created a successful standard for Webpad applications. I'd like to have a set of MaemoMoko and MokoMaemo wrapper classes that allow me add support for running OpenMoko applications on Maemo and vice versa. Perhaps we can get help from the Nokia OSS folks for that.

==== wxWidgets Integration ====
wxWidgets is a cross-platform application framework that's very popular (I'd say, #3 after Qt and Gtk+). On Linux, wxWidgets uses Gtk+ to implement the widgets. It shouldn't be hard to add support for the additional OpenMoko classes to wxWidgets hence supporting the native OpenMoko look and feel for wxWidgets applications.

wxWidgets team wants OpenMoko classes too and we (wxWidgets) plan to include this project as one of our ideas for [http://google-code-updates.blogspot.com/2007/02/speaking-of-summer.html GSoC 2007]

==== SDL Integration ====
SDL is ''the'' game developer library. There are tons of SDL games out there. We should add OpenMoko support into SDL.

=== Software: Language bindings ===
==== Python bindings ====
Python bindings seem to be a commonly requested feature.

[[User:Mickey]] says, "They are kind of usable on the [http://www.maemo.org Nokia 770], but it's at the lower end of being bearable. We should keep this in mind -- Gtk+ already comes with Python Bindings, so we "just" would need to wrap libmoko*. I would prefer to leave this to the community do though, since it doesn't make sense to start wrapping the API until we have a stable API -- and I can imagine it will take us a couple of months after going open until we can start with stabilizing the libmoko API."

==== C++ bindings ====
There is a whole skilled C++ community coming from the [http://qtopia.net Qtopia] and [http://opie.handhelds.org Opie] projects. If we would consider basing OpenMoko C++ Bindings on [http://www.gtkmm.org/ Gtkmm], then we could drag these guys in.

==== Other bindings ====
* Perl
* Ruby
* C#
* I think you could skip a bunch of these by binding to Dbus; most languages already have Dbus bindings

== Community Support ==

=== [http://projects.openmoko.org projects.openmoko.org] ===
Infrastructure for developers with
* One bugzilla for all projects (makes moving bugs forth and backwards between projects ''very'' easy)
* One mailing list for project

== Platform ==
=== Community Images ===
In the future there could be complete, unofficial "product images" that are created by the community, for example maybe one that incorporates only free software (in the GNU or OSI sense). Or images build with a particular niche market in mind -- a student for example.

=== Wishlist voting ===
There could be a kind of voting system like they have at one of those big computer manufacturers homepage. Then the community could vote for the ideas that are most important to them. This would especially make sense for the hardware wishlist, because the hardware is still the part which can't be done by the community that easily.

== Software: Additional features ==
===Calling===

==== Mask ID based on dialed numbers ====
It would be nice if my number only showed up when I call people in my address book and was otherwise masked. The phone I have now either always shows my number or never or can be set on a per call basis. Having it done automatically based on the number dialed would be good.

==== Use calling cards and similar routing techniques for lower-cost calling ====
Many people use calling cards, low-cost numbers and similar ways of reducing the costs of their calls. It would be nice to have a single panel that would allow you to configure the rules of dialing a number taking in to account such systems.

==== Outgoing black/white lists ====
The ability to allow or deny outoging calls to certain numbers can be useful in a number of situations (e.g. the holder of the 'phone is a child, untrusted, etc.). This could be related to entries in the contact list, for example a user is only allowed to call people who are in their contact list.

Also lists for incoming calls? Some friends always come through, unknown numbers get rejected automatically.

==== Time-based blocking/unblocking of calls ====
Allowing or disallowing outgoing calls at certain times of the day could be useful, e.g. blocking a business phone from making calls outside of business hours.

====Speaker-phone====
* A speaker-phone 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. This software has not been written.

====Advanced Airtime Tracking====
Many phone users have complicated plans, things like unlimited incoming, 100 anytime minutes, 1000 evening minutes, etc. It would be nice if a user could input the various monthly airtime chunks their plan gives them, and then the phone could track how much is left in each chunk, i.e. How much anytime minutes are left this month? Optionally, the software could warn when someone is close to the monthly limit, to help avoid bigger bills.

==== Anti-stutter software ====
Delayed Auditory Feedback (DAF) has shown to reduce stuttering in individuals by 70%. By using the microphone, it should be pretty simple to implement this on the OpenMoko. The DAF functionality should also be present during phone calls. See http://en.wikipedia.org/wiki/Delayed_auditory_feedback for more information.

====Minimize In-Call mode (check address book while in call)====
On my locked phones I always find it annoying that one can not use other features while a call is in progress. In particular, I'd like to access the address book so that we can (1) give a caller someone else's phone number (or other info) and (2) lookup a phone number when using a calling card or some other proxy.

Similar request when using the browser (lookup passwords, todo list, etc).

====Hold Music (Ringback Tone)====
On some cellphone networks you can pay to change the normal [http://en.wikipedia.org/wiki/Ringback_tone Ringback Tone] that the caller hears when ringing, to a customised sound.
This can partially be implemented on the phone.
Issues are:
*In countries where callers pay, this will make you unpopular.
*In countries where the called party pays, it will use your minutes, or cost you money.
**A list of people to activate this function for would alleviate this.
*[[GPRS]] internet connection will stall while the hold music is being played.
*Extra battery used when playing music.

Also see [[Answering Machine]].

====Play sound clips over the air====
Dialer could have a tab with big buttons which, when push, send sound clips over GSM to the person on the other end of the call. This feature is included in GizmoProject and is called sound blasts: http://support.gizmoproject.com/index.php?_a=knowledgebase&_j=questiondetails&_i=104
The buttons can have default sounds, but also have the ability to be customized.

It would also be useful to loop a pre-recorded sound in the background so you can lie about where you are, and have the ability to simulate a really bad connection.

==== Conversation Recorder ====

An option to record phone conversations. Would be helpful to have the device always recording for every call, with the sound data encoded to low quality Ogg Vorbis or SPEEX and stored in RAM. At the end of the conversation the user would have the option to save to flash or discard the conversation. This idea could also be applied to voicemail so you could save voicemails locally.

====Unlicensed Mobile Access (UMA)====
T-Mobile recently rolled out a UMA service that hands off calls between the GSM network and WiFi access points. Only a few phones support it right now, this could be a rather unique feature if OpenMoko can implement it.

==== Ignore-Call Button ====
{{Main|Wishlist:Ignore Call Button}}

Shut up a ringing phone, without accepting or rejecting the call.

Another alternative might be to use microphone to recognize when the user gives an audible "Shhh!" command. This could prove difficult to determine with the simultaneous ringing, and possible in-pocket shuffling noises.

==== Voice Mailbox ====
{{Main|Voice Mailbox}}
On-Phone voice mailbox that records calls on the phone and retrieves voice messages from your mobile service provider's voice mailbox and saves them locally.
Can act profile-dependent.

==== Hold Button ====

Similar to mute, but plays a sound file for the user on the other end while they wait. The sound file could be chosen in some setup beforehand.

==== Unanswered Call, Fast Call ====

In Greece because of the various bill programs some people call a mobile phone, rings one time and then hangup.
Then the user of the mobile phone calls the other user(using the CallerID recognition).

===Audio===

==== Ambient Noise Detection ====
{{Main|Wishlist:Ambient Noise Detection}}

Using the microphone to detect ambient noise the ringtone volume could be adjusted automatically.

Detection of ambient noise could also be used to subtract the noise from the audio signal. However this approach is best performed using two Microphones, one for the voice and the other to detect the noise.

==== Active noise control ====

Using the microphone to do [http://en.wikipedia.org/wiki/Anti-noise active noise control] on media player playback or telephone calls. This should be an independent module/library which can be used by any application which might require this feature. also provide a way to easily alter the parameters of the active noise control.

==== Hear Impaired Mode ====

Hearing impaired people need louder speaker(but with less volume than hands free) and equalized sound, based on their hearing problems(example 20dB hearing loss from 2KHz to 4KHz).
Older people 50+ years old need slower speech rate(time stretch, cut the big speech gups) and cleaner voice.

Please note also the Hearing Aid Compatibility regulations in the US. I have tried to summarize and clarify them [http://quux.wiki.zoho.com/WhereAreHACphones.html here]. I haven't yet discovered whether the FIC device is M or T rated. For many hearing impaired users, a tcoil coupling to their hearing aid (t3/T4 rating) would be preferable to manipulating sound output in other ways.

==== Mute Button ====

Button to temporarily disable microphone while talking for applications such as telephone, audio recording and (when available) movie recording.

===Media===
====Music/Video Software====
A real good programming area for competition with the iPhone, a singular video/music player would be great for multimedia. A seamless integration system, a la iTunes and iPod, would be extremely popular.

Using the Wi-Fi connectivity, a separate music program that supports wireless music sharing/ streaming (similar to what can be done when two computer running iTunes that are both on the same network) and that also supports internet radio.

==== Reading Support ====
It would be really great to be able to read :

*PDF
*Open Document files
*Text / RTF files
*MS Office files
*Aportis Doc (pdb)
*DjVu
*...

In both landscape and portrait

==== Wikipedia Mirror ====
{{Main|Wishlist:Wikipedia_Mirror}}

==== Blog ScribblePad ====

Draw an image (and maybe add some text), then post to your blog.

==== E-Book Reader ====
* Neos brilliant ultra-sharp screen makes for a very good e-book reading device. All it takes is a good e-book reader with touch-screen page turning / scrolling. FBReader could probably be adjusted easily by an experienced GTK hacker. Note that e-book reading is different to pure text/pdf displaying as it requires at least auto-bookmarking of the last read page, proper text and image scaling and text formatting.

==== Personal Wiki ====
{{Main|Wishlist:PersonalWiki}}

Display the notes database as a Wiki. Inspiration: [http://www.acrocat.com/AcroWiki/default.asp?lang=en AcroWiki].

[http://www.didiwiki.org/ Didiwiki]

==== Dictionary, thesaurus, translator and flashcards ====
Native lookup dictionary and thesaurus and foreign translation dictionaries, also with support for Asian languages. Optional custom configurable (though preconfigured) interface with on-line versions of dictionaries, thesaurus and translation services.

Support for vocabulary training with flashcard system (also usable for other content than foreign language words!)

===PIM (Personal Information Managment)===
====Context Sensitivity====
Any email or sms message or application that contains a telephone number should be click to dial, eg [http://123567890 1234567890]. Addresses link to mapping software too?

==== Address Book ====

* Option to search not just the stored list of addresses, but one or more of the online phonebooks. Probably should be modular to make adding/changing phonebook sites easy. Also allows for future integration with LDAP
servers or whatever.
* Also the possibility to search all info on the contact, like number, email, postal address and so on, in case someone asks you to identify a known number.
* Web-based map-lookup. 'How do I get there from here? (here = current GPS location)' This could also be done
by integrating with whatever on-phone GPS mapping software the Neo ends up using.
* Random text input 'notes' about a contact
* Overall, this should more resemble a Palm-pilot's address-book than your average cellphone's
* Automated Daily backup of phone book to a website archive (similar to Verizon's Back-up Assistant
*Ability to integrate address book with web-based email (such as gmail) account, for those who use web based email as their primary account
* '''[[Wishlist:Tagging|Tagging]]''' Place tags for contacts. Enhance message application to send messages to all contacts tagged with ... . Enhance other application(GPS, ...) with tags.
* Support for:
**[http://en.wikipedia.org/wiki/SyncML SyncML]
**[http://en.wikipedia.org/wiki/Ldap LDAP] address book
**[http://en.wikipedia.org/wiki/LDIF LDIF], [http://en.wikipedia.org/wiki/Xml XML] and [http://en.wikipedia.org/wiki/Comma-separated_values CSV] export and import (when possible).
*Store Bluetooth IDs of friends and notify (configurable only on this device or on both devices) when a one of these Bluetooth ID has been detected (this is more a separate application but has requirements on the address book. Should also be able to create an address book entry from a Bluetooth ID. Could be used as a nice tool to detect people who you're avoiding.

==== Database/List Display/Edit ====
{{Main|Wishlist:PilotDB}}

One of the most useful apps on my Palm Pilot for me is [http://pilot-db.sourceforge.net/ pilot-db]. It's GPL'd.

==== Joe's Goals ====

It'd be nice to have something like [http://www.joesgoals.com Joe's Goals] always available, like my phone is, even when I'm disconnected from the net.

==== Workout ====

Use your phone instead of your notebook while at the gym, and get pretty graphs to admire after you're done.

==== Shopping List ====
keep Track of Prices in different shops and the products you have/don't have. Ideally using a barcode reader and gps.
If it was made aware of recipes it could even tell you what to buy without entering a shoppinglist manually.

==== Fuel Log ====
File data about fueling your car (date/time, liters, price, mileage, ...) and display some information (costs per month, average consumption, ...).
Advanced features could include:
* Automatically storing the GPS coordinates of the place where the car has been fueled (can be deactivated)
* Sending the data to a central server which collects the information
* Let the OpenMoko receive fuel logs per SMS (e.g. if my wife with a non-openmoko mobile fuels the car and wants to file the data using her mobile phone)
* Let the OpenMoko device act as SMS gateway for non-openmoko devices to easily send the data to the central server
* Also support for air log for divers. Not that you will take this device under water but for the crew at the surface.

==== Keep in touch reminder ====
A background application which keeps track of your friends and reminds you when you have not talked, SMS, IM or mailed a person for more than # days.

==== Menstruation period timer ====
Fill in statistics and compute probabilities for menstruation, fertility, mood.
See http://www.getjar.com/products/48/MyGirls

==== Tagging ====
{{Main|Wishlist:Tagging}}
Tags can be used by various applications. Requirement is interoperability for further enhancement.
Tags should be applied to calendar events, mail/sms, calls, places(GPS) and files.

==== Context based TO-DO list ====
{{Main|Wishlist:context based to-do list}}

If I arrive home and there are "@home" things in the to-do list, the Context based to-do list reminds me of that.

==== Exchange Integration ====

Once there is good TCP/IP connectivity on this phone, integration with corporate email/calendar/to do/etc servers would be a big advantage... near-real-time automatic email downloads and automatic bi-directional syncing are productivity boosters that you have to experience to appreciate. It turns your phone from a 'nice gadget to fiddle with' to a natural-feeling extension of your day-to-day life.

* Is the time right to name names ? Add as your liking...
** Plugin/integration to & from Kontact
** Same with Evolution - Thunderbird - Seamonkey
** ?? Google Calendars ?? (this one is tough)

==== An electronic wallet ====

A database which stores securely PIN codes, login data, bank and email accounts, membership informations, and other valuable and private data. Entries can be ordered in a folder-like manner. Access to the database is given by a master password. The database as well as the master password are stored with strong encryption. For security reasons, the program asks again for entry of the master password after a certain period of inactivity. The database can be synchronized with a PC application (ideally written in Java for cross platform compatibility).

Examples: KWallet [http://docs.kde.org/stable/en/kdeutils/kwallet/index.html], Viskeeper [http://www.sfr-software.de/cms/EN/pocketpc/viskeeperpro/index.html], KeePass [http://keepass.info/]

==== Easy business card sharing for a small group (in the same room) over bluetooth or WIFI ====

Six Neo1973 owners are having a chat in a cafe. They agree to split but meet later. They want to exchange their numbers with each other before they go.... The normal way to do this is for a rather longwinded repeating of numbers to each other, or half the people manually inputting numbers before phoning/texting the other half to complete the process. All in all its a fair number of button presses to get it sorted.

Instead the NEO could have a small app where the phones link up in a small peer to peer Bluetooth network and share automatically with one person initiating a request and the other detected NEOS agreeing/acknowledging the share. The initiating NEO would then sync the mini-group automatically by interrogating each phone and then sending the table of results. The NEOs would have to be clever about checking for duplicates in the address book and offering a choice to the user if there are any conflicts.

PROS:
*genuine saving in time for social and business situations

CONS:
*I am sure there are some security hassles to be pondered....
*not going to be used every day... definitely not an immediate priority.....
*only at geek conferences will all have a neo....

===Profiles===
{{Main|Wishlist:Profiles}}

The Wishlist:Profiles page documents many possible profiles - ways to configure the phone. Including ways to respond to calls, wifi and GPS events.
And how to automatically switch between them.

===Text Messaging===
For '''Text Input related ideas''' see [[Wishlist:Text_Input]]. Bear in mind that T9 can not be included
For current development status of the messaging-app see: [[Messages]].

There are many useful options that now can be used to full capacity:
* '''Acknowledge/status SMS'''
In GSM networks so-called acknowledge-SMS are sent back to the SMS's dispatcher in order to indicate that the primal sms was received (as message delivery is only best effort and is not guaranteed). So in the SMS dialog there could be equal sized buttons with captions as 'send only', 'send and receive delivery status message' and 'send and notify (e.g. ring) when delivery succeeded'.
** '''Special handling of status-SMS'''
Related to the previous entry, these acknowledgment-sms' should be handled in a different way than normal SMS'. Most Motorola do this, while Samsung SGH series don't & clog the inbox, warn of a "new" message upon Status notification: Delivery Status Messages should be stored in a separate menu so they don't bloat the received-folder and you are able to quickly review the status of the messages you had sent.
* '''SMS at time/date''' You could be able to set up messages that are sent at a certain time/date
* '''Binary SMS''' Send binary SMS. Could be used to feign WAP pushes. [http://en.wikipedia.org/wiki/Multimedia_Messaging_Service] See:
** Resource for SMS encoding: [http://web.archive.org/web/20021016104345/www.dreamfabric.com/sms/] [http://web.archive.org/web/20060411222332/] [http://home.student.utwente.nl/s.p.ekkebus/portfolio/resource/sms_pdu.html] [http://www.ihub.com/Binary%20Messages.htm]
** [http://www.gammu.org www.gammu.org] - you can use Gammu/Gammu+ source for this software and/or understanding various SMS formats including EMS, WAP, Nokia Smart Messaging, Siemens & Alcatel encoding ([[User:Marcin|I could]] eventually help)
** Resource for SMS encoding (German): http://de.wikipedia.org/wiki/SMS-Kodierung
** The infamous pocketpc-attack: http://www.mulliner.org/pocketpc/
* '''Profile-override-SMS''' SMS that start with a certain code word override the silent profile and have the phone ring. So someone could alert you in case of some emergency.
* '''Codeword-SMS''' An expansion of the above: check for code words and allow selectable tones for matches. E.g. "Server Down!" has a loud klaxon, "Disk Warning" has a quiet chirp.
* '''(De-)Abreviation-script''' Implement a script that de-abbreviates: "hi m8 u k?-sry i 4gt 2 cal u lst nyt-y dnt we go c film 2moz" becomes "Hi mate. Are you okay? I am sorry that I forgot to call you last night. Why don't we go and see a film tomorrow?" (taken from: [http://en.wikipedia.org/wiki/SMS_language])
** Implement a script that abbreviates :-)
* '''Anti-Spam''' ...feature for SMS. May be it's possible to port some Bayesian based application like bogofilter.
* '''Rule based authorizations''' ...for received messages. For example, delete messages from one source between 9h00 and 18h00 (workday) allow them otherwise (to get alerting messages).
* '''Enable chat-like SMS-viewing''' SMS-Email-like: retain SMS app, but store 'conversations' rather than pile-up. Group/archive conversations by Caller Group (Work / Friends / Home / any user-defined Caller Group). Show appropriate icon from either Caller Group or Caller ID at the source of conversations panel
* '''Searching''' allow full-text search or string search.
* '''Massive SMS Deletion''' based on Conversation, author, before-date-xx.xx.xxxx, caller group, [[Wishlist:Tagging|tags]]...
* '''Call Back''' Prompt 'Call Back' alongside other first-line options (Delete, Save number,.. this kind of options) that appear when reading an SMS.
* '''Non-destructive deletion''', deleted messages goes to trash, and are recoverable.
* '''SMS-EMail-Gateway'''
SMS comes in, gets forward to your inbox, like any other piece of mail. Appropriate alerts and etc occur - again, just like for email. A simple SMTPD running on 127.0.0.1 that is hooked to an email-to-SMS translator that will send email addressed to 'SMS@localhost' (or whatever special address) out via SMS
* '''SMS-filter chain''', for stuff like Codeword-SMS above, Theft-mode activation, auto-response (reply with gsm-position for "Where are you?"), auto-substitution (like replace $POS with gsm-position in outgoing SMS).

=== Text input ===
{{Main|Wishlist:Text Input}}
There are many good suggestions for text input on the specific text input ideas page.

=== More/Custom Input Method Widgets ===
{{Main|Wishlist:More/Custom_Input_Method_Widgets}}
Additional and customizable Input Method Widgets (similar to virtual keyboard).
This could add soft-key functionality to games or other applications such as:
*D-Pads
*buttons
*virtual trackballs
*...
Personalized layouts could be associated with each application.

=== Games ===
{{Main|Wishlist:Games}}

=== Mesh Networking ===
{{Main|Wishlist:Mesh Networking}}

=== Printing Support ===
It would be really neat to be able to print over either bluetooth or USB. I can imagine wanting to print:

* Notes
* Maps
* Email
* Calendars
* ...

Cups contains a bluetooth printing backend, so (in theory) once you have your data in postscript format, you could hand it to cups and it'll do the rest. In practice, it depends on

# GTK+'s printing support
# Making cups run on a really small system

{{note| GTK+'s printing support seems to be very immature in 2.6 (which we need to use for some time). Gtk+ 2.10 contains much better printing support -- once we can use this, it should be more easy.}}

There's always the possibility to render postscript ourselves, but this is not a piece of cake -- in general, printing is much harder than one would imagine.

Further details:
* [http://groups.osdl.org/apps/group_public/download.php/2205/print-summit-gtk.pdf#search=%22gtk%2B%20printing%20API%22 osdl.org]
* [http://www.gnome.org/~alexl/presentations/guadec2006-printing.pdf#search=%22gtk%2B%20printing%20API%22 gnome.org]
* [http://www.j5live.com/?p=204 j5live.com]

===Misc Software===
====Clocks/timers/Activity meters====
===== Sport tracker =====
{{Main|Wishlist:Sport_tracker}}
Sport tracker can be used to measure the distance/velocity from point A to point B (or it could have several intermediate stopping points) using GPS. This would be extremely useful for running, biking, hiking, etc.

===== Standby clock =====
{{Main|Wishlist:Standby_clock}}
A quick way to see what time it is.

===== Egg Timer =====
{{Main|Wishlist:EggTimer}}

Very simple (one click) count up / count down timers are very useful.

===== Cycle Computer =====
As already mentioned by [http://wiki.openmoko.org/wiki/User_talk:Technil Technil], a cycle computer could be created using gps. The sensor at the bike's wheel could transmit data via bluetooth or some cable that would be attached to an openmoko device. In order to save power, one could switch off the gps and only use the bike's sensor.
* Just another idea that came to me: Why don't have sensor's transmit cable plug into the headphone/microphone plug? A tool reads the signals created by the induction of the passing magnet, then gives them to the cycle-computer-app :) --[[User:Minime|Minime]] 19:50, 12 April 2007 (CEST)

===== NTP Server =====

Run the [http://www.ntp.org NTP] daemon using the GPS chipset as a reference clock, so that the Neo would have a very accurate time-of-day clock and would be able to serve time to other networked devices.

I don't know what it would take to implement this. Items to consider would be the availability of a 1 pulse-per-second hardware signal, the accuracy of timestamps delivered in NMEA messags, etc. Dealing with power-management issues (such as the device going to sleep) would also be challenging.

Very simple (one click) count up / count down timers are very useful.

===== Reality check reminder =====
{{Main|Wishlist:Reality check reminder}}

A tool to [http://www.phrack.org/issues.html?issue=64&id=16 hack your brain]

====Calculators====
===== A Universal Unit Converter Tool =====

One never knows when one may have to convert acre-feet into deciliters. A unit conversion tool makes all engineers and engineer wannabes much happier. And not only the engineers.

Ideas what kind of conversions a converter tool could do:

Lenght
- Acceleration
- Angle
- Angular Velocity
- Area
- Capacitance
- Radioactivity
- Currency
- Charge
- Computer Memory
- Conductance
- Density
- Energy
- Illumination
- Power
- Force
- Flow
- Pressure
- Speed
- Temperature
- Time
- Torque
- Viscosity
- Volume
- Weight

Roman Numerals
- ASCII, Hex
- Cooking
- BMI
- Clothing Sizes

Physical and Mathematical Constants
GPS conversions

- link to or integration of a scientific calculator
- link to or integration of a simple calculator

A good basis for such a converter tool could be the Palm program "units" from
François Pessaux [http://francois.pessaux.neuf.fr/files/units1_11.tgz]. The GPL'd program comes with full documentation.

For GPS conversions see gpsbabel [http://www.gpsbabel.org]

===== An Postfix Notation (RPN) calculator =====

Many engineers, computer scientists and other groups who have grown to enjoy the simplicity and ease of an postfix notation calculator will miss them when they give up other platforms to move to OpenMoko. A RPN calculator will increase adoption by providing one of the tools that other platforms have provided for many years.

==== Web-browser Plugins ====

* While an extensive browser plugin system would be costly to the efficacy of the platform three particular browser plugins as poplularized by Mozilla firefox should be adapted to the web-browser, namely: [http://noscript.net/ noscript], [http://adblockplus.org/en/ adblock plus], [http://www.greasespot.net/ greasemonkey] and [http://www.foxmarks.com/ foxmarks].
* Careful use of these can dramatically reduce bandwidth, page space, and rendering costs even if it comes at the risk of some hard drive space in the form of block lists.
* Greasemonkey, in particular, gives users control to set up scripts for commonly traveled pages to further reduce unnecessary or unwanted content.

==== Windows CE Emulator ====

On ARM machine, Windows CE API emulator, like Wine on x86 machines.

==== PalmOS Emulator ====

The Access group is probably coming out with their Linux platform any time soon. One of the components is a PalmOS emulator which I'd like to see working on OpenMoko as well. There are literally thousands of PalmOS apps.

I'd like to see a Windows CE Emulator with active sync support.

==== TV Guide/Remote Control ====

Use your Phone to easily program your VCR using EPGs.

==== Alcohol meter ====
Give the phone some info about your body (gender, size, weigth) and when/what you drink and it will compute an approximation of the amount of alcohol in your blood. Updates automatically, could have an alarm, when you are probably sober again.
See, for example (German text) http://www.misterio-online.de/promille.htm

==== Interaction with LEGO Mindstorm ====
With the accelerometers, GPS and good CPU, the phone could be used to control/serve as input with robots built with LEGO Mindstorm, which can be accessed by USB and Bluetooth.

==== Flashlight ====
Simple finger application that makes every pixel on the entire screen white to be as bright as possible until you tap the screen again to turn it off. This way, you can use your Neo as a (short term) flashlight!

=== Accessibility ===
Accessibility features for the visually impaired.
* High Contrast Themes.
* Screen Magnifier. Features should include automatic cursor tracking when navigating menus and entereing text and provide manual controls to zoom in on other section of the screen.
* Text to speech. The software should read out menu item ,contact lists ,text messages etc. Would also be useful for operating the phone while driving.

==== VOIP ====
Ability to use the phone for VOIP over wi-fi such as Vonage. They currently have 2 different pieces of software for pc . Basically software creates a mac address which is paired with your Vonage account. Skype could also be implemented but I prefer Vonage. Only available when connected to wi-fi with a good connection. Phone treats calls the same as a cellular call, could keep a separate log of minutes, ability to record conversations, etc. Option to use VOIP if connection is available automaticly or manually. Small icon to show when call is using VOIP.
* A standard SIP client would probably fit better into the "free and open" philosophy.

==== Power Meter ====
If the power bar is clicked on it will show time left on charge and if charging it will show time until full.

=== Accelerometer wishes ===
==== Flick interface ====
Ability to "flick" the phone for page up/down by simply and rapidly tilting the phone back-and-forth for up and forth-and-back for down. The same motion can be implemented for sideways motion. This will take advantage of the 2 3d accelerators.

Sensitivity of the scrolling should be configurable and a test option provided.

==== Reading navigation of documents enhanced by accelerometers ====
If the two accelerometers in Neo1973 allows it, it will be nice if when you're reading, give a newspaper, you can move up, down, left and to the right the viewing of the document just moving the phones to the corresponding direction.

I don't know if this is possible (haven't seen the project in detail yet) but this feature could be very attractive for final users (and this is good). (sorry for my english but i'm italian)

==== Wand UI ====
In keeping with the requests to think outside of the box... the dual 3d accelerometers should enable a 'magic wand'-style UI for certain uses. Macros could be recorded and edited, or presets could be used. For example, flipping the device playfully could initiate a game mode or could signal the end of the work day.

==== Shake-to-Wake ====
Giving the phone a shake enables voice commands for a few seconds.
Usage Examples:

{Shake} "Call" ''ContactName'' ''PhoneType'' --- {Shake} "Call John Mobile" (Calls John's mobile)

{Shake} ''ApplicationName'' --- {Shake} "Reader" (Opens the e-book application)

Would require a method of inputting voice tags for applications and contacts and obviously will only work for P2 (accelerometers)
But lets get voice command functionality working before P2 (just by pressing a button on the screen instead of shaking)

I think that is possibly to replace "Shake" with double hit with finger in the side of phone. Proper algorithms(with accelerometers) should recognize any similar activities.

==== Emergency call ====
When the accelerometer detects a great acceleration (i.e. 5G) start a countdown sequence, if it is not stopped make a call to a preconfigured emergency number. If the data from the GPS is accurate give it.

A first version could use a recorded message (an audio file). In next version it could use a synthesizer, so it can give more information (add GPS information when it is ready).

==== Movement detection ====
By detecting that the owner is walking a user defined profile can be activated with a specific set of notification settings. For example you may wish to use a cheap old sounding ringtone so you don't attract attention from muggers. Or you may wish to have a louder ringtone if you carry your phone in a bag where it can't be so easily heard.

==== Others ====
Also see the pages[[Wishlist:Auto Align Map]], [[Wishlist:Determine Position]], [[Distance Measuring]], [[Wishlist:Computer Mouse]], [[Wishlist:Dynamic Screen Orientation]].

=== Connectivity ===

==== VNC client ====
A good, stylus friendly VNC client/host combo would be easy to add and terribly useful.

==== Networked X-Windows ====

Whether it's running true X-Windowing over the network, or your bog-standard VNC connection as mentioned above, the ability to have your phone's screen available on your laptop or palmtop would be most desirable.

==== NX client ====

A form of X-windows forwarding optimized for performance over slow, or high-latency links, which could prove extremely useful. Capable of streaming a good quality, full desktop session over modem speeds. The protocol and at least one implementation is gpl'd. [http://en.wikipedia.org/wiki/NX_technology wikipedia]

=== Security ===

==== My Account ====
{{Main|My Account}}
A way to securely store information about the phone, and ensure that a phone you may be considering purchasing is not stolen.

==== [http://zfoneproject.com/ Zfone] or similar ====

Something that allows the user to speak with another person securely.

==== GSM Encryption ====

This software application would allow GSM encrypted calls to be made using the GSM Data Call Channel.

[[OSvS]]

==== My Voice is my Passport ====
Use voice recognition to unlock the phone. "Hi. My name is ... My voice is my passport. Verify me."

==== Firewall ====
A network firewall

==== Anti Theft Application ====

This application would enter the phone into an [[Anti-Theft Mode]] which activates particular security features to reduce the risk of theft and also to ensure a higher probability of recovery of a stolen handset.

====RFID based personal alerts====
Assuming an RFID reader is available: You'd put an RFID tag on your keys, wallet, etc and train a program on the phone to give you a soft or hard alert when one of them leaves detection range. That way, if you're walking away from one of them, the phone could alert you.

=== Integrated Help System ===

A help system that is either on or off. It could be activated and deactivated by a [[five-second-press]] on a button, for example the AUX button. When the help system is activated, it will explain the use of any item you touch on screen (with stylus or finger). Example: if you touch the battery icon, it will explain that this shows battery level / remaining time. If you touch the date / time icon, it will explain that this icon shows date and time, and that if you press it, you can set date and time. Primarily, this help system should be able to explain all user interface elements in the main screen, but if it proves popular, it could be expanded to cover other applications as well.

===Performance optimisation===
==== Use DMA engine in CPU for blitter ====
The DMA engine in the CPU can substantially speed up moving of large areas of screen in some cases.

==== Use virtual screen to optimise scrolling ====
In some other cases, the hardware supported virtual screen may also speed it up.

==Bluetooth==

=== Voice Dialing ===

Dial by voice commands.
<br>Dial by dictating phone number. This way we can voice dial any number even if not in our contact list.

=== Music through Bluetooth Headset ===

Music can be played through a Bluetooth headset, but would stop playing when a call comes in.

=== Walkie Talkie ===

Let OpenMoko devices connect to one another via bluetooth or another connection method (GPRS for long distance but high latency, probably Wifi on P2), and hold a conversation.

Features for this applications can be:
* Push To Talk (PTT) button
* Voice Activated Control (VAC) which will set it in transmit mode when input has is detected above a certain predefined level.
* Optionally a full duplex mode
* Different channels to choose from
* Monitor different (preselected or all) channels for traffic.
* Content encryption
* Active noise control
* Allow zero config use (units can talk without any access point helping)

Local (non-GPRS) use cases include chatting while biking
or motorcycling in a group; perhaps also in a car caravan.
This application could also be used as a baby-phone to monitor your siblings.

This would be more useful if the Neo had Class 1 bluetooth, though probable Wifi on P2 will also offer more range.

=== Automatic Sync ===

Automatically synchronize with desktop computer (or with any [http://en.wikipedia.org/wiki/SyncML SyncML] server) when within range based on user profile. This may require the use of a secure data transfer.

=== GPS Assisted Bluetooth Management ===

Allow Bluetooth to automatically turn off after loosing connectivity and to automatically turn back on based upon GPS location.

A Bluetooth device is configured for automatic reacquisition based on the following profiles:
* Manual - only when Bluetooth is on
* Non-mobile - the target device is not mobile, periodically attempt reacquisition when in the general area of the device.
* Mobile - the target device is mobile, periodically attempt reacquisition when in the general area of the device.

Each target device is configured as follows:
* Automatic acquisition at last known location: enable/disable
* Automatic acquisition at these locations: list of nickname + coordinates + range

==== Non-mobile devices ====

Examples devices include: computers

The location and range of the target device is determined via training. Periodically, the current GPS coordinates and Bluetooth signal strength are logged. Additionally, connectivity loss events are logged. An algorithm uses these logs to determine the device location and range.

Connection attempts are made when in a configurable proximity to the device. The first attempt when entering the proximity and further attempts at a configurable interval.

==== Mobile devices ====

Example devices include: automobiles

Mobile devices are configured to have two types of locations:
# Last known location
# Non-mobile locations (homes)

===== Last known location =====

A car is mobile, ideally, when you leave your car, the phone should note the car's location when connectivity is lost and then attempt to reacquire the car when you return to the location of the car.

===== Non-mobile locations (homes) =====

As mobile devices may have multiple users, it is not sufficient to always use the last known location. In this case, the device may additionally have multiple homes. For example, a car might have as its homes: home garage and work parking lot.

=== Bluetooth neighbor detection and multiuser apps ===

Like the [http://en.wikipedia.org/wiki/One_laptop_per_child one laptop per child] (OLPC) interface, keep a number in the status bar that represents a count of other openmoko or compatible bluetooth devices in the area. Allow for the spontaneous initiation of a chatroom or multiplayer game or file trading with any moko in the area.

=== Bluetooth environment detection ===

Capability to detect when a predetermined bt device enters/leaves bt range and launch a system-wide event accordingly. This would feed not only the "Neighbour detection" idea described above, but also the "Profiles", "Context based TO-DO list" and "Location-based reminders" ideas. Reminders could be set to trigger in the presence of a specific person X (with BT device Y). Profiles can take into account which devices are present around the phone (car kit, for ex.). To-do list could also change according to present devices.

=== Remote control ===

==== Wireless presenter ====
Use the phone to run your OpenOffice.org Impress presentation remotely using Bluetooth. Cool features:
* Display the text notes for the presenter on the phone's display and update it whenever the slide is changing.
** OO.org has implemented support for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 dual monitor]/[http://www.openoffice.org/issues/show_bug.cgi?id=18486 presenter mode] that can be used as a starting point
* A small timer showing the time passed (and perhaps remaining if the presentation app supports such a feature).
* If you want to be super-cool, you give a preview of the notes of the next slide in the show.
* At the end of a presentation, a "navigator" could allow to easily jump to any slide in the presentation by clicking on it on the phone.
** When you right-click in a running OO.org Impress presentation, you can choose "got o slide..." and select any slide to jump to.

==== Initiated from another device ====
Remote control over Bluetooth from other devices to control media player (play, pause, next, previous, volume control), camera (capture image), etc.
==== Directed at another device ====
Remote control over Bluetooth to other devices to control media player, lights in your house, etc.

Z-wave uses web-browser control of devices that is said to be compatible with mobile phone browsers so should work with openmoko browser. [http://www.z-wave.com www.z-wave.com]

=== Bluetooth Car Connection ===

Have a deeper connection to the car than just handsfree speakerphone. For instance a transceiver with challenge/response systems to open, possibly even start the car. Possibly go as far as OBD connection to monitor car status on screen/log for later.

==== Dude, Where's My Car? ====

When in range of the car navigation system, remember the position (perhaps check with the car GPS). When not in range, assumme that you are not in the car, and offer the opportunity to navigate to the car's last known position. That way, you can find your car e.g. on a large parking lot.

=== [[Bluetooth powered Multi-SIM support]] ===

As the Neo1971 does not come with dual-SIM support this could be solved by joining your old bluetooth-enabled mobile to your OpenMoko-phone.

Let SIM card A be in your OpenMoko-phone and SIM card B in your old mobile:
* Incoming call on SIM card B - the OpenMoko-phone acts as a headset(Bluetooth Headset profile)
* Calling out via SIM card B - the OpenMoko-phone acts again as a headset
* Same for Short Messages/MMS/Internet
This way you'd have your old phone switched silent and connected to your OpenMoko-phone that handles all the calls and one can select which SIM card to use.
Advantage: No 'switching' between cards
Disadvantage: Second mobile needs to be in range(e.g. handbag) and charged every once in a while.

===Internet Gateway===

If the device could function as a Bluetooth router/gateway to the internet via the GPRS/data connector, then you could use it to get network connectivity from your laptop and other devices while on the road. Many smartphones can be configured as modems via Bluetooth for use as Dial-Up Networking connectors, and that should be the minimum target. Ideally, if the WiFi functionality was used so the OpenMoko could be an 802.11 router or peer to peer gateway for a laptop, this would be even better. The full bandwidth of GPRS or whatever network is available would then be available.

=== Social Networking ===

Anybody running the social networking app will be broadcasting a profile, and when certain keywords are matched with other users who are also running the application, an alert is sounded. Each mokoid can be added as a hexstring to a profile page, and xml filters can be developed for each social service to convert various keywords and interests to moko-friendly format.

=== Give userspace api control over bluetooth signal strength ===

I have tried bluetooth handsfree sets with other phones and don't get perfect reception due to low signal strength. I suppose the reason the signal is so weak is because the manufacturer wants the battery to last long on its latest charge. Can you please make the strength setting configurable by the user of the phone through an api and perhaps even through the phones gui? I would gladly waste some battery time in exchange for stronger bluetooth signal strength.

== Other ==

=== Vibrate Pattern Recorder ===

An application that would allow the user to define their own vibration patterns, and possibly link them to audio files. Recording would be done in real time initiated with a "Record" button, optionally playing the associated sound file in sync with recording). While recording, the user would press and hold a button to define the timing and duration of vibration. The user would press "Stop" when finished. Vibration patterns would have the option of being looped(would terminate at some global ringtone length maximum).

One simple suggested vibration file format would be a sort of run-length encoding: First byte defines the length of a "time-slice" in milliseconds, which would determine the overall tempo(actually the inverse of tempo). The next byte would define the number of time-slices to leave the vibration on, and then another byte for how long to pause after. Continue alternating these on/off bytes until the entire pattern is defined.

- or just use MIDI, using a separate channel for the vibrator.

An implementation of RTTL could also be used to define vibration patterns.

=== PC Input Device ===

Provide a method to use the touchscreen as input device for a nearby desktop machine. Could connect over USB or bluetooth.

=== Advanced Notification And Ringtone Manager ===
{{Main|Wishlist-ANARM}}

ANARM would be an application for handling all event-based audible notifications from an OpenMoko device.

=== Location based reminders ===
{{Main|Wishlist:Location_based_reminders}}
Location based reminders can be used to notify users of various events or reminders that are location based.

=== Synergy Client ===
A synergy client would enable the user to place the device next to a desktop PC and share the desktop`s mouse, keyboard and clipboard over a TCP/IP network. [http://synergy2.sourceforge.net/ Synergy]

== GPS Software ==
*Providing GPS Support also for outdoor users in addition to ordinary street navigation features
** Overlay of satellite images with existing streetmaps
** Incorporating SRTM digital elevation model: for example using the VRML/X3D as data format (see http://www.ai.sri.com/geovrml/) which is interesting for e.g. mountaineering: using a 3d browser rendering VRML/X3D Model, displaying the current position and track (possibly also other gps-tracks of the different routes to a summit downloaded before could be mapped onto the 3d model), (what about 3d hardware support? there is nothing written in the hardware specs about graphics: thinking of OpenGL for embedded systems (see http://www.khronos.org/opengles/)
** Using sth like a tracking mode to allow certain people to determine the current position and track (for rescue missions - like they have for example at http://www.steiger-stiftung.de (a German beneficence for rescue issues) There you can register your mobile phone so the rescue service is able to track you immediately if necessary. The interesting thing: It seams like some mobile phones with GPS have special support for this issue. If your phone is registered, the rescue service is able to get your GPS coordinates directly from the phone without any user assistance. Openmoko should also support this! )
* Implementation of 3dTracking's (http://free.3dtracking.net/) tracking software or equivalent.

<br>[[Community Based Traffic Information]]

== Hardware ==
{{Main|Wish List - Hardware}}

It could be use for beepway Online service too
[http://www.beepway.com]

=== Tactile feedback via buzzer ===
Assuming the hardware has a vibrator/buzzer for silent calls, use a lightly pulsed version of that to simulate tactile feedback when dragging finger across buttons on-screen. Implemented properly, it would almost feel as if the buttons were real.

=== Detachable keyboard ===
Hardware keyboard that can be attached with magnets to a future version of the Neo.

=== IR port ===
Remote control applications

[[Category:User]]
[[Category:Ideas| ]]

Wishlist/Accessories

2007-08-06T23:45:28Z

Tommy: /* Wishlist */ Make the stylus laser-pen recharge its batteries from phone while "docked"

Wishlist/Accessories

2007-08-06T23:25:06Z

Tommy: /* Wishlist */ USB keyboard ability.

User:Tommy

2007-08-06T23:06:08Z

Tommy:

andersonthomas at gmail dot com

FAQ

2007-08-06T21:57:00Z

Tommy: /* Q:Can I has some money for a Neo1973? */ Indentation corrected. Semantics of joke left intact.

Questions and Answers that don't seem to fit elsewhere

==Introduction==

=== Q: What is OpenMoko and Neo1973? ===
A: [[OpenMoko]] is a software platform, an attempt to create the world's first completely open mobile phone software stack. The [[FIC]] [[Neo1973]] is the first fully supported OpenMoko phone.

=== Q: I'm a ____ expert, can I join/help OpenMoko? ===

We would love to hear from you.

If you are interested in joining OpenMoko, please visit http://www.openmoko.com/contact-index.html and send us an e-mail. Or simply post a message to our community list if you just want to help.

=== Q: When can I buy a [[Neo1973]]? ===

A: Now - from https://direct.openmoko.com/. But please see "What will it do?" below first.

=== Q: How much? ===

A: Neo1973 GTA01B_v04: $300 for Neo Base, $450 for Neo Advanced. Available now. See [[Neo1973]] for what is included.

A: Neo1973 GTA02: $450 for Neo Base, $600 for Neo Advanced. Planned to be available Fall 2007. See [[Neo1973]] for list of hardware.

=== Q: What will it do? ===

A: For long answer see [[Developer preview]]

A: The Phase 1 phone is aimed at developers only. It is not suitable for end users, it will have basic functionality as a touchscreen phone. Little else will work, software development will continue till mass market release.

Those interested should:

* Know that there will be a device with faster cpu, gsm system etc. 4-5 months later (GTA02)
* Have fun hacking devices.
* Be able to find their way through prototype software and hardware without much documentation.
* Share the dream of a device powered by free software.
* Not expect a consumer-level device.
* Come up with new ideas for exploring the age of mobile computing.
* Have $300.

Ideally they also:

* Can spot bugs and submit patches.
* Love to cooperate with a community improving the software.

=== Q: Do I need Neo Advanced? ===

With Neo Base you can do:
* Kernel development.
* Application developemnt.
* Updating u-boot (equivalent to PC BIOS) using a tested image.
* Replace a non-booting kernel and/or rootfs using [[Dfu-util]].

With Neo Advanced you can additionally do:
* U-boot development.
* Use the kernel console.
* Unbrick your device if you flash a wrong or non-working u-boot image.

=== Q: I have a shipping related question ===

See [[SH1_FAQ|Shipment 1 FAQ]].

=== Q: What will the [[Neo1973]] look like? ===

See the proposed [[Artwork|artwork]].

==Software==

=== Q: Can the software do/connect to/... ===
A: At the moment, the answer is in almost all cases no. The phone is at the moment a small linux box with a touchscreen, a working dialer and some prototype apps.
Most do not function in any way that would be suitable for users.
If you want to add a feature or application request, then look over the existing applications and either add one, or add a feature request to the applications page.

===What software is on the phone?===
At the moment, almost no 'end-user' applications are present and working in a usable state.
It is possible to make and receive calls in some software revisions, this frequently breaks though.

====What software can be installed on the phone?====

=== Q: Is there description and list of OpenMoko software? ===

A: See [[OpenMoko]] and [[OpenMokoFramework]]

=== Q: Is it completely free software/open source? ===

A: User space [[Gpsd]] will use binary plugin for [[:Category:Neo1973 Hardware#AGPS|Hammerhead AGPS]] and [[:Category:Neo1973 Hardware#GSM.2FGPRS|GSM modem]] is separate subsystem connected to S3C2410 UART1. Otherwise it is completely free software. See [[MokoMakefile]] and [[Development resources]].

=== Q: How do I install and manage software on OpenMoko? ===

A: ipkg: http://handhelds.org/moin/moin.cgi/Ipkg

=== Q: How can I compile programs for the Neo1973? ===

A: See [[Toolchain]].

=== Q: Is there an emulator available for OpenMoko? ===

For a lot of testing and development work, you don't actually need emulation as you can run OpenMoko on a normal PC too. The emulators also aren't 100% accurate. That being said, there are several emulation options as described in the following.

====QEMU====
QEMU can now emulate the Neo1973 device. The [[MokoMakefile]] has support for automatically building, flashing, and running [[OpenMoko under QEMU|the Neo1973 emulator]].

“make qemu” will build qemu-neo1973, download the latest official openmoko images, flash the images into the virtual NAND flash, and run the emulator.

====Xoo====
Another is [http://projects.o-hand.com/xoo Xoo]. Koen says: "Xoo should be enough for most apps people will develop, since most don't need access to the gsm uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".

Update: Stefan Schmidt has resized the [[Neo1973]] Mock-up and written a small description for xoo. In his words:

It's not really useable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.

http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2

Start with 'xoo --device /path/to/neo1973.xml'

Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].

====Xephyr====
Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):
Xephyr -screen 480x640 -nolisten tcp -ac :1 &
export DISPLAY=:1
export LD_LIBRARY_PATH=/usr/local/lib
matchbox-window-manager -display $DISPLAY -use_titlebar no \
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \
-use_cursor yes &
matchbox-panel --geometry=480x44 --end-applets=clock &
openmoko-footer &
openmoko-taskmanager &

=== Q: Where can I find some type of tutorial for a 'Hello, world' on OpenMoko? ===

A: This should get you started:
http://www.gtk.org/tutorial/

=== Q: Can PalmOS apps applications be ported to run on OpenMoko? ===

A: Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux
is decidedly non-trivial.

PalmOS apps are in general very hard to simply 'port'. Particularly well-designed programs may make it possible.

The ACCESS Linux Platform will include Garnet on Host (GHost), a PalmOS emulator that will support M6800 (68k) and ARM PalmOS applications. This part (GarnetVM and the .prc loader) will however be closed-source and likely under a restrictive license (fact confirmed by ACCESS Co. employees), making it rather unusable. In addition GarnetVM depends on Hiker and other packages.

It is possible that POSE, an emulator that simulates a Palm device on a Linux host could be used to allow 68k based applications to run. This emulator has been around a long time; one expects that it will also run on OpenMoko, but this has to be considered a short-term bandaid rather than a long-term solution.

The soon-to-be-released [http://www.palm.com/foleo/ Palm Foleo], which runs a Linux port developed by Palm Inc. independently of ALP, contains a PalmOS compatibility environment that runs PalmOS apps, supposedly all of them and supposedly seamlessly. Little is known about how it works but if it's not too kludgy it should run unmodified on any ARM linux. It is not known what license it will be distributed under.

Hopefully emulation will be necessary only for M68000 code (pre-PalmOS 5) while native ARM programs can run natively under Linux, provided a proper set of PalmOS libraries and a .prc executable loader.

=== Q: Does it have Java? ===
A: It will have eventually, if you help us to get it working. Some good places to keep track of would be [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] and [https://phoneme.dev.java.net/ PhoneME].

=== Q: What are the relevant X11 details? ===

A: See [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].

=== Q: Does OpenMoko run on any other hardware? ===

You can run it on your [[How_to_run_OpenMoko_Apps_on_PC|PC]]. There is work going on with [http://www.datenfreihafen.org/~stefan/weblog//archives/2007/02/#e2007-02-18T15_27_07.txt OpenEZX and HTC]. It's running on [http://dominion.kabel.utwente.nl/koen/cms/openmoko-running-on-an-ipaq iPaq hx4700], on a [http://hackndev.com/node/701 Palm TX] and on [http://blog.mikeasoft.com/2007/07/01/openmoko-on-a-treo-650/ PalmOne's Treo 650].

=== Q: What are the requirements to the hardware to run OpenMoko? (Would it run on the IXI ogo?) ===

=== Q: Why do you not build on top of the Maemo platform instead? ===

While I can't speak for the OpenMoko team, it's worth noting that maemo is fixed resolution only. That will, I've heard, change in the future, but it hasn't yet. Maemo's current layout is also optimized for wide screens, not tall narrow ones. Most third party maemo applications that are out there will need to be modified to work at different sizes. Finally, a number of the software components of the Nokia 770 and N800 are not open source. --gopi

To add up on that, according to Nokia, Maemo is designed to bring the "Desktop" experience to an Internet Tablet. A lot of Desktop paradigms just won't work on a phone. However, we really share a lot of the base-technology (gtk, dbus, eds, gconf, to name a few) with Maemo, so we are definitely not a reinvent-the-wheel team.

=== Q: Will it be possible to use popular VoIP applications such as Skype on the OpenMoko platform? ===

A: Perhaps. Hardware issues mean that it won't work well on the Neo1973. (the typical latency of GPRS is far too high). Also, Skype is a closed source application, which does not provide binaries that would be suitable to run on OpenMoko. Skype's vendor could of course choose to provide binaries for OpenMoko phones. However, many telephone providers' terms of service agreements preclude running VoIP over their baseline GSM service.

=== Q: Same question for Instant Messaging applications such as MSN Messenger? ===

A: Very probably. MSN is closed source and will only run where Microsoft wants you to run it. But there are many Open Source IM clients, many of which have a plugin architecture and so support the use of more than one IM protocol, even simultaneously. One example is [http://www.pidgin.im Pidgin, formerly called GAIM]. GPRS does induce a certain amount of latency but that should not be a problem for simple, text-oriented chat between parties. And the GTA02's WiFi will make it even better.

==Neo1973 Hardware==

=== Q: Is there description of [[:Category:Neo1973 Hardware | Neo1973 Hardware]] ? ===

A: See [[:Category:Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]]

=== Q: What are the dimensions? ===

A: 120.7 x 62 x 18.5 mm, It would fit entirely in a coke can. (4.75 * 2.4 * 0.72 ")

=== Q: How heavy is it? ===

A: 185g, (6.5 ounces).

=== Q: Does it have a camera? ===

A: No, see [[:Category:Neo1973 Hardware | Neo1973]] for details on what it does include (and [[Wish List - Hardware]] for what some want in the future.) See also [[FAQ#USB]].

=== Q: Does it have Wifi? ===

A: The currently available [[Neo1973]] does not have WiFi. There was no suitable Wifi device available when it was designed. The next version will have WiFi. See also [[FAQ#USB]].

=== Q: Does it have bluetooth? ===

A: Yes! Bluetooth 2.0.

=== Q: Does it come with a stylus? ===

A: Yes, but there's no holder for it on the phone.

=== Q: Where are the buttons? ===

The power button is a small circular button, just next to the USB connector. [[Neo1973 Power Button]]
The Auxilliary button is a rectangular button on the top left of the edge of the phone. (on black phones it looks just like an IRDA port). [[Neo1973 AUX Button]]

=== Q: How do I input text? ===

A: Use provided keyboard app.

A: Use Bluetooth keyboard.

A: For more methods and ideas see [[Wishlist:Text_Input]].

=== Q: Can I record calls and/or play audio files in calls? ===

A: Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing an [[Answering Machine]] is possible. Also using text->speech should be possible or modifying outgoing voice. Currently there is no software bundled in phone to do this.
There are only 2 A/D inputs and three D/A outputs (one dedicated to the earpiece). This means that stereo audio playback cannot happen at the same time as the [[Answering Machine]] functionality, amongst other things. See the audio page. (which?){{fixme}}

=== Q: What is the battery life? ===

A: There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].

=== USB ===

==== Q: What can I do with the USB port on the Neo1973? ====
A: Charge the phone, communicate with it over USB-serial, or USB-networking.

A: Plug external devices, such as wifi, cameras, or mass-storage devices in. The "Mass Market" version of the phone will have wifi integrated.

==== Q: What can't I do with the USB? ====

The USB on the neo has no power output. This means that you cannot use USB bus powered devices without some sort of powered hub or cable.
This is due to the fact that adding a 5V power supply into the device would have added complexity, volume and cost.

Many powered USB devices don't work without at least a nominal amount of 5v power from the USB bus. A few powered USB hubs will work without 5v power from the host, but most powered ones need to have simple electrical modifications done to work.

==== Q: Why is only USB 1.1 provided? ====

A: The processor has USB 1.1 built in. One with USB2 built in would have been more expensive.

==== Q: Can the Neo charge and use devices on a USB hub at the same time? ====

A:
*When the Neo is connected to a device port on a USB hub, it will start charging. If the hub is a powered hub, then it will charge fast (3h), otherwise around 12h.

*If you plug the Neo into the host port of a USB hub you can use devices on that hub but the Neo will not charge. (Some/many USB hubs will not accept an unpowered host as valid, hence the need for the below cable.)
*This is because the host socket on USB hubs is not powered.

FIC product development is looking into providing something that
conveniently solves this problem.

The USB port on the Neo is not a properly compliant USB host port, all USB host ports must provide 5V - though powered devices or hubs may not draw any current from this, they may refuse to work. (The Belkin Tetrahub is an example of a hub that will not work.)

One solution is a three headed cable.

One end plugs into the Neo. One end plugs into a device port of a powered hub, or the Neo charger. One end plugs into the host port of a hub.

The Charger/USB device plug only has +5V and 0V connected in the simple cable, which are connected to the other ends.

For a more complex cable, when the host socket is not plugged in, the cable acts as a simple USB cable.

==== Q: What are the details of the USB port on the [[Neo1973]]? How does it compare to USB On-The-Go? ====

A: The [[Neo1973]] will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just
a AB socket, but also electrical and software components which cannot be provide by the S3C2410.

You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).

=== Q: Are there any LEDs on the Neo 1973? ===

A: The [[Neo1973]] P1/P2 will have no LEDs besides the screen backlight.

=== Q: Will a JTAG port be made available? ===

A: The "Hacker's Lunchbox" in Advanced version will make this kind of stuff easy.

There are [[Neo1973_Hardware#Changes_from_GTA01Bv3|exposed I2C, SPI and debug board connectors]] inside case in all versions and [[Debug Board|Debug Board v2]] (JTAG and serial console) in Advanced version. [[Connecting Neo1973 with Debug Board v2]] explains how to connect it to the phone.

=== Q: What can we expect in future versions? ===

A: A faster CPU, faster GSM (EDGE?) perhaps even powered USB port, USB2, wifi, and camera. No details have been released yet. More details of hardware upgrades should be available sometime in May. There will also be 5 more OpenMoko devices - some not phones in the traditional sense - announced by FIC in September.

==Networking/Connectivity==

=== Q: What kind of connectivity? ===

A: Quad-band GSM, GPRS Class12/CS4 2.5G (Not EDGE), Bluetooth 2.0 EDR, USB in all versions. WiFi: Atheros AR6K in [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]. (No 3G in year 2007 models)

=== Q: Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ===

A: Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].

=== Q: What providers provide the GSM required for Neo1973? ===

A: See [[Neo1973 compatible cellphone providers]]

=== Q: Will OpenMoko "Just Work" with Mac OS X? ===

A: There has been some discussion of this on the mailing list. There is motivation, and there are interested developers.
Not being a Mac OS X user, I don't know enough
to summarize the discussion to answer this question. Can someone please fill in?

A: For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the OpenMoko.

A: It is expected that (Bluetooth/UB) SyncML based interoperation for
contacts and events can easily be achieved by a patch
to the Apple iSync configuration tables.

A: There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of
PPC/x86/ARM universal binaries) on OpenMoko devices: mySTEP.

==Misc==

=== Q: On the lists on lists.openmoko.org, should replies be added above or below the original text? ===

A: Please reply UNDER post.

=== Q: How can I find out if a question or topic has already been discussed on the mailing lists? ===

A: By searching the mailing list archives. For example, using Google searches:

site:openmoko.org text

For example, to search for accelerometer:

site:openmoko.org accelerometer

If you only want to read the "official" mails from FIC people or from OpenMoko people:

site:openmoko.org text "at fic.com.tw"
site:openmoko.org text "at openmoko.org"

For example to search for "release date" from FIC people:

site:openmoko.org "release date" "at fic.com.tw"

Alternatively you can use the [http://www.google.com/coop/cse?cx=017507431580478583395%3Astsl7lhxzbc custom OpenMoko search engine] which has been created using [http://www.google.com/coop/ Google Co-op].

=== Q: Can I has some money for a Neo1973? ===

A: No.

{{Languages|FAQ}}

[[Category:Information]]

FAQ

2007-08-06T21:55:56Z

Tommy: /* Q:Can I has some money for a Neo1973 */ language.

Questions and Answers that don't seem to fit elsewhere

==Introduction==

=== Q: What is OpenMoko and Neo1973? ===
A: [[OpenMoko]] is a software platform, an attempt to create the world's first completely open mobile phone software stack. The [[FIC]] [[Neo1973]] is the first fully supported OpenMoko phone.

=== Q: I'm a ____ expert, can I join/help OpenMoko? ===

We would love to hear from you.

If you are interested in joining OpenMoko, please visit http://www.openmoko.com/contact-index.html and send us an e-mail. Or simply post a message to our community list if you just want to help.

=== Q: When can I buy a [[Neo1973]]? ===

A: Now - from https://direct.openmoko.com/. But please see "What will it do?" below first.

=== Q: How much? ===

A: Neo1973 GTA01B_v04: $300 for Neo Base, $450 for Neo Advanced. Available now. See [[Neo1973]] for what is included.

A: Neo1973 GTA02: $450 for Neo Base, $600 for Neo Advanced. Planned to be available Fall 2007. See [[Neo1973]] for list of hardware.

=== Q: What will it do? ===

A: For long answer see [[Developer preview]]

A: The Phase 1 phone is aimed at developers only. It is not suitable for end users, it will have basic functionality as a touchscreen phone. Little else will work, software development will continue till mass market release.

Those interested should:

* Know that there will be a device with faster cpu, gsm system etc. 4-5 months later (GTA02)
* Have fun hacking devices.
* Be able to find their way through prototype software and hardware without much documentation.
* Share the dream of a device powered by free software.
* Not expect a consumer-level device.
* Come up with new ideas for exploring the age of mobile computing.
* Have $300.

Ideally they also:

* Can spot bugs and submit patches.
* Love to cooperate with a community improving the software.

=== Q: Do I need Neo Advanced? ===

With Neo Base you can do:
* Kernel development.
* Application developemnt.
* Updating u-boot (equivalent to PC BIOS) using a tested image.
* Replace a non-booting kernel and/or rootfs using [[Dfu-util]].

With Neo Advanced you can additionally do:
* U-boot development.
* Use the kernel console.
* Unbrick your device if you flash a wrong or non-working u-boot image.

=== Q: I have a shipping related question ===

See [[SH1_FAQ|Shipment 1 FAQ]].

=== Q: What will the [[Neo1973]] look like? ===

See the proposed [[Artwork|artwork]].

==Software==

=== Q: Can the software do/connect to/... ===
A: At the moment, the answer is in almost all cases no. The phone is at the moment a small linux box with a touchscreen, a working dialer and some prototype apps.
Most do not function in any way that would be suitable for users.
If you want to add a feature or application request, then look over the existing applications and either add one, or add a feature request to the applications page.

===What software is on the phone?===
At the moment, almost no 'end-user' applications are present and working in a usable state.
It is possible to make and receive calls in some software revisions, this frequently breaks though.

====What software can be installed on the phone?====

=== Q: Is there description and list of OpenMoko software? ===

A: See [[OpenMoko]] and [[OpenMokoFramework]]

=== Q: Is it completely free software/open source? ===

A: User space [[Gpsd]] will use binary plugin for [[:Category:Neo1973 Hardware#AGPS|Hammerhead AGPS]] and [[:Category:Neo1973 Hardware#GSM.2FGPRS|GSM modem]] is separate subsystem connected to S3C2410 UART1. Otherwise it is completely free software. See [[MokoMakefile]] and [[Development resources]].

=== Q: How do I install and manage software on OpenMoko? ===

A: ipkg: http://handhelds.org/moin/moin.cgi/Ipkg

=== Q: How can I compile programs for the Neo1973? ===

A: See [[Toolchain]].

=== Q: Is there an emulator available for OpenMoko? ===

For a lot of testing and development work, you don't actually need emulation as you can run OpenMoko on a normal PC too. The emulators also aren't 100% accurate. That being said, there are several emulation options as described in the following.

====QEMU====
QEMU can now emulate the Neo1973 device. The [[MokoMakefile]] has support for automatically building, flashing, and running [[OpenMoko under QEMU|the Neo1973 emulator]].

“make qemu” will build qemu-neo1973, download the latest official openmoko images, flash the images into the virtual NAND flash, and run the emulator.

====Xoo====
Another is [http://projects.o-hand.com/xoo Xoo]. Koen says: "Xoo should be enough for most apps people will develop, since most don't need access to the gsm uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".

Update: Stefan Schmidt has resized the [[Neo1973]] Mock-up and written a small description for xoo. In his words:

It's not really useable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.

http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2

Start with 'xoo --device /path/to/neo1973.xml'

Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].

====Xephyr====
Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):
Xephyr -screen 480x640 -nolisten tcp -ac :1 &
export DISPLAY=:1
export LD_LIBRARY_PATH=/usr/local/lib
matchbox-window-manager -display $DISPLAY -use_titlebar no \
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \
-use_cursor yes &
matchbox-panel --geometry=480x44 --end-applets=clock &
openmoko-footer &
openmoko-taskmanager &

=== Q: Where can I find some type of tutorial for a 'Hello, world' on OpenMoko? ===

A: This should get you started:
http://www.gtk.org/tutorial/

=== Q: Can PalmOS apps applications be ported to run on OpenMoko? ===

A: Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux
is decidedly non-trivial.

PalmOS apps are in general very hard to simply 'port'. Particularly well-designed programs may make it possible.

The ACCESS Linux Platform will include Garnet on Host (GHost), a PalmOS emulator that will support M6800 (68k) and ARM PalmOS applications. This part (GarnetVM and the .prc loader) will however be closed-source and likely under a restrictive license (fact confirmed by ACCESS Co. employees), making it rather unusable. In addition GarnetVM depends on Hiker and other packages.

It is possible that POSE, an emulator that simulates a Palm device on a Linux host could be used to allow 68k based applications to run. This emulator has been around a long time; one expects that it will also run on OpenMoko, but this has to be considered a short-term bandaid rather than a long-term solution.

The soon-to-be-released [http://www.palm.com/foleo/ Palm Foleo], which runs a Linux port developed by Palm Inc. independently of ALP, contains a PalmOS compatibility environment that runs PalmOS apps, supposedly all of them and supposedly seamlessly. Little is known about how it works but if it's not too kludgy it should run unmodified on any ARM linux. It is not known what license it will be distributed under.

Hopefully emulation will be necessary only for M68000 code (pre-PalmOS 5) while native ARM programs can run natively under Linux, provided a proper set of PalmOS libraries and a .prc executable loader.

=== Q: Does it have Java? ===
A: It will have eventually, if you help us to get it working. Some good places to keep track of would be [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] and [https://phoneme.dev.java.net/ PhoneME].

=== Q: What are the relevant X11 details? ===

A: See [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].

=== Q: Does OpenMoko run on any other hardware? ===

You can run it on your [[How_to_run_OpenMoko_Apps_on_PC|PC]]. There is work going on with [http://www.datenfreihafen.org/~stefan/weblog//archives/2007/02/#e2007-02-18T15_27_07.txt OpenEZX and HTC]. It's running on [http://dominion.kabel.utwente.nl/koen/cms/openmoko-running-on-an-ipaq iPaq hx4700], on a [http://hackndev.com/node/701 Palm TX] and on [http://blog.mikeasoft.com/2007/07/01/openmoko-on-a-treo-650/ PalmOne's Treo 650].

=== Q: What are the requirements to the hardware to run OpenMoko? (Would it run on the IXI ogo?) ===

=== Q: Why do you not build on top of the Maemo platform instead? ===

While I can't speak for the OpenMoko team, it's worth noting that maemo is fixed resolution only. That will, I've heard, change in the future, but it hasn't yet. Maemo's current layout is also optimized for wide screens, not tall narrow ones. Most third party maemo applications that are out there will need to be modified to work at different sizes. Finally, a number of the software components of the Nokia 770 and N800 are not open source. --gopi

To add up on that, according to Nokia, Maemo is designed to bring the "Desktop" experience to an Internet Tablet. A lot of Desktop paradigms just won't work on a phone. However, we really share a lot of the base-technology (gtk, dbus, eds, gconf, to name a few) with Maemo, so we are definitely not a reinvent-the-wheel team.

=== Q: Will it be possible to use popular VoIP applications such as Skype on the OpenMoko platform? ===

A: Perhaps. Hardware issues mean that it won't work well on the Neo1973. (the typical latency of GPRS is far too high). Also, Skype is a closed source application, which does not provide binaries that would be suitable to run on OpenMoko. Skype's vendor could of course choose to provide binaries for OpenMoko phones. However, many telephone providers' terms of service agreements preclude running VoIP over their baseline GSM service.

=== Q: Same question for Instant Messaging applications such as MSN Messenger? ===

A: Very probably. MSN is closed source and will only run where Microsoft wants you to run it. But there are many Open Source IM clients, many of which have a plugin architecture and so support the use of more than one IM protocol, even simultaneously. One example is [http://www.pidgin.im Pidgin, formerly called GAIM]. GPRS does induce a certain amount of latency but that should not be a problem for simple, text-oriented chat between parties. And the GTA02's WiFi will make it even better.

==Neo1973 Hardware==

=== Q: Is there description of [[:Category:Neo1973 Hardware | Neo1973 Hardware]] ? ===

A: See [[:Category:Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]]

=== Q: What are the dimensions? ===

A: 120.7 x 62 x 18.5 mm, It would fit entirely in a coke can. (4.75 * 2.4 * 0.72 ")

=== Q: How heavy is it? ===

A: 185g, (6.5 ounces).

=== Q: Does it have a camera? ===

A: No, see [[:Category:Neo1973 Hardware | Neo1973]] for details on what it does include (and [[Wish List - Hardware]] for what some want in the future.) See also [[FAQ#USB]].

=== Q: Does it have Wifi? ===

A: The currently available [[Neo1973]] does not have WiFi. There was no suitable Wifi device available when it was designed. The next version will have WiFi. See also [[FAQ#USB]].

=== Q: Does it have bluetooth? ===

A: Yes! Bluetooth 2.0.

=== Q: Does it come with a stylus? ===

A: Yes, but there's no holder for it on the phone.

=== Q: Where are the buttons? ===

The power button is a small circular button, just next to the USB connector. [[Neo1973 Power Button]]
The Auxilliary button is a rectangular button on the top left of the edge of the phone. (on black phones it looks just like an IRDA port). [[Neo1973 AUX Button]]

=== Q: How do I input text? ===

A: Use provided keyboard app.

A: Use Bluetooth keyboard.

A: For more methods and ideas see [[Wishlist:Text_Input]].

=== Q: Can I record calls and/or play audio files in calls? ===

A: Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing an [[Answering Machine]] is possible. Also using text->speech should be possible or modifying outgoing voice. Currently there is no software bundled in phone to do this.
There are only 2 A/D inputs and three D/A outputs (one dedicated to the earpiece). This means that stereo audio playback cannot happen at the same time as the [[Answering Machine]] functionality, amongst other things. See the audio page. (which?){{fixme}}

=== Q: What is the battery life? ===

A: There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].

=== USB ===

==== Q: What can I do with the USB port on the Neo1973? ====
A: Charge the phone, communicate with it over USB-serial, or USB-networking.

A: Plug external devices, such as wifi, cameras, or mass-storage devices in. The "Mass Market" version of the phone will have wifi integrated.

==== Q: What can't I do with the USB? ====

The USB on the neo has no power output. This means that you cannot use USB bus powered devices without some sort of powered hub or cable.
This is due to the fact that adding a 5V power supply into the device would have added complexity, volume and cost.

Many powered USB devices don't work without at least a nominal amount of 5v power from the USB bus. A few powered USB hubs will work without 5v power from the host, but most powered ones need to have simple electrical modifications done to work.

==== Q: Why is only USB 1.1 provided? ====

A: The processor has USB 1.1 built in. One with USB2 built in would have been more expensive.

==== Q: Can the Neo charge and use devices on a USB hub at the same time? ====

A:
*When the Neo is connected to a device port on a USB hub, it will start charging. If the hub is a powered hub, then it will charge fast (3h), otherwise around 12h.

*If you plug the Neo into the host port of a USB hub you can use devices on that hub but the Neo will not charge. (Some/many USB hubs will not accept an unpowered host as valid, hence the need for the below cable.)
*This is because the host socket on USB hubs is not powered.

FIC product development is looking into providing something that
conveniently solves this problem.

The USB port on the Neo is not a properly compliant USB host port, all USB host ports must provide 5V - though powered devices or hubs may not draw any current from this, they may refuse to work. (The Belkin Tetrahub is an example of a hub that will not work.)

One solution is a three headed cable.

One end plugs into the Neo. One end plugs into a device port of a powered hub, or the Neo charger. One end plugs into the host port of a hub.

The Charger/USB device plug only has +5V and 0V connected in the simple cable, which are connected to the other ends.

For a more complex cable, when the host socket is not plugged in, the cable acts as a simple USB cable.

==== Q: What are the details of the USB port on the [[Neo1973]]? How does it compare to USB On-The-Go? ====

A: The [[Neo1973]] will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just
a AB socket, but also electrical and software components which cannot be provide by the S3C2410.

You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).

=== Q: Are there any LEDs on the Neo 1973? ===

A: The [[Neo1973]] P1/P2 will have no LEDs besides the screen backlight.

=== Q: Will a JTAG port be made available? ===

A: The "Hacker's Lunchbox" in Advanced version will make this kind of stuff easy.

There are [[Neo1973_Hardware#Changes_from_GTA01Bv3|exposed I2C, SPI and debug board connectors]] inside case in all versions and [[Debug Board|Debug Board v2]] (JTAG and serial console) in Advanced version. [[Connecting Neo1973 with Debug Board v2]] explains how to connect it to the phone.

=== Q: What can we expect in future versions? ===

A: A faster CPU, faster GSM (EDGE?) perhaps even powered USB port, USB2, wifi, and camera. No details have been released yet. More details of hardware upgrades should be available sometime in May. There will also be 5 more OpenMoko devices - some not phones in the traditional sense - announced by FIC in September.

==Networking/Connectivity==

=== Q: What kind of connectivity? ===

A: Quad-band GSM, GPRS Class12/CS4 2.5G (Not EDGE), Bluetooth 2.0 EDR, USB in all versions. WiFi: Atheros AR6K in [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]. (No 3G in year 2007 models)

=== Q: Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ===

A: Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].

=== Q: What providers provide the GSM required for Neo1973? ===

A: See [[Neo1973 compatible cellphone providers]]

=== Q: Will OpenMoko "Just Work" with Mac OS X? ===

A: There has been some discussion of this on the mailing list. There is motivation, and there are interested developers.
Not being a Mac OS X user, I don't know enough
to summarize the discussion to answer this question. Can someone please fill in?

A: For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the OpenMoko.

A: It is expected that (Bluetooth/UB) SyncML based interoperation for
contacts and events can easily be achieved by a patch
to the Apple iSync configuration tables.

A: There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of
PPC/x86/ARM universal binaries) on OpenMoko devices: mySTEP.

==Misc==

=== Q: On the lists on lists.openmoko.org, should replies be added above or below the original text? ===

A: Please reply UNDER post.

=== Q: How can I find out if a question or topic has already been discussed on the mailing lists? ===

A: By searching the mailing list archives. For example, using Google searches:

site:openmoko.org text

For example, to search for accelerometer:

site:openmoko.org accelerometer

If you only want to read the "official" mails from FIC people or from OpenMoko people:

site:openmoko.org text "at fic.com.tw"
site:openmoko.org text "at openmoko.org"

For example to search for "release date" from FIC people:

site:openmoko.org "release date" "at fic.com.tw"

Alternatively you can use the [http://www.google.com/coop/cse?cx=017507431580478583395%3Astsl7lhxzbc custom OpenMoko search engine] which has been created using [http://www.google.com/coop/ Google Co-op].

=== Q:Can I has some money for a Neo1973? ===

A: No.

{{Languages|FAQ}}

[[Category:Information]]

FAQ

2007-08-06T21:49:58Z

Tommy: /* Q: What can I do with the USB port on the Neo1973? */ wifi info.

Questions and Answers that don't seem to fit elsewhere

==Introduction==

=== Q: What is OpenMoko and Neo1973? ===
A: [[OpenMoko]] is a software platform, an attempt to create the world's first completely open mobile phone software stack. The [[FIC]] [[Neo1973]] is the first fully supported OpenMoko phone.

=== Q: I'm a ____ expert, can I join/help OpenMoko? ===

We would love to hear from you.

If you are interested in joining OpenMoko, please visit http://www.openmoko.com/contact-index.html and send us an e-mail. Or simply post a message to our community list if you just want to help.

=== Q: When can I buy a [[Neo1973]]? ===

A: Now - from https://direct.openmoko.com/. But please see "What will it do?" below first.

=== Q: How much? ===

A: Neo1973 GTA01B_v04: $300 for Neo Base, $450 for Neo Advanced. Available now. See [[Neo1973]] for what is included.

A: Neo1973 GTA02: $450 for Neo Base, $600 for Neo Advanced. Planned to be available Fall 2007. See [[Neo1973]] for list of hardware.

=== Q: What will it do? ===

A: For long answer see [[Developer preview]]

A: The Phase 1 phone is aimed at developers only. It is not suitable for end users, it will have basic functionality as a touchscreen phone. Little else will work, software development will continue till mass market release.

Those interested should:

* Know that there will be a device with faster cpu, gsm system etc. 4-5 months later (GTA02)
* Have fun hacking devices.
* Be able to find their way through prototype software and hardware without much documentation.
* Share the dream of a device powered by free software.
* Not expect a consumer-level device.
* Come up with new ideas for exploring the age of mobile computing.
* Have $300.

Ideally they also:

* Can spot bugs and submit patches.
* Love to cooperate with a community improving the software.

=== Q: Do I need Neo Advanced? ===

With Neo Base you can do:
* Kernel development.
* Application developemnt.
* Updating u-boot (equivalent to PC BIOS) using a tested image.
* Replace a non-booting kernel and/or rootfs using [[Dfu-util]].

With Neo Advanced you can additionally do:
* U-boot development.
* Use the kernel console.
* Unbrick your device if you flash a wrong or non-working u-boot image.

=== Q: I have a shipping related question ===

See [[SH1_FAQ|Shipment 1 FAQ]].

=== Q: What will the [[Neo1973]] look like? ===

See the proposed [[Artwork|artwork]].

==Software==

=== Q: Can the software do/connect to/... ===
A: At the moment, the answer is in almost all cases no. The phone is at the moment a small linux box with a touchscreen, a working dialer and some prototype apps.
Most do not function in any way that would be suitable for users.
If you want to add a feature or application request, then look over the existing applications and either add one, or add a feature request to the applications page.

===What software is on the phone?===
At the moment, almost no 'end-user' applications are present and working in a usable state.
It is possible to make and receive calls in some software revisions, this frequently breaks though.

====What software can be installed on the phone?====

=== Q: Is there description and list of OpenMoko software? ===

A: See [[OpenMoko]] and [[OpenMokoFramework]]

=== Q: Is it completely free software/open source? ===

A: User space [[Gpsd]] will use binary plugin for [[:Category:Neo1973 Hardware#AGPS|Hammerhead AGPS]] and [[:Category:Neo1973 Hardware#GSM.2FGPRS|GSM modem]] is separate subsystem connected to S3C2410 UART1. Otherwise it is completely free software. See [[MokoMakefile]] and [[Development resources]].

=== Q: How do I install and manage software on OpenMoko? ===

A: ipkg: http://handhelds.org/moin/moin.cgi/Ipkg

=== Q: How can I compile programs for the Neo1973? ===

A: See [[Toolchain]].

=== Q: Is there an emulator available for OpenMoko? ===

For a lot of testing and development work, you don't actually need emulation as you can run OpenMoko on a normal PC too. The emulators also aren't 100% accurate. That being said, there are several emulation options as described in the following.

====QEMU====
QEMU can now emulate the Neo1973 device. The [[MokoMakefile]] has support for automatically building, flashing, and running [[OpenMoko under QEMU|the Neo1973 emulator]].

“make qemu” will build qemu-neo1973, download the latest official openmoko images, flash the images into the virtual NAND flash, and run the emulator.

====Xoo====
Another is [http://projects.o-hand.com/xoo Xoo]. Koen says: "Xoo should be enough for most apps people will develop, since most don't need access to the gsm uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".

Update: Stefan Schmidt has resized the [[Neo1973]] Mock-up and written a small description for xoo. In his words:

It's not really useable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.

http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2

Start with 'xoo --device /path/to/neo1973.xml'

Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].

====Xephyr====
Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):
Xephyr -screen 480x640 -nolisten tcp -ac :1 &
export DISPLAY=:1
export LD_LIBRARY_PATH=/usr/local/lib
matchbox-window-manager -display $DISPLAY -use_titlebar no \
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \
-use_cursor yes &
matchbox-panel --geometry=480x44 --end-applets=clock &
openmoko-footer &
openmoko-taskmanager &

=== Q: Where can I find some type of tutorial for a 'Hello, world' on OpenMoko? ===

A: This should get you started:
http://www.gtk.org/tutorial/

=== Q: Can PalmOS apps applications be ported to run on OpenMoko? ===

A: Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux
is decidedly non-trivial.

PalmOS apps are in general very hard to simply 'port'. Particularly well-designed programs may make it possible.

The ACCESS Linux Platform will include Garnet on Host (GHost), a PalmOS emulator that will support M6800 (68k) and ARM PalmOS applications. This part (GarnetVM and the .prc loader) will however be closed-source and likely under a restrictive license (fact confirmed by ACCESS Co. employees), making it rather unusable. In addition GarnetVM depends on Hiker and other packages.

It is possible that POSE, an emulator that simulates a Palm device on a Linux host could be used to allow 68k based applications to run. This emulator has been around a long time; one expects that it will also run on OpenMoko, but this has to be considered a short-term bandaid rather than a long-term solution.

The soon-to-be-released [http://www.palm.com/foleo/ Palm Foleo], which runs a Linux port developed by Palm Inc. independently of ALP, contains a PalmOS compatibility environment that runs PalmOS apps, supposedly all of them and supposedly seamlessly. Little is known about how it works but if it's not too kludgy it should run unmodified on any ARM linux. It is not known what license it will be distributed under.

Hopefully emulation will be necessary only for M68000 code (pre-PalmOS 5) while native ARM programs can run natively under Linux, provided a proper set of PalmOS libraries and a .prc executable loader.

=== Q: Does it have Java? ===
A: It will have eventually, if you help us to get it working. Some good places to keep track of would be [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] and [https://phoneme.dev.java.net/ PhoneME].

=== Q: What are the relevant X11 details? ===

A: See [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].

=== Q: Does OpenMoko run on any other hardware? ===

You can run it on your [[How_to_run_OpenMoko_Apps_on_PC|PC]]. There is work going on with [http://www.datenfreihafen.org/~stefan/weblog//archives/2007/02/#e2007-02-18T15_27_07.txt OpenEZX and HTC]. It's running on [http://dominion.kabel.utwente.nl/koen/cms/openmoko-running-on-an-ipaq iPaq hx4700], on a [http://hackndev.com/node/701 Palm TX] and on [http://blog.mikeasoft.com/2007/07/01/openmoko-on-a-treo-650/ PalmOne's Treo 650].

=== Q: What are the requirements to the hardware to run OpenMoko? (Would it run on the IXI ogo?) ===

=== Q: Why do you not build on top of the Maemo platform instead? ===

While I can't speak for the OpenMoko team, it's worth noting that maemo is fixed resolution only. That will, I've heard, change in the future, but it hasn't yet. Maemo's current layout is also optimized for wide screens, not tall narrow ones. Most third party maemo applications that are out there will need to be modified to work at different sizes. Finally, a number of the software components of the Nokia 770 and N800 are not open source. --gopi

To add up on that, according to Nokia, Maemo is designed to bring the "Desktop" experience to an Internet Tablet. A lot of Desktop paradigms just won't work on a phone. However, we really share a lot of the base-technology (gtk, dbus, eds, gconf, to name a few) with Maemo, so we are definitely not a reinvent-the-wheel team.

=== Q: Will it be possible to use popular VoIP applications such as Skype on the OpenMoko platform? ===

A: Perhaps. Hardware issues mean that it won't work well on the Neo1973. (the typical latency of GPRS is far too high). Also, Skype is a closed source application, which does not provide binaries that would be suitable to run on OpenMoko. Skype's vendor could of course choose to provide binaries for OpenMoko phones. However, many telephone providers' terms of service agreements preclude running VoIP over their baseline GSM service.

=== Q: Same question for Instant Messaging applications such as MSN Messenger? ===

A: Very probably. MSN is closed source and will only run where Microsoft wants you to run it. But there are many Open Source IM clients, many of which have a plugin architecture and so support the use of more than one IM protocol, even simultaneously. One example is [http://www.pidgin.im Pidgin, formerly called GAIM]. GPRS does induce a certain amount of latency but that should not be a problem for simple, text-oriented chat between parties. And the GTA02's WiFi will make it even better.

==Neo1973 Hardware==

=== Q: Is there description of [[:Category:Neo1973 Hardware | Neo1973 Hardware]] ? ===

A: See [[:Category:Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]]

=== Q: What are the dimensions? ===

A: 120.7 x 62 x 18.5 mm, It would fit entirely in a coke can. (4.75 * 2.4 * 0.72 ")

=== Q: How heavy is it? ===

A: 185g, (6.5 ounces).

=== Q: Does it have a camera? ===

A: No, see [[:Category:Neo1973 Hardware | Neo1973]] for details on what it does include (and [[Wish List - Hardware]] for what some want in the future.) See also [[FAQ#USB]].

=== Q: Does it have Wifi? ===

A: The currently available [[Neo1973]] does not have WiFi. There was no suitable Wifi device available when it was designed. The next version will have WiFi. See also [[FAQ#USB]].

=== Q: Does it have bluetooth? ===

A: Yes! Bluetooth 2.0.

=== Q: Does it come with a stylus? ===

A: Yes, but there's no holder for it on the phone.

=== Q: Where are the buttons? ===

The power button is a small circular button, just next to the USB connector. [[Neo1973 Power Button]]
The Auxilliary button is a rectangular button on the top left of the edge of the phone. (on black phones it looks just like an IRDA port). [[Neo1973 AUX Button]]

=== Q: How do I input text? ===

A: Use provided keyboard app.

A: Use Bluetooth keyboard.

A: For more methods and ideas see [[Wishlist:Text_Input]].

=== Q: Can I record calls and/or play audio files in calls? ===

A: Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing an [[Answering Machine]] is possible. Also using text->speech should be possible or modifying outgoing voice. Currently there is no software bundled in phone to do this.
There are only 2 A/D inputs and three D/A outputs (one dedicated to the earpiece). This means that stereo audio playback cannot happen at the same time as the [[Answering Machine]] functionality, amongst other things. See the audio page. (which?){{fixme}}

=== Q: What is the battery life? ===

A: There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].

=== USB ===

==== Q: What can I do with the USB port on the Neo1973? ====
A: Charge the phone, communicate with it over USB-serial, or USB-networking.

A: Plug external devices, such as wifi, cameras, or mass-storage devices in. The "Mass Market" version of the phone will have wifi integrated.

==== Q: What can't I do with the USB? ====

The USB on the neo has no power output. This means that you cannot use USB bus powered devices without some sort of powered hub or cable.
This is due to the fact that adding a 5V power supply into the device would have added complexity, volume and cost.

Many powered USB devices don't work without at least a nominal amount of 5v power from the USB bus. A few powered USB hubs will work without 5v power from the host, but most powered ones need to have simple electrical modifications done to work.

==== Q: Why is only USB 1.1 provided? ====

A: The processor has USB 1.1 built in. One with USB2 built in would have been more expensive.

==== Q: Can the Neo charge and use devices on a USB hub at the same time? ====

A:
*When the Neo is connected to a device port on a USB hub, it will start charging. If the hub is a powered hub, then it will charge fast (3h), otherwise around 12h.

*If you plug the Neo into the host port of a USB hub you can use devices on that hub but the Neo will not charge. (Some/many USB hubs will not accept an unpowered host as valid, hence the need for the below cable.)
*This is because the host socket on USB hubs is not powered.

FIC product development is looking into providing something that
conveniently solves this problem.

The USB port on the Neo is not a properly compliant USB host port, all USB host ports must provide 5V - though powered devices or hubs may not draw any current from this, they may refuse to work. (The Belkin Tetrahub is an example of a hub that will not work.)

One solution is a three headed cable.

One end plugs into the Neo. One end plugs into a device port of a powered hub, or the Neo charger. One end plugs into the host port of a hub.

The Charger/USB device plug only has +5V and 0V connected in the simple cable, which are connected to the other ends.

For a more complex cable, when the host socket is not plugged in, the cable acts as a simple USB cable.

==== Q: What are the details of the USB port on the [[Neo1973]]? How does it compare to USB On-The-Go? ====

A: The [[Neo1973]] will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just
a AB socket, but also electrical and software components which cannot be provide by the S3C2410.

You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).

=== Q: Are there any LEDs on the Neo 1973? ===

A: The [[Neo1973]] P1/P2 will have no LEDs besides the screen backlight.

=== Q: Will a JTAG port be made available? ===

A: The "Hacker's Lunchbox" in Advanced version will make this kind of stuff easy.

There are [[Neo1973_Hardware#Changes_from_GTA01Bv3|exposed I2C, SPI and debug board connectors]] inside case in all versions and [[Debug Board|Debug Board v2]] (JTAG and serial console) in Advanced version. [[Connecting Neo1973 with Debug Board v2]] explains how to connect it to the phone.

=== Q: What can we expect in future versions? ===

A: A faster CPU, faster GSM (EDGE?) perhaps even powered USB port, USB2, wifi, and camera. No details have been released yet. More details of hardware upgrades should be available sometime in May. There will also be 5 more OpenMoko devices - some not phones in the traditional sense - announced by FIC in September.

==Networking/Connectivity==

=== Q: What kind of connectivity? ===

A: Quad-band GSM, GPRS Class12/CS4 2.5G (Not EDGE), Bluetooth 2.0 EDR, USB in all versions. WiFi: Atheros AR6K in [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]. (No 3G in year 2007 models)

=== Q: Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ===

A: Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].

=== Q: What providers provide the GSM required for Neo1973? ===

A: See [[Neo1973 compatible cellphone providers]]

=== Q: Will OpenMoko "Just Work" with Mac OS X? ===

A: There has been some discussion of this on the mailing list. There is motivation, and there are interested developers.
Not being a Mac OS X user, I don't know enough
to summarize the discussion to answer this question. Can someone please fill in?

A: For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the OpenMoko.

A: It is expected that (Bluetooth/UB) SyncML based interoperation for
contacts and events can easily be achieved by a patch
to the Apple iSync configuration tables.

A: There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of
PPC/x86/ARM universal binaries) on OpenMoko devices: mySTEP.

==Misc==

=== Q: On the lists on lists.openmoko.org, should replies be added above or below the original text? ===

A: Please reply UNDER post.

=== Q: How can I find out if a question or topic has already been discussed on the mailing lists? ===

A: By searching the mailing list archives. For example, using Google searches:

site:openmoko.org text

For example, to search for accelerometer:

site:openmoko.org accelerometer

If you only want to read the "official" mails from FIC people or from OpenMoko people:

site:openmoko.org text "at fic.com.tw"
site:openmoko.org text "at openmoko.org"

For example to search for "release date" from FIC people:

site:openmoko.org "release date" "at fic.com.tw"

Alternatively you can use the [http://www.google.com/coop/cse?cx=017507431580478583395%3Astsl7lhxzbc custom OpenMoko search engine] which has been created using [http://www.google.com/coop/ Google Co-op].

=== Q:Can I has some money for a Neo1973 ===

A:No.

{{Languages|FAQ}}

[[Category:Information]]

FAQ

2007-08-06T21:43:21Z

Tommy: /* Q: Does it have bluetooth? */

Questions and Answers that don't seem to fit elsewhere

==Introduction==

=== Q: What is OpenMoko and Neo1973? ===
A: [[OpenMoko]] is a software platform, an attempt to create the world's first completely open mobile phone software stack. The [[FIC]] [[Neo1973]] is the first fully supported OpenMoko phone.

=== Q: I'm a ____ expert, can I join/help OpenMoko? ===

We would love to hear from you.

If you are interested in joining OpenMoko, please visit http://www.openmoko.com/contact-index.html and send us an e-mail. Or simply post a message to our community list if you just want to help.

=== Q: When can I buy a [[Neo1973]]? ===

A: Now - from https://direct.openmoko.com/. But please see "What will it do?" below first.

=== Q: How much? ===

A: Neo1973 GTA01B_v04: $300 for Neo Base, $450 for Neo Advanced. Available now. See [[Neo1973]] for what is included.

A: Neo1973 GTA02: $450 for Neo Base, $600 for Neo Advanced. Planned to be available Fall 2007. See [[Neo1973]] for list of hardware.

=== Q: What will it do? ===

A: For long answer see [[Developer preview]]

A: The Phase 1 phone is aimed at developers only. It is not suitable for end users, it will have basic functionality as a touchscreen phone. Little else will work, software development will continue till mass market release.

Those interested should:

* Know that there will be a device with faster cpu, gsm system etc. 4-5 months later (GTA02)
* Have fun hacking devices.
* Be able to find their way through prototype software and hardware without much documentation.
* Share the dream of a device powered by free software.
* Not expect a consumer-level device.
* Come up with new ideas for exploring the age of mobile computing.
* Have $300.

Ideally they also:

* Can spot bugs and submit patches.
* Love to cooperate with a community improving the software.

=== Q: Do I need Neo Advanced? ===

With Neo Base you can do:
* Kernel development.
* Application developemnt.
* Updating u-boot (equivalent to PC BIOS) using a tested image.
* Replace a non-booting kernel and/or rootfs using [[Dfu-util]].

With Neo Advanced you can additionally do:
* U-boot development.
* Use the kernel console.
* Unbrick your device if you flash a wrong or non-working u-boot image.

=== Q: I have a shipping related question ===

See [[SH1_FAQ|Shipment 1 FAQ]].

=== Q: What will the [[Neo1973]] look like? ===

See the proposed [[Artwork|artwork]].

==Software==

=== Q: Can the software do/connect to/... ===
A: At the moment, the answer is in almost all cases no. The phone is at the moment a small linux box with a touchscreen, a working dialer and some prototype apps.
Most do not function in any way that would be suitable for users.
If you want to add a feature or application request, then look over the existing applications and either add one, or add a feature request to the applications page.

===What software is on the phone?===
At the moment, almost no 'end-user' applications are present and working in a usable state.
It is possible to make and receive calls in some software revisions, this frequently breaks though.

====What software can be installed on the phone?====

=== Q: Is there description and list of OpenMoko software? ===

A: See [[OpenMoko]] and [[OpenMokoFramework]]

=== Q: Is it completely free software/open source? ===

A: User space [[Gpsd]] will use binary plugin for [[:Category:Neo1973 Hardware#AGPS|Hammerhead AGPS]] and [[:Category:Neo1973 Hardware#GSM.2FGPRS|GSM modem]] is separate subsystem connected to S3C2410 UART1. Otherwise it is completely free software. See [[MokoMakefile]] and [[Development resources]].

=== Q: How do I install and manage software on OpenMoko? ===

A: ipkg: http://handhelds.org/moin/moin.cgi/Ipkg

=== Q: How can I compile programs for the Neo1973? ===

A: See [[Toolchain]].

=== Q: Is there an emulator available for OpenMoko? ===

For a lot of testing and development work, you don't actually need emulation as you can run OpenMoko on a normal PC too. The emulators also aren't 100% accurate. That being said, there are several emulation options as described in the following.

====QEMU====
QEMU can now emulate the Neo1973 device. The [[MokoMakefile]] has support for automatically building, flashing, and running [[OpenMoko under QEMU|the Neo1973 emulator]].

“make qemu” will build qemu-neo1973, download the latest official openmoko images, flash the images into the virtual NAND flash, and run the emulator.

====Xoo====
Another is [http://projects.o-hand.com/xoo Xoo]. Koen says: "Xoo should be enough for most apps people will develop, since most don't need access to the gsm uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".

Update: Stefan Schmidt has resized the [[Neo1973]] Mock-up and written a small description for xoo. In his words:

It's not really useable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.

http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2

Start with 'xoo --device /path/to/neo1973.xml'

Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].

====Xephyr====
Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):
Xephyr -screen 480x640 -nolisten tcp -ac :1 &
export DISPLAY=:1
export LD_LIBRARY_PATH=/usr/local/lib
matchbox-window-manager -display $DISPLAY -use_titlebar no \
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \
-use_cursor yes &
matchbox-panel --geometry=480x44 --end-applets=clock &
openmoko-footer &
openmoko-taskmanager &

=== Q: Where can I find some type of tutorial for a 'Hello, world' on OpenMoko? ===

A: This should get you started:
http://www.gtk.org/tutorial/

=== Q: Can PalmOS apps applications be ported to run on OpenMoko? ===

A: Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux
is decidedly non-trivial.

PalmOS apps are in general very hard to simply 'port'. Particularly well-designed programs may make it possible.

The ACCESS Linux Platform will include Garnet on Host (GHost), a PalmOS emulator that will support M6800 (68k) and ARM PalmOS applications. This part (GarnetVM and the .prc loader) will however be closed-source and likely under a restrictive license (fact confirmed by ACCESS Co. employees), making it rather unusable. In addition GarnetVM depends on Hiker and other packages.

It is possible that POSE, an emulator that simulates a Palm device on a Linux host could be used to allow 68k based applications to run. This emulator has been around a long time; one expects that it will also run on OpenMoko, but this has to be considered a short-term bandaid rather than a long-term solution.

The soon-to-be-released [http://www.palm.com/foleo/ Palm Foleo], which runs a Linux port developed by Palm Inc. independently of ALP, contains a PalmOS compatibility environment that runs PalmOS apps, supposedly all of them and supposedly seamlessly. Little is known about how it works but if it's not too kludgy it should run unmodified on any ARM linux. It is not known what license it will be distributed under.

Hopefully emulation will be necessary only for M68000 code (pre-PalmOS 5) while native ARM programs can run natively under Linux, provided a proper set of PalmOS libraries and a .prc executable loader.

=== Q: Does it have Java? ===
A: It will have eventually, if you help us to get it working. Some good places to keep track of would be [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] and [https://phoneme.dev.java.net/ PhoneME].

=== Q: What are the relevant X11 details? ===

A: See [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].

=== Q: Does OpenMoko run on any other hardware? ===

You can run it on your [[How_to_run_OpenMoko_Apps_on_PC|PC]]. There is work going on with [http://www.datenfreihafen.org/~stefan/weblog//archives/2007/02/#e2007-02-18T15_27_07.txt OpenEZX and HTC]. It's running on [http://dominion.kabel.utwente.nl/koen/cms/openmoko-running-on-an-ipaq iPaq hx4700], on a [http://hackndev.com/node/701 Palm TX] and on [http://blog.mikeasoft.com/2007/07/01/openmoko-on-a-treo-650/ PalmOne's Treo 650].

=== Q: What are the requirements to the hardware to run OpenMoko? (Would it run on the IXI ogo?) ===

=== Q: Why do you not build on top of the Maemo platform instead? ===

While I can't speak for the OpenMoko team, it's worth noting that maemo is fixed resolution only. That will, I've heard, change in the future, but it hasn't yet. Maemo's current layout is also optimized for wide screens, not tall narrow ones. Most third party maemo applications that are out there will need to be modified to work at different sizes. Finally, a number of the software components of the Nokia 770 and N800 are not open source. --gopi

To add up on that, according to Nokia, Maemo is designed to bring the "Desktop" experience to an Internet Tablet. A lot of Desktop paradigms just won't work on a phone. However, we really share a lot of the base-technology (gtk, dbus, eds, gconf, to name a few) with Maemo, so we are definitely not a reinvent-the-wheel team.

=== Q: Will it be possible to use popular VoIP applications such as Skype on the OpenMoko platform? ===

A: Perhaps. Hardware issues mean that it won't work well on the Neo1973. (the typical latency of GPRS is far too high). Also, Skype is a closed source application, which does not provide binaries that would be suitable to run on OpenMoko. Skype's vendor could of course choose to provide binaries for OpenMoko phones. However, many telephone providers' terms of service agreements preclude running VoIP over their baseline GSM service.

=== Q: Same question for Instant Messaging applications such as MSN Messenger? ===

A: Very probably. MSN is closed source and will only run where Microsoft wants you to run it. But there are many Open Source IM clients, many of which have a plugin architecture and so support the use of more than one IM protocol, even simultaneously. One example is [http://www.pidgin.im Pidgin, formerly called GAIM]. GPRS does induce a certain amount of latency but that should not be a problem for simple, text-oriented chat between parties. And the GTA02's WiFi will make it even better.

==Neo1973 Hardware==

=== Q: Is there description of [[:Category:Neo1973 Hardware | Neo1973 Hardware]] ? ===

A: See [[:Category:Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]]

=== Q: What are the dimensions? ===

A: 120.7 x 62 x 18.5 mm, It would fit entirely in a coke can. (4.75 * 2.4 * 0.72 ")

=== Q: How heavy is it? ===

A: 185g, (6.5 ounces).

=== Q: Does it have a camera? ===

A: No, see [[:Category:Neo1973 Hardware | Neo1973]] for details on what it does include (and [[Wish List - Hardware]] for what some want in the future.) See also [[FAQ#USB]].

=== Q: Does it have Wifi? ===

A: The currently available [[Neo1973]] does not have WiFi. There was no suitable Wifi device available when it was designed. The next version will have WiFi. See also [[FAQ#USB]].

=== Q: Does it have bluetooth? ===

A: Yes! Bluetooth 2.0.

=== Q: Does it come with a stylus? ===

A: Yes, but there's no holder for it on the phone.

=== Q: Where are the buttons? ===

The power button is a small circular button, just next to the USB connector. [[Neo1973 Power Button]]
The Auxilliary button is a rectangular button on the top left of the edge of the phone. (on black phones it looks just like an IRDA port). [[Neo1973 AUX Button]]

=== Q: How do I input text? ===

A: Use provided keyboard app.

A: Use Bluetooth keyboard.

A: For more methods and ideas see [[Wishlist:Text_Input]].

=== Q: Can I record calls and/or play audio files in calls? ===

A: Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing an [[Answering Machine]] is possible. Also using text->speech should be possible or modifying outgoing voice. Currently there is no software bundled in phone to do this.
There are only 2 A/D inputs and three D/A outputs (one dedicated to the earpiece). This means that stereo audio playback cannot happen at the same time as the [[Answering Machine]] functionality, amongst other things. See the audio page. (which?){{fixme}}

=== Q: What is the battery life? ===

A: There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].

=== USB ===

==== Q: What can I do with the USB port on the Neo1973? ====
A: Charge the phone, communicate with it over USB-serial, or USB-networking.

A: Plug external devices, such as wifi, cameras, or mass-storage devices in.

==== Q: What can't I do with the USB? ====

The USB on the neo has no power output. This means that you cannot use USB bus powered devices without some sort of powered hub or cable.
This is due to the fact that adding a 5V power supply into the device would have added complexity, volume and cost.

Many powered USB devices don't work without at least a nominal amount of 5v power from the USB bus. A few powered USB hubs will work without 5v power from the host, but most powered ones need to have simple electrical modifications done to work.

==== Q: Why is only USB 1.1 provided? ====

A: The processor has USB 1.1 built in. One with USB2 built in would have been more expensive.

==== Q: Can the Neo charge and use devices on a USB hub at the same time? ====

A:
*When the Neo is connected to a device port on a USB hub, it will start charging. If the hub is a powered hub, then it will charge fast (3h), otherwise around 12h.

*If you plug the Neo into the host port of a USB hub you can use devices on that hub but the Neo will not charge. (Some/many USB hubs will not accept an unpowered host as valid, hence the need for the below cable.)
*This is because the host socket on USB hubs is not powered.

FIC product development is looking into providing something that
conveniently solves this problem.

The USB port on the Neo is not a properly compliant USB host port, all USB host ports must provide 5V - though powered devices or hubs may not draw any current from this, they may refuse to work. (The Belkin Tetrahub is an example of a hub that will not work.)

One solution is a three headed cable.

One end plugs into the Neo. One end plugs into a device port of a powered hub, or the Neo charger. One end plugs into the host port of a hub.

The Charger/USB device plug only has +5V and 0V connected in the simple cable, which are connected to the other ends.

For a more complex cable, when the host socket is not plugged in, the cable acts as a simple USB cable.

==== Q: What are the details of the USB port on the [[Neo1973]]? How does it compare to USB On-The-Go? ====

A: The [[Neo1973]] will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just
a AB socket, but also electrical and software components which cannot be provide by the S3C2410.

You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).

=== Q: Are there any LEDs on the Neo 1973? ===

A: The [[Neo1973]] P1/P2 will have no LEDs besides the screen backlight.

=== Q: Will a JTAG port be made available? ===

A: The "Hacker's Lunchbox" in Advanced version will make this kind of stuff easy.

There are [[Neo1973_Hardware#Changes_from_GTA01Bv3|exposed I2C, SPI and debug board connectors]] inside case in all versions and [[Debug Board|Debug Board v2]] (JTAG and serial console) in Advanced version. [[Connecting Neo1973 with Debug Board v2]] explains how to connect it to the phone.

=== Q: What can we expect in future versions? ===

A: A faster CPU, faster GSM (EDGE?) perhaps even powered USB port, USB2, wifi, and camera. No details have been released yet. More details of hardware upgrades should be available sometime in May. There will also be 5 more OpenMoko devices - some not phones in the traditional sense - announced by FIC in September.

==Networking/Connectivity==

=== Q: What kind of connectivity? ===

A: Quad-band GSM, GPRS Class12/CS4 2.5G (Not EDGE), Bluetooth 2.0 EDR, USB in all versions. WiFi: Atheros AR6K in [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]. (No 3G in year 2007 models)

=== Q: Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ===

A: Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].

=== Q: What providers provide the GSM required for Neo1973? ===

A: See [[Neo1973 compatible cellphone providers]]

=== Q: Will OpenMoko "Just Work" with Mac OS X? ===

A: There has been some discussion of this on the mailing list. There is motivation, and there are interested developers.
Not being a Mac OS X user, I don't know enough
to summarize the discussion to answer this question. Can someone please fill in?

A: For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the OpenMoko.

A: It is expected that (Bluetooth/UB) SyncML based interoperation for
contacts and events can easily be achieved by a patch
to the Apple iSync configuration tables.

A: There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of
PPC/x86/ARM universal binaries) on OpenMoko devices: mySTEP.

==Misc==

=== Q: On the lists on lists.openmoko.org, should replies be added above or below the original text? ===

A: Please reply UNDER post.

=== Q: How can I find out if a question or topic has already been discussed on the mailing lists? ===

A: By searching the mailing list archives. For example, using Google searches:

site:openmoko.org text

For example, to search for accelerometer:

site:openmoko.org accelerometer

If you only want to read the "official" mails from FIC people or from OpenMoko people:

site:openmoko.org text "at fic.com.tw"
site:openmoko.org text "at openmoko.org"

For example to search for "release date" from FIC people:

site:openmoko.org "release date" "at fic.com.tw"

Alternatively you can use the [http://www.google.com/coop/cse?cx=017507431580478583395%3Astsl7lhxzbc custom OpenMoko search engine] which has been created using [http://www.google.com/coop/ Google Co-op].

=== Q:Can I has some money for a Neo1973 ===

A:No.

{{Languages|FAQ}}

[[Category:Information]]