http://wiki.openmoko.org/api.php?action=feedcontributions&user=Erin&feedformat=atomOpenmoko - User contributions [en]2013-05-22T02:22:01ZUser contributionsMediaWiki 1.19.6http://wiki.openmoko.org/wiki/Manually_using_BluetoothManually using Bluetooth2008-12-02T08:41:16Z<p>Erin: /* OBEX */</p>
<hr />
<div>{{InProgress}}<br />
Bluetooth is one of the core functions of the Neo1973, however it is basically unimplemented on the software side at the moment.<br />
Hardware problems in the P1 phone mean that the CPU has to be active in order to wake on external bluetooth events, which will reduce the battery life to some 2 days at best in standby.<br />
<br />
This page details how to use bluetooth from the command line.<br />
We have quite a lot of plans about what exactly Bluetooth should be used for.<br />
<br />
== Power it up ==<br />
<br />
Power up the adapter by clicking on the bluetooth icon in the top bar and selecting power on.<br />
<br />
The old way to do it is a shell command (for kernels before 2.6.24):<br />
<br />
root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on<br />
<br />
For kernel 2.6.24 (or later) use<br />
<br />
root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br />
<br />
and on the GTA02 *only* (i.e. not on the GTA01) also use<br />
<br />
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
<br />
But nowadays[http://permalink.gmane.org/gmane.comp.hardware.smartphones.userland/165], one should use [[Dbus device API]]s!<br />
<br />
At the shell, "hciconfig" should print information about the adapter if it powered up properly:<br />
<br />
hciconfig<br />
<br />
The devices should show as UP. If not you can use<br />
<br />
hciconfig <device> up<br />
<br />
== Bluetooth Functions ==<br />
<br />
===Configuring Bluetooth on Openmoko 2007.2 (August 27 snapshot with kernel 2.6.21.6-moko11) ===<br />
<br />
In file /etc/bluetooth/hcid.conf you should change the passkey from BlueZ to something numeric. For testing you may use "0000". Also, you can set the name to "Neo (%d)".<br />
<br />
=== Scanning for bluetooth devices ===<br />
<br />
hcitool scan<br />
<br />
This will list the addresses of any discoverable bluetooth devices in the vicinity<br />
<br />
=== passkey agent example ===<br />
<br />
There should be a passkey agent built into openmoko, but for now you can start up the example passkey agent and set the pin code there. This will allow for new pairings to be made when you attempt a connection.<br />
<br />
passkey-agent --default 0000 &<br />
<br />
Note: the passkey-agent is not required in Openmoko 2007.2 with kernel 2.6.21.6 as of at least since August 27 (maybe earlier).<br />
<br />
=== HID (Human Input Device) ===<br />
<br />
==== Being able to use HID devices ====<br />
<br />
Using a bluetooth keyboard with the built-in terminal is a little funky... I can only type into the console using the bt keyboard if the onscreen keyboard is visible. Also, pressing "p" twice on the bt keyboard actually gives you a "q".<br />
<br />
We want to be able to use a bluetooth keyboard to type into the various applications of our Neo1973.<br />
To use a Bluetooth Keyboard type: (11:22:33:44:55:66 is the Address of your BT-Keyboard)<br />
<br />
hidd --connect 11:22:33:44:55:66<br />
<br />
and press "Connect" on your BT-KB. Alternately, if you know that only one BT-Keyboard is within range, you can just:<br />
<br />
hidd --search<br />
<br />
to find and connect to any BT-Keyboard. There are some bluetooth keyboard only support SPP profile can't direct using hidd comannd to connect. Please reference the discussion of this page for more information.<br />
<br />
Tested on:<br />
* [http://www.logitech.com/index.cfm/products/details/US/EN,CRID=2166,CONTENTID=10717 Logitech Dinovo Edge]<br />
* [http://www.logitech.com/index.cfm/keyboards/keyboard_mice_combos/devices/164&cl=us,en Logitech Dinovo Media Desktop (keyboard)]<br />
* [http://www.nokia.es/A4181580 Nokia SU-8W]. Switched on the BT keyboard, scanned for BT address and ran the connect statement above. Works fine.<br />
* [http://blog.russnelson.com/chordite Chordite]. This keyboard uses the Broadcom BCM2042 BT keyboard controller along with a custom driver.<br />
* [http://www.apple.com/keyboard/ Apple's Aluminum Keyboard]. You may have to add 'auth enable; encrypt enable;' to device {} in hcid.conf. Run the passkey agent the first time. --search works to pair and every time after. (Might be obvious for those who have used BT in other spots, but you have to type in y our passkey on the keyboard as the connect is happening, otherwise pairing doesn't take place. I don't think there is a prompt on the Neo for this)<br />
* [http://www.apple.com/support/keyboard/ Apple's white "Wireless Keyboard (original)"] - details may be the same as above. (tested some time ago)<br />
* [http://www.frogpad.com/ FrogPad] - as above<br />
* [http://freedominput.com The freedom keyboard] and its many rebranded models (they look like this: [http://rabenfrost.net/openmoko/keyboard.jpg]) need 'modprobe uinput' to circumvent the 'Can't open input device: No such file or directory (2)' error of 'hidd --search'. It works as of february 7th 2008.<br />
* [http://www.nextag.com/Playstation-3-Logitech-Cordless-564345667/prices-html?nxtg=f8320a24052a-7789F8FE732FF6E3 Logitech Playstation 3 Keyboard] Works well, Mouse pad works.<br />
* [http://corporate.igo.com/product_details.aspx?id=16 iGo Stowaway UltraSlim] (which was apparently discontinued early 2008, but can still be bought in some places) ([[user:ChristW]] I have 2008.8 on it, and using hidd --search to connect to the iGo works perfectly. I also used it to edit a new contact, dial a number and edit a settings text box in [[TangoGPS]]. So far, no problems...)<br />
* [http://www.vkb-support.com/ I-Tech Virtual Laser Keyboard] works. Cursor keys not recognized as such, but produce keycodes than can be mapped.<br />
<br />
==== Acting as HID device ====<br />
<br />
We want to be able to use the Neo as a HID device, being able to use it as controller for presentations. See [[ReMoko]]<br />
<br />
=== RFCOMM ===<br />
<br />
Here's how to connect to an external Bluetooth GPS and read NMEA data (Tested with a Holux GPSSlim236 and a Nokia LD-3W ).<br />
<br />
First, switch on the GPS and identify the BT address:<br />
<br />
hcitool scan<br />
<br />
Then, edit /etc/bluetooth/rfcomm.conf, which by default has all settings commented out, to something like this:<br />
<br />
rfcomm0 {<br />
# Automatically bind the device at startup<br />
bind no;<br />
# Bluetooth address of the device<br />
device 00:11:22:33:44:55;<br />
# RFCOMM channel for the connection (check your GPS docs for details)<br />
channel 1;<br />
# Description of the connection<br />
comment "Bluetooth GPS";<br />
}<br />
<br />
Restart the BT services:<br />
<br />
root@neo:~$ /etc/init.d/bluetooth stop<br />
root@neo:~$ /etc/init.d/bluetooth start<br />
<br />
You should now be able to bind the GPS to /dev/rfcomm0, like this:<br />
<br />
root@neo:~$ rfcomm bind 0<br />
<br />
Confirm the connect:<br />
<br />
root@neo:~$ rfcomm<br />
rfcomm0: 00:11:22:33:44:55 channel 1 clean <br />
<br />
... and watch the NMEA strings coming from your GPS:<br />
<br />
root@neo:~$ cat /dev/rfcomm0 <br />
$GPGGA,111748.000,5907.6964,N,01121.1787,E,1,06,1.2,57.7,M,40.1,M,,0000*6F<br />
$GPRMC,111748.000,A,5907.6964,N,01121.1787,E,0.00,94.94,160807,,,A*50<br />
$GPVTG,94.94,T,,M,0.00,N,0.0,K,A*3D<br />
<br />
If you have nothing better to do, you can now pinpoint my office :-).<br />
<br />
=== OBEX ===<br />
OBEX (abbreviation of OBject EXchange, also termed IrOBEX) is a communications protocol that facilitates the exchange of binary objects between devices. Here is the notes about how to use OBEX to send/receive files via bluetooth in NEO.<br />
<br />
power on bluetooth: <br />
if you use FSO image<br />
root@om-gta02:~# dbus-send --system --dest=org.freesmartphone.odeviced --type=method_call --print-reply <br />
/org/freesmartphone/Device/PowerControl/Bluetooth org.freesmartphone.Device.PowerControl.SetPower int32:1<br />
else: (GTA02 only)<br />
root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
<br />
[http://linux.die.net/man/5/hcid.conf hcid.conf] <br />
modify /etc/bluetooth/hcid.conf<br />
<br />
<pre><br />
#<br />
# HCI daemon configuration file.<br />
#<br />
<br />
# HCId options<br />
options {<br />
# Automatically initialize new devices<br />
autoinit yes;<br />
<br />
# Security Manager mode<br />
# none - Security manager disabled<br />
# auto - Use local PIN for incoming connections<br />
# user - Always ask user for a PIN<br />
#<br />
security auto;<br />
<br />
# Pairing mode<br />
# none - Pairing disabled<br />
# multi - Allow pairing with already paired devices<br />
# once - Pair once and deny successive attempts<br />
pairing multi;<br />
<br />
# Default PIN code for incoming connections<br />
passkey "1234";<br />
}<br />
<br />
# Default settings for HCI devices<br />
device {<br />
# Local device name<br />
# %d - device id<br />
# %h - host name<br />
name "%h-%d";<br />
<br />
# Local device class<br />
class 0x000100;<br />
<br />
# Default packet type<br />
pkt_type DH1,DM1,HV1;<br />
<br />
# Inquiry and Page scan<br />
iscan enable; pscan enable;<br />
<br />
# Default link mode<br />
# none - no specific policy <br />
# accept - always accept incoming connections<br />
# master - become master on incoming connections,<br />
# deny role switch on outgoing connections<br />
lm accept;<br />
<br />
# Default link policy<br />
# none - no specific policy<br />
# rswitch - allow role switch<br />
# hold - allow hold mode<br />
# sniff - allow sniff mode<br />
# park - allow park mode<br />
lp rswitch,hold,sniff,park;<br />
}<br />
</pre><br />
<br />
[http://linux.die.net/man/8/hcid hcid] - Bluetooth Host Controller Interface Daemon <br />
<br />
All paired devices information are stored in /var/lib/bluetooth/BT HW addr folder <br />
eg. <br />
<pre><br />
root@om-gta02:/var/lib/bluetooth/00:06:6E:16:EB:C7# ls<br />
classes features lastused names panu<br />
config gn manufacturers nap<br />
</pre><br />
<br />
Display local devices<br />
root@om-gta02:/# hcitool dev<br />
<br />
Scan all nearby bluetooth devices<br />
root@om-gta02:~# hcitool scan<br />
<br />
Browse what kind of services in this device<br />
root@om-gta02:~# sdptool browse 00:18:C5:42:18:78<br />
<br />
<pre><br />
Browsing 00:18:C5:42:18:78 ...<br />
<br />
Service Name: OBEX File Transfer<br />
Service RecHandle: 0x1005b<br />
Service Class ID List:<br />
"OBEX File Transfer" (0x1106)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 11<br />
"OBEX" (0x0008)<br />
Language Base Attr List:<br />
code_ISO639: 0x454e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"OBEX File Transfer" (0x1106)<br />
Version: 0x0100<br />
<br />
Service Name: OBEX Object Push<br />
Service RecHandle: 0x1005e<br />
Service Class ID List:<br />
"OBEX Object Push" (0x1105)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 9<br />
"OBEX" (0x0008)<br />
Language Base Attr List:<br />
code_ISO639: 0x454e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"OBEX Object Push" (0x1105)<br />
Version: 0x0100<br />
<br />
</pre><br />
<br />
Use obexpush and obexftp tools<br />
<br />
install obexpush, obexftp packages<br />
opkg install obexpush, [http://www.go2linux.org/linux-command-line-obexftp-man-page obexftp]<br />
<br />
obexpush would launch 'opd' and it's a obex data server. It starts OBEX file transfer service. The default folder is \home\root and it would store all received files here. <br />
<br />
<pre><br />
root@om-gta02:~# ps aux | grep opd<br />
root 1322 0.0 0.4 1972 604 ? Ss 16:21 0:00 opd: waiting for incomming OBEX connections on channel 10...<br />
</pre> <br />
<br />
How to pair with a bluetooth device, check [http://wiki.bluez.org/wiki/Security bluez wiki]<br />
<br />
=== Networking ===<br />
<br />
==== Using PC's connection from Neo ====<br />
<br />
===== Bluetooth networking with a Linux system =====<br />
<br />
Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br />
<br />
'''On the laptop'''<br />
<br />
* Start bluetooth<br />
/etc/init.d/bluetooth start<br />
<br />
* Start pand as server<br />
pand -s<br />
<br />
* As soon as pand is started on the phone configure your IP address<br />
ip a add 10.0.0.1/24 dev bnep0<br />
ip l set bnep0 up<br />
<br />
* Configure IP forwarding and masquerading to your liking (see [[USB_Networking]]). You can even set up Udev rules to do this for you once the bnep0 interface appears.<br />
<br />
<br />
'''On the Neo'''<br />
<br />
* There is a little script that does the steps below (and retries the pand -c command; I had issues with it not working the first time every time) at [[Bt-net-script]] You shouldn't need the other steps below if you use the script.<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
00:0E:6D:C0:0l:6A Sho<br />
00:20:E0:5A:FE:C8 BlueZ (0)<br />
<br />
* Connect to the laptop pand<br />
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br />
<br />
* Configure your IP address<br />
ip a add 10.0.0.2/24 dev bnep0<br />
ip r add default via 10.0.0.1<br />
<br />
* Sometimes you may need to bring up the bnep0 on the phone as well:<br />
ip l set bnep0 up<br />
* Enjoy<br />
<br />
<br />
*--[[User:Mantis|Mantis]] 18:37, 15 October 2008 (UTC) Note for use on OpenSuse 11.0 - I was getting a connection failure with 'Host is down(112)' errors in /var/log/messages (on neo).<br />
I found that editing /etc/bluetooth/hcid.conf to set 'pscan enable' instead of 'pscan disable' and making passkey consistent with Neo Freerunner made it work.<br />
<br />
Should see log line like<br />
''pand[17965]: New connection from 00:06:6E:XX:XX:XX at bnep0''<br />
<br />
if connection is successful in server's /var/log/messages.<br />
<br />
===== Bluetooth networking with a MacOS X system =====<br />
<br />
Please refer to [[MacOS_X#Bluetooth_2]]<br />
<br />
For using the Neo as a dialup Bluetooth server and the Mac as the client, please see below at [[Manually_using_Bluetooth#PPP_Networking]]<br />
<br />
===== Bluetooth networking with a Windows XP system =====<br />
<br />
This was tested with a Windows XP SP2 on a IBM Thinkpad T41 with the Widcomm BT stack<br />
<br />
* Start bluetooth on Windows XP<br />
<br />
* Enable "Network Access" in the Bluetooth configuration<br />
<br />
* Scan for the Neo and pair with the Neo (right click, select pair)<br />
<br />
<br />
On the Neo<br />
<br />
* Enable PAN support on the Neo by changing Autostart from false to true in /etc/bluetooth/network.service<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
<laptop_bt_address> Thinkpad<br />
...<br />
<br />
<br />
* Connect to the laptop pand<br />
pand -c <laptop_bt_address> -r PANU -d NAP -e bnep0 -A -E -S<br />
(add '-n' to see the pand status messages until you get it right)<br />
<br />
For some reason, I was not able to initiate PAN connections from the Neo, I got 'Permission denied (13)' even when I had explicitly allowed the Neo to connect (right click on Neo icon, set properties, on Authorization tab). But initiating 'PAN User' from Windows worked when executing on Neo:<br />
pand -l -r PANU -d NAP -e bnep0 -A -E -S<br />
(add '-n' to see the pand status messages until you get it right)<br />
<br />
<br />
* Configure your IP address. It should work like when connecting to Linux:<br />
ip a add 10.0.0.2/24 dev bnep0<br />
ip r add default via 10.0.0.1<br />
If this does not work, the IP stacks may have auto-assigned network addresses to themselves. You can look this up with 'ifconfig' on the Neo and with 'ipconfig' on Windows.<br />
<br />
<br />
* You should now be able to ssh/putty from Windows to your Neo. Enjoy!<br />
By setting up the Windows Bluetooth connection properly, it should also be possible to share the Internet Connection of the Windows box with the Neo.<br />
<br />
===== PPP Networking =====<br />
<br />
If you are unable to use the 'BNEP' method described above, you may be able to use [[PPP]] and a DUN (dialup-networking) emulation mode. On the Neo:<br />
<br />
* Edit the /etc/default/bluetooth file and set the following options:<br />
RFCOMM_ENABLE=true<br />
DUND_ENABLE=true<br />
DUND_OPTIONS="--listen --persist call dun"<br />
<br />
* Create an /etc/ppp/peers/dun file with options like the following:<br />
115200<br />
192.168.2.202:192.168.2.200<br />
passive<br />
local<br />
noipdefault<br />
noauth<br />
nodefaultroute<br />
<br />
* Restart bluetooth (/etc/init.d/bluetooth stop ; /etc/init.d/bluetooth start)<br />
<br />
To connect from a MacOS 10.3 client:<br />
<br />
* Open "Applications/Utilities/Bluetooth Serial Utility"<br />
<br />
* Click on "New"<br />
<br />
* Choose a name, then click "Choose Device"<br />
<br />
* Locate your Neo, then select the "LAN Access Point" service. If your device is not found, or if this service does not show up, then you will need to troubleshoot and fix that before continuing. Bluetooth is designed for short-range communication, so make sure that the devices are physically close to each other. <br />
<br />
* Select "Port type: RS-232" and "Show in Network Preferences". Click OK.<br />
<br />
* Open the Network Preferences page then "Show: Network Port Configurations". Enable the new device that you defined in the previous step and drag it to the bottom of the device list (so that it will not interfere with your other network connections)<br />
<br />
* Choose "Show: <your-device-name>", then click "Modem"<br />
<br />
* Select "Null Modem 115200" from the list of available devices. Uncheck "Wait for dial tone" and "Enable error correction and compression in modem". Optionally check "Show modem status in menu bar". <br />
<br />
* Click "Connect". If everything worked, you will end up with a 'ppp0' device on your Mac with a local address of 192.168.2.200 and you will be able to access your Neo at 192.168.2.202.<br />
<br />
===== Bluetooth networking with a Linux system - More secure way =====<br />
<br />
''Check this, probably needs some corrections''<br />
<br />
Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br />
<br />
On the laptop<br />
<br />
* check these options in /etc/bluetooth/hcid.conf<br />
security auto;<br />
passkey "your pin";<br />
lm master;<br />
<br />
* Start bluetooth<br />
# /etc/init.d/bluetooth start<br />
<br />
* Start pand as server<br />
pand --listen --role NAP --encrypt<br />
<br />
* Add in /etc/network/interfaces (see [[USB_Networking]])<br />
auto bnep0<br />
iface bnep0 inet static<br />
address 192.168.1.1<br />
netmask 255.255.255.0<br />
network 192.168.1.0<br />
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.1.0/24<br />
post-up echo 1 > /proc/sys/net/ipv4/ip_forward<br />
post-up iptables -P FORWARD ACCEPT<br />
<br />
On the Neo<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
00:20:E0:5A:FE:C8 laptop<br />
<br />
* Set pin<br />
root@fic-gta01:~$ passkey-agent 'your pin' 00:20:E0:5A:FE:C8 &<br />
<br />
* Connect to the laptop pand<br />
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br />
<br />
* Configure your IP address<br />
root@fic-gta01:~$ ifconfig bnep0 192.168.1.2<br />
root@fic-gta01:~$ route add default gateway 192.168.1.1<br />
<br />
* Enjoy<br />
<br />
==== Using Neo's connection from PC ====<br />
<br />
===== Calling Neo's GPRS modem via Bluetooth =====<br />
<br />
In this mode, Neo would behave like any other phone which can be used from a PC to get a network connection.<br />
<br />
This section not written yet. Has someone set it up?<br />
<br />
===== Sharing existing Neo's connection =====<br />
<br />
In this mode, Neo already has a network connection (GPRS, WLAN, ...), and it should get shared to the PC. This guide is general on how to forward network connection from a machine running Linux to another machine. If interested, please see more information for example at http://www.gentoo.org/doc/en/bluetooth-guide.xml.<br />
<br />
On the PC<br />
# Check with hciconfig you have working Bluetooth<br />
On the Neo<br />
(if on Debian etc., remember modprobe ohci_hcd hci_usb)<br />
# Initialize Bluetooth as told before:<br />
## echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br />
## echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
# install iptables: opkg install http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/iptables_1.3.8-r4.1_armv4t.ipk<br />
# modprobe bnep<br />
# Check that hcid is running both on Neo and PC (Bluetooth 4.x: install bluez-compat)<br />
# Use default passkey "1234" in /etc/bluetooth/hcid.conf<br />
# pand --listen --role NAP --master --autozap # note: after this you might have to the the step 1 below ("On the PC") or the next step of getting the interface up does not work # note2: you could automate pand listener to start automatically when Bluetooth is turned on<br />
# ifconfig bnep0 10.0.5.2 up<br />
# echo 1 > /proc/sys/net/ipv4/ip_forward<br />
# iptables -t nat -A POSTROUTING -j MASQUERADE -o ppp0<br />
On the PC:<br />
# sudo pand --connect <your bluetooth mac address> --service NAP --autozap<br />
# ifconfig bnep0 10.0.5.1 up<br />
# You can test the connection with ping 10.0.5.2<br />
# sudo ip route add default via 10.0.5.2 dev bnep0<br />
# [not automated yet] add GPRS connection's nameservers to /etc/resolv.conf<br />
<br />
== Advanced Audio Distribution Profile (A2DP) ==<br />
<br />
=== A2DP quickie ===<br />
<br />
* If you experience problems with choppyness, try changing your hcid.conf to include "lm accept,master;" and "lp hold,sniff,park;" You may also have to bond (commonly known as 'pairing') your phone and your headset. See http://wiki.bluez.org/wiki/HOWTO/Bonding for details. [[User:Mercury|Mercury]] 17:36, 5 September 2008 (UTC)<br />
<br />
It's now possible (if a little hackish) to stream mp3 to a bluetooth headset. It's a known problem that the playback rate changes (pitch varies). Timing issues are also likely the reason for gaps in playback.<br />
<br />
If the bluez packages are recent enough, you can use a shortcut. I'll document it here and leave the longer version below (the long version also demonstrates the API used by the GUI to manage headsets)<br />
<br />
Create /etc/asound.conf with your bluetooth headset's address filled in:<br />
<br />
pcm.!default {<br />
type bluetooth<br />
device "xx:xx:xx:xx:xx:xx"<br />
}<br />
<br />
then play a song<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay<br />
<br />
or for smoother results...<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:song.wav<br />
aplay song.wav<br />
<br />
=== A2DP ===<br />
<br />
If that doesn't work... all the more hackish... install required packages:<br />
<br />
echo "src/gz python http://www.angstrom-distribution.org/unstable/feed/armv4t/python/" >> /etc/ipkg/angstrom-python.conf <br />
echo "src/gz base http://www.angstrom-distribution.org/unstable/feed/armv4t/base/" >> /etc/ipkg/angstrom-base.conf<br />
ipkg update ; ipkg install python-core python-xml python-dbus bluez-utils bluez-utils-alsa<br />
<br />
Create /etc/asound.conf:<br />
<br />
pcm.!default {<br />
type bluetooth<br />
}<br />
ctl.!default {<br />
type bluetooth<br />
}<br />
pcm.bluetooth {<br />
type bluetooth<br />
}<br />
ctl.bluetooth {<br />
type bluetooth<br />
}<br />
<br />
Run the passkey agent (see above in this page)<br />
<br />
Fill in your bluetooth headset address below and execute the python script (with your headset turned on)<br />
<br />
#!/usr/bin/python<br />
import dbus<br />
bus = dbus.SystemBus()<br />
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')<br />
conn = manager.ActivateService('audio')<br />
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')<br />
path = audio.CreateDevice('00:0D:3C:44:33:22')<br />
audio.ChangeDefaultDevice(path)<br />
sink = dbus.Interface(bus.get_object(conn, path), 'org.bluez.audio.Sink')<br />
sink.Connect()<br />
<br />
FINALLY: play a song<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay<br />
<br />
=== Headset Audio ===<br />
<br />
[[Neo1973_Audio_Subsystem]] has detail about alsa settings and a proposal for audio scenario management.<br />
<br />
To try this out, follow the instructions in the a2dp section to install software and run the passkey agent.<br />
<br />
Remove or disable the stuff you put in asound.conf. When using a voice headset, the application uses the regular system audio device and it gets routed to bluetooth in the codec.<br />
<br />
Put the headset in pairing mode. Replace the bluetooth address below with your headset's and run the python script:<br />
<br />
#!/usr/bin/python<br />
import dbus<br />
bus = dbus.SystemBus()<br />
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')<br />
conn = manager.ActivateService('audio')<br />
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')<br />
path = audio.CreateHeadset('00:0B:2E:39:33:22')<br />
audio.ChangeDefaultHeadset(path)<br />
headset = dbus.Interface (bus.get_object(conn, path), 'org.bluez.audio.Headset')<br />
headset.Connect()<br />
headset.Play()<br />
<br />
Now place a call and try to route it to bluetooth (after it's in progress):<br />
<br />
alsactl -f /etc/gsmbluetooth.state restore<br />
<br />
You may also be able to listen to system audio given the right state file:<br />
<br />
alsactl -f /etc/systembluetooth.state restore<br />
madplay song.mp3<br />
<br />
==Bluetooth Headset on Freerunner ==<br />
<br />
[http://lists.openmoko.org/pipermail/support/2008-September/thread.html#2627 This thread] suggests the following:<br />
<br />
:Turn on bluetooth. If some of the scripts below fail you may need to reboot [https://docs.openmoko.org/trac/ticket/1744 Bluetooth after suspend]<br />
<br />
:Pair your headset according to [http://wiki.bluez.org/ these] instructions or use the script below. The script will change your .asoundrc so make a backup before you run it.<br />
<br />
:http://handheldshell.com/BtConfigure.py<br />
:Put the headset in pairing mode ( this only needs to be done once for each new headset ) and run<br />
BtConfigure.py <br />
<br />
:Download the the following python scripts to set up the audio service and set the headset as the default device:<br />
<br />
:http://handheldshell.com/BtHeadset.py<br />
:http://handheldshell.com/passkey.py<br />
:http://handheldshell.com/BtHeadsetDisconnect.py<br />
:http://handheldshell.com/python-pyalsaaudio_0.3-ml0_armv4t.ipk - can someone add python-pyalsa to the feeds ?<br />
<br />
:Download the the following python scripts if you prefer not to mess around with alsactl:<br />
<br />
:http://handheldshell.com/pymixer.py<br />
:http://handheldshell.com/volume.desktop<br />
<br />
:put pymixer in /usr/bin<br />
<br />
chmod u+x /usr/bin/pymixer.py<br />
<br />
:put volume.desktop in /usr/share/applications<br />
<br />
:Get the [[http://handheldshell.com/gsm_headset.txt alsa state file]] - this state file _WORKS_, mic and earphones are properly routed<br />
<br />
cp gsm_headset.txt /usr/share/openmoko/scenarios/btheadset.state<br />
<br />
:from the home screen run Volume<br />
<br />
:from the terminal run<br />
<br />
BtHeadset.py <br />
<br />
:Wait until it says waiting for call to end, you should hear static in the headset. If you don't something has gone wrong.<br />
<br />
:Now start the call<br />
<br />
:In the volume control switch to the btheadset tab. press restore<br />
<br />
:You should now hear the call in your headset. <br />
<br />
:End the call<br />
<br />
BtHeadsetDisconnect.py <br />
<br />
:This was all done with the 2008-updates image from sept 4. <br />
<br />
:The new scripts rely on a specific format for the .asoundrc . A stanza like this is required :<br />
<br />
pcm.headset {<br />
type bluetooth<br />
device <headset mac><br />
profile "voice"<br />
}<br />
<br />
== Further reading ==<br />
<br />
http://www.holtmann.org/papers/bluetooth/ols2006_slides.pdf<br />
http://wiki.bluez.org/wiki/Audio#org.bluez.Audio<br />
http://www.gentoo.org/doc/en/bluetooth-guide.xml<br />
<br />
{{Languages|Manually_using_Bluetooth}}<br />
<br />
[[Category:Bluetooth| ]]<br />
[[Category:Networking]]<br />
[[Category:Application Developer]]</div>Erinhttp://wiki.openmoko.org/wiki/Manually_using_BluetoothManually using Bluetooth2008-12-02T08:40:00Z<p>Erin: /* OBEX */</p>
<hr />
<div>{{InProgress}}<br />
Bluetooth is one of the core functions of the Neo1973, however it is basically unimplemented on the software side at the moment.<br />
Hardware problems in the P1 phone mean that the CPU has to be active in order to wake on external bluetooth events, which will reduce the battery life to some 2 days at best in standby.<br />
<br />
This page details how to use bluetooth from the command line.<br />
We have quite a lot of plans about what exactly Bluetooth should be used for.<br />
<br />
== Power it up ==<br />
<br />
Power up the adapter by clicking on the bluetooth icon in the top bar and selecting power on.<br />
<br />
The old way to do it is a shell command (for kernels before 2.6.24):<br />
<br />
root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on<br />
<br />
For kernel 2.6.24 (or later) use<br />
<br />
root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br />
<br />
and on the GTA02 *only* (i.e. not on the GTA01) also use<br />
<br />
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
<br />
But nowadays[http://permalink.gmane.org/gmane.comp.hardware.smartphones.userland/165], one should use [[Dbus device API]]s!<br />
<br />
At the shell, "hciconfig" should print information about the adapter if it powered up properly:<br />
<br />
hciconfig<br />
<br />
The devices should show as UP. If not you can use<br />
<br />
hciconfig <device> up<br />
<br />
== Bluetooth Functions ==<br />
<br />
===Configuring Bluetooth on Openmoko 2007.2 (August 27 snapshot with kernel 2.6.21.6-moko11) ===<br />
<br />
In file /etc/bluetooth/hcid.conf you should change the passkey from BlueZ to something numeric. For testing you may use "0000". Also, you can set the name to "Neo (%d)".<br />
<br />
=== Scanning for bluetooth devices ===<br />
<br />
hcitool scan<br />
<br />
This will list the addresses of any discoverable bluetooth devices in the vicinity<br />
<br />
=== passkey agent example ===<br />
<br />
There should be a passkey agent built into openmoko, but for now you can start up the example passkey agent and set the pin code there. This will allow for new pairings to be made when you attempt a connection.<br />
<br />
passkey-agent --default 0000 &<br />
<br />
Note: the passkey-agent is not required in Openmoko 2007.2 with kernel 2.6.21.6 as of at least since August 27 (maybe earlier).<br />
<br />
=== HID (Human Input Device) ===<br />
<br />
==== Being able to use HID devices ====<br />
<br />
Using a bluetooth keyboard with the built-in terminal is a little funky... I can only type into the console using the bt keyboard if the onscreen keyboard is visible. Also, pressing "p" twice on the bt keyboard actually gives you a "q".<br />
<br />
We want to be able to use a bluetooth keyboard to type into the various applications of our Neo1973.<br />
To use a Bluetooth Keyboard type: (11:22:33:44:55:66 is the Address of your BT-Keyboard)<br />
<br />
hidd --connect 11:22:33:44:55:66<br />
<br />
and press "Connect" on your BT-KB. Alternately, if you know that only one BT-Keyboard is within range, you can just:<br />
<br />
hidd --search<br />
<br />
to find and connect to any BT-Keyboard. There are some bluetooth keyboard only support SPP profile can't direct using hidd comannd to connect. Please reference the discussion of this page for more information.<br />
<br />
Tested on:<br />
* [http://www.logitech.com/index.cfm/products/details/US/EN,CRID=2166,CONTENTID=10717 Logitech Dinovo Edge]<br />
* [http://www.logitech.com/index.cfm/keyboards/keyboard_mice_combos/devices/164&cl=us,en Logitech Dinovo Media Desktop (keyboard)]<br />
* [http://www.nokia.es/A4181580 Nokia SU-8W]. Switched on the BT keyboard, scanned for BT address and ran the connect statement above. Works fine.<br />
* [http://blog.russnelson.com/chordite Chordite]. This keyboard uses the Broadcom BCM2042 BT keyboard controller along with a custom driver.<br />
* [http://www.apple.com/keyboard/ Apple's Aluminum Keyboard]. You may have to add 'auth enable; encrypt enable;' to device {} in hcid.conf. Run the passkey agent the first time. --search works to pair and every time after. (Might be obvious for those who have used BT in other spots, but you have to type in y our passkey on the keyboard as the connect is happening, otherwise pairing doesn't take place. I don't think there is a prompt on the Neo for this)<br />
* [http://www.apple.com/support/keyboard/ Apple's white "Wireless Keyboard (original)"] - details may be the same as above. (tested some time ago)<br />
* [http://www.frogpad.com/ FrogPad] - as above<br />
* [http://freedominput.com The freedom keyboard] and its many rebranded models (they look like this: [http://rabenfrost.net/openmoko/keyboard.jpg]) need 'modprobe uinput' to circumvent the 'Can't open input device: No such file or directory (2)' error of 'hidd --search'. It works as of february 7th 2008.<br />
* [http://www.nextag.com/Playstation-3-Logitech-Cordless-564345667/prices-html?nxtg=f8320a24052a-7789F8FE732FF6E3 Logitech Playstation 3 Keyboard] Works well, Mouse pad works.<br />
* [http://corporate.igo.com/product_details.aspx?id=16 iGo Stowaway UltraSlim] (which was apparently discontinued early 2008, but can still be bought in some places) ([[user:ChristW]] I have 2008.8 on it, and using hidd --search to connect to the iGo works perfectly. I also used it to edit a new contact, dial a number and edit a settings text box in [[TangoGPS]]. So far, no problems...)<br />
* [http://www.vkb-support.com/ I-Tech Virtual Laser Keyboard] works. Cursor keys not recognized as such, but produce keycodes than can be mapped.<br />
<br />
==== Acting as HID device ====<br />
<br />
We want to be able to use the Neo as a HID device, being able to use it as controller for presentations. See [[ReMoko]]<br />
<br />
=== RFCOMM ===<br />
<br />
Here's how to connect to an external Bluetooth GPS and read NMEA data (Tested with a Holux GPSSlim236 and a Nokia LD-3W ).<br />
<br />
First, switch on the GPS and identify the BT address:<br />
<br />
hcitool scan<br />
<br />
Then, edit /etc/bluetooth/rfcomm.conf, which by default has all settings commented out, to something like this:<br />
<br />
rfcomm0 {<br />
# Automatically bind the device at startup<br />
bind no;<br />
# Bluetooth address of the device<br />
device 00:11:22:33:44:55;<br />
# RFCOMM channel for the connection (check your GPS docs for details)<br />
channel 1;<br />
# Description of the connection<br />
comment "Bluetooth GPS";<br />
}<br />
<br />
Restart the BT services:<br />
<br />
root@neo:~$ /etc/init.d/bluetooth stop<br />
root@neo:~$ /etc/init.d/bluetooth start<br />
<br />
You should now be able to bind the GPS to /dev/rfcomm0, like this:<br />
<br />
root@neo:~$ rfcomm bind 0<br />
<br />
Confirm the connect:<br />
<br />
root@neo:~$ rfcomm<br />
rfcomm0: 00:11:22:33:44:55 channel 1 clean <br />
<br />
... and watch the NMEA strings coming from your GPS:<br />
<br />
root@neo:~$ cat /dev/rfcomm0 <br />
$GPGGA,111748.000,5907.6964,N,01121.1787,E,1,06,1.2,57.7,M,40.1,M,,0000*6F<br />
$GPRMC,111748.000,A,5907.6964,N,01121.1787,E,0.00,94.94,160807,,,A*50<br />
$GPVTG,94.94,T,,M,0.00,N,0.0,K,A*3D<br />
<br />
If you have nothing better to do, you can now pinpoint my office :-).<br />
<br />
=== OBEX ===<br />
OBEX (abbreviation of OBject EXchange, also termed IrOBEX) is a communications protocol that facilitates the exchange of binary objects between devices. Here is the notes about how to use OBEX to send/receive files via bluetooth in NEO.<br />
<br />
power on bluetooth: <br />
if you use FSO image<br />
root@om-gta02:~# dbus-send --system --dest=org.freesmartphone.odeviced --type=method_call --print-reply <br />
/org/freesmartphone/Device/PowerControl/Bluetooth org.freesmartphone.Device.PowerControl.SetPower int32:1<br />
else: (GTA02 only)<br />
root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
<br />
[http://linux.die.net/man/5/hcid.conf hcid.conf] <br />
modify /etc/bluetooth/hcid.conf<br />
<br />
<pre><br />
#<br />
# HCI daemon configuration file.<br />
#<br />
<br />
# HCId options<br />
options {<br />
# Automatically initialize new devices<br />
autoinit yes;<br />
<br />
# Security Manager mode<br />
# none - Security manager disabled<br />
# auto - Use local PIN for incoming connections<br />
# user - Always ask user for a PIN<br />
#<br />
security auto;<br />
<br />
# Pairing mode<br />
# none - Pairing disabled<br />
# multi - Allow pairing with already paired devices<br />
# once - Pair once and deny successive attempts<br />
pairing multi;<br />
<br />
# Default PIN code for incoming connections<br />
passkey "1234";<br />
}<br />
<br />
# Default settings for HCI devices<br />
device {<br />
# Local device name<br />
# %d - device id<br />
# %h - host name<br />
name "%h-%d";<br />
<br />
# Local device class<br />
class 0x000100;<br />
<br />
# Default packet type<br />
pkt_type DH1,DM1,HV1;<br />
<br />
# Inquiry and Page scan<br />
iscan enable; pscan enable;<br />
<br />
# Default link mode<br />
# none - no specific policy <br />
# accept - always accept incoming connections<br />
# master - become master on incoming connections,<br />
# deny role switch on outgoing connections<br />
lm accept;<br />
<br />
# Default link policy<br />
# none - no specific policy<br />
# rswitch - allow role switch<br />
# hold - allow hold mode<br />
# sniff - allow sniff mode<br />
# park - allow park mode<br />
lp rswitch,hold,sniff,park;<br />
}<br />
</pre><br />
<br />
[http://linux.die.net/man/8/hcid hcid] - Bluetooth Host Controller Interface Daemon <br />
<br />
All paired devices information are stored in /var/lib/bluetooth/BT HW addr folder <br />
eg. <br />
<pre><br />
root@om-gta02:/var/lib/bluetooth/00:06:6E:16:EB:C7# ls<br />
classes features lastused names panu<br />
config gn manufacturers nap<br />
</pre><br />
<br />
Display local devices<br />
root@om-gta02:/# hcitool dev<br />
<br />
Scan all nearby bluetooth devices<br />
root@om-gta02:~# hcitool scan<br />
<br />
Browse what kind of services in this device<br />
root@om-gta02:~# sdptool browse 00:18:C5:42:18:78<br />
<br />
<pre><br />
Browsing 00:18:C5:42:18:78 ...<br />
<br />
Service Name: OBEX File Transfer<br />
Service RecHandle: 0x1005b<br />
Service Class ID List:<br />
"OBEX File Transfer" (0x1106)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 11<br />
"OBEX" (0x0008)<br />
Language Base Attr List:<br />
code_ISO639: 0x454e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"OBEX File Transfer" (0x1106)<br />
Version: 0x0100<br />
<br />
Service Name: OBEX Object Push<br />
Service RecHandle: 0x1005e<br />
Service Class ID List:<br />
"OBEX Object Push" (0x1105)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 9<br />
"OBEX" (0x0008)<br />
Language Base Attr List:<br />
code_ISO639: 0x454e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"OBEX Object Push" (0x1105)<br />
Version: 0x0100<br />
<br />
</pre><br />
<br />
Use obexpush and obexftp tools<br />
<br />
install obexpush, obexftp packages<br />
opkg install obexpush, [http://www.go2linux.org/linux-command-line-obexftp-man-page obexftp]<br />
<br />
obexpush would launch 'opd' and it's a obex data server. It starts OBEX file transfer service. The default folder is \home\root and it would store all received files here. <br />
<br />
<pre><br />
root@om-gta02:~# ps aux | grep opd<br />
root 1322 0.0 0.4 1972 604 ? Ss 16:21 0:00 opd: waiting for incomming OBEX connections on channel 10...<br />
</pre> <br />
<br />
How to pair with a bluetooth device, check [http://wiki.bluez.org/wiki/bluez bluez wiki]<br />
<br />
=== Networking ===<br />
<br />
==== Using PC's connection from Neo ====<br />
<br />
===== Bluetooth networking with a Linux system =====<br />
<br />
Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br />
<br />
'''On the laptop'''<br />
<br />
* Start bluetooth<br />
/etc/init.d/bluetooth start<br />
<br />
* Start pand as server<br />
pand -s<br />
<br />
* As soon as pand is started on the phone configure your IP address<br />
ip a add 10.0.0.1/24 dev bnep0<br />
ip l set bnep0 up<br />
<br />
* Configure IP forwarding and masquerading to your liking (see [[USB_Networking]]). You can even set up Udev rules to do this for you once the bnep0 interface appears.<br />
<br />
<br />
'''On the Neo'''<br />
<br />
* There is a little script that does the steps below (and retries the pand -c command; I had issues with it not working the first time every time) at [[Bt-net-script]] You shouldn't need the other steps below if you use the script.<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
00:0E:6D:C0:0l:6A Sho<br />
00:20:E0:5A:FE:C8 BlueZ (0)<br />
<br />
* Connect to the laptop pand<br />
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br />
<br />
* Configure your IP address<br />
ip a add 10.0.0.2/24 dev bnep0<br />
ip r add default via 10.0.0.1<br />
<br />
* Sometimes you may need to bring up the bnep0 on the phone as well:<br />
ip l set bnep0 up<br />
* Enjoy<br />
<br />
<br />
*--[[User:Mantis|Mantis]] 18:37, 15 October 2008 (UTC) Note for use on OpenSuse 11.0 - I was getting a connection failure with 'Host is down(112)' errors in /var/log/messages (on neo).<br />
I found that editing /etc/bluetooth/hcid.conf to set 'pscan enable' instead of 'pscan disable' and making passkey consistent with Neo Freerunner made it work.<br />
<br />
Should see log line like<br />
''pand[17965]: New connection from 00:06:6E:XX:XX:XX at bnep0''<br />
<br />
if connection is successful in server's /var/log/messages.<br />
<br />
===== Bluetooth networking with a MacOS X system =====<br />
<br />
Please refer to [[MacOS_X#Bluetooth_2]]<br />
<br />
For using the Neo as a dialup Bluetooth server and the Mac as the client, please see below at [[Manually_using_Bluetooth#PPP_Networking]]<br />
<br />
===== Bluetooth networking with a Windows XP system =====<br />
<br />
This was tested with a Windows XP SP2 on a IBM Thinkpad T41 with the Widcomm BT stack<br />
<br />
* Start bluetooth on Windows XP<br />
<br />
* Enable "Network Access" in the Bluetooth configuration<br />
<br />
* Scan for the Neo and pair with the Neo (right click, select pair)<br />
<br />
<br />
On the Neo<br />
<br />
* Enable PAN support on the Neo by changing Autostart from false to true in /etc/bluetooth/network.service<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
<laptop_bt_address> Thinkpad<br />
...<br />
<br />
<br />
* Connect to the laptop pand<br />
pand -c <laptop_bt_address> -r PANU -d NAP -e bnep0 -A -E -S<br />
(add '-n' to see the pand status messages until you get it right)<br />
<br />
For some reason, I was not able to initiate PAN connections from the Neo, I got 'Permission denied (13)' even when I had explicitly allowed the Neo to connect (right click on Neo icon, set properties, on Authorization tab). But initiating 'PAN User' from Windows worked when executing on Neo:<br />
pand -l -r PANU -d NAP -e bnep0 -A -E -S<br />
(add '-n' to see the pand status messages until you get it right)<br />
<br />
<br />
* Configure your IP address. It should work like when connecting to Linux:<br />
ip a add 10.0.0.2/24 dev bnep0<br />
ip r add default via 10.0.0.1<br />
If this does not work, the IP stacks may have auto-assigned network addresses to themselves. You can look this up with 'ifconfig' on the Neo and with 'ipconfig' on Windows.<br />
<br />
<br />
* You should now be able to ssh/putty from Windows to your Neo. Enjoy!<br />
By setting up the Windows Bluetooth connection properly, it should also be possible to share the Internet Connection of the Windows box with the Neo.<br />
<br />
===== PPP Networking =====<br />
<br />
If you are unable to use the 'BNEP' method described above, you may be able to use [[PPP]] and a DUN (dialup-networking) emulation mode. On the Neo:<br />
<br />
* Edit the /etc/default/bluetooth file and set the following options:<br />
RFCOMM_ENABLE=true<br />
DUND_ENABLE=true<br />
DUND_OPTIONS="--listen --persist call dun"<br />
<br />
* Create an /etc/ppp/peers/dun file with options like the following:<br />
115200<br />
192.168.2.202:192.168.2.200<br />
passive<br />
local<br />
noipdefault<br />
noauth<br />
nodefaultroute<br />
<br />
* Restart bluetooth (/etc/init.d/bluetooth stop ; /etc/init.d/bluetooth start)<br />
<br />
To connect from a MacOS 10.3 client:<br />
<br />
* Open "Applications/Utilities/Bluetooth Serial Utility"<br />
<br />
* Click on "New"<br />
<br />
* Choose a name, then click "Choose Device"<br />
<br />
* Locate your Neo, then select the "LAN Access Point" service. If your device is not found, or if this service does not show up, then you will need to troubleshoot and fix that before continuing. Bluetooth is designed for short-range communication, so make sure that the devices are physically close to each other. <br />
<br />
* Select "Port type: RS-232" and "Show in Network Preferences". Click OK.<br />
<br />
* Open the Network Preferences page then "Show: Network Port Configurations". Enable the new device that you defined in the previous step and drag it to the bottom of the device list (so that it will not interfere with your other network connections)<br />
<br />
* Choose "Show: <your-device-name>", then click "Modem"<br />
<br />
* Select "Null Modem 115200" from the list of available devices. Uncheck "Wait for dial tone" and "Enable error correction and compression in modem". Optionally check "Show modem status in menu bar". <br />
<br />
* Click "Connect". If everything worked, you will end up with a 'ppp0' device on your Mac with a local address of 192.168.2.200 and you will be able to access your Neo at 192.168.2.202.<br />
<br />
===== Bluetooth networking with a Linux system - More secure way =====<br />
<br />
''Check this, probably needs some corrections''<br />
<br />
Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br />
<br />
On the laptop<br />
<br />
* check these options in /etc/bluetooth/hcid.conf<br />
security auto;<br />
passkey "your pin";<br />
lm master;<br />
<br />
* Start bluetooth<br />
# /etc/init.d/bluetooth start<br />
<br />
* Start pand as server<br />
pand --listen --role NAP --encrypt<br />
<br />
* Add in /etc/network/interfaces (see [[USB_Networking]])<br />
auto bnep0<br />
iface bnep0 inet static<br />
address 192.168.1.1<br />
netmask 255.255.255.0<br />
network 192.168.1.0<br />
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.1.0/24<br />
post-up echo 1 > /proc/sys/net/ipv4/ip_forward<br />
post-up iptables -P FORWARD ACCEPT<br />
<br />
On the Neo<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
00:20:E0:5A:FE:C8 laptop<br />
<br />
* Set pin<br />
root@fic-gta01:~$ passkey-agent 'your pin' 00:20:E0:5A:FE:C8 &<br />
<br />
* Connect to the laptop pand<br />
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br />
<br />
* Configure your IP address<br />
root@fic-gta01:~$ ifconfig bnep0 192.168.1.2<br />
root@fic-gta01:~$ route add default gateway 192.168.1.1<br />
<br />
* Enjoy<br />
<br />
==== Using Neo's connection from PC ====<br />
<br />
===== Calling Neo's GPRS modem via Bluetooth =====<br />
<br />
In this mode, Neo would behave like any other phone which can be used from a PC to get a network connection.<br />
<br />
This section not written yet. Has someone set it up?<br />
<br />
===== Sharing existing Neo's connection =====<br />
<br />
In this mode, Neo already has a network connection (GPRS, WLAN, ...), and it should get shared to the PC. This guide is general on how to forward network connection from a machine running Linux to another machine. If interested, please see more information for example at http://www.gentoo.org/doc/en/bluetooth-guide.xml.<br />
<br />
On the PC<br />
# Check with hciconfig you have working Bluetooth<br />
On the Neo<br />
(if on Debian etc., remember modprobe ohci_hcd hci_usb)<br />
# Initialize Bluetooth as told before:<br />
## echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br />
## echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
# install iptables: opkg install http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/iptables_1.3.8-r4.1_armv4t.ipk<br />
# modprobe bnep<br />
# Check that hcid is running both on Neo and PC (Bluetooth 4.x: install bluez-compat)<br />
# Use default passkey "1234" in /etc/bluetooth/hcid.conf<br />
# pand --listen --role NAP --master --autozap # note: after this you might have to the the step 1 below ("On the PC") or the next step of getting the interface up does not work # note2: you could automate pand listener to start automatically when Bluetooth is turned on<br />
# ifconfig bnep0 10.0.5.2 up<br />
# echo 1 > /proc/sys/net/ipv4/ip_forward<br />
# iptables -t nat -A POSTROUTING -j MASQUERADE -o ppp0<br />
On the PC:<br />
# sudo pand --connect <your bluetooth mac address> --service NAP --autozap<br />
# ifconfig bnep0 10.0.5.1 up<br />
# You can test the connection with ping 10.0.5.2<br />
# sudo ip route add default via 10.0.5.2 dev bnep0<br />
# [not automated yet] add GPRS connection's nameservers to /etc/resolv.conf<br />
<br />
== Advanced Audio Distribution Profile (A2DP) ==<br />
<br />
=== A2DP quickie ===<br />
<br />
* If you experience problems with choppyness, try changing your hcid.conf to include "lm accept,master;" and "lp hold,sniff,park;" You may also have to bond (commonly known as 'pairing') your phone and your headset. See http://wiki.bluez.org/wiki/HOWTO/Bonding for details. [[User:Mercury|Mercury]] 17:36, 5 September 2008 (UTC)<br />
<br />
It's now possible (if a little hackish) to stream mp3 to a bluetooth headset. It's a known problem that the playback rate changes (pitch varies). Timing issues are also likely the reason for gaps in playback.<br />
<br />
If the bluez packages are recent enough, you can use a shortcut. I'll document it here and leave the longer version below (the long version also demonstrates the API used by the GUI to manage headsets)<br />
<br />
Create /etc/asound.conf with your bluetooth headset's address filled in:<br />
<br />
pcm.!default {<br />
type bluetooth<br />
device "xx:xx:xx:xx:xx:xx"<br />
}<br />
<br />
then play a song<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay<br />
<br />
or for smoother results...<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:song.wav<br />
aplay song.wav<br />
<br />
=== A2DP ===<br />
<br />
If that doesn't work... all the more hackish... install required packages:<br />
<br />
echo "src/gz python http://www.angstrom-distribution.org/unstable/feed/armv4t/python/" >> /etc/ipkg/angstrom-python.conf <br />
echo "src/gz base http://www.angstrom-distribution.org/unstable/feed/armv4t/base/" >> /etc/ipkg/angstrom-base.conf<br />
ipkg update ; ipkg install python-core python-xml python-dbus bluez-utils bluez-utils-alsa<br />
<br />
Create /etc/asound.conf:<br />
<br />
pcm.!default {<br />
type bluetooth<br />
}<br />
ctl.!default {<br />
type bluetooth<br />
}<br />
pcm.bluetooth {<br />
type bluetooth<br />
}<br />
ctl.bluetooth {<br />
type bluetooth<br />
}<br />
<br />
Run the passkey agent (see above in this page)<br />
<br />
Fill in your bluetooth headset address below and execute the python script (with your headset turned on)<br />
<br />
#!/usr/bin/python<br />
import dbus<br />
bus = dbus.SystemBus()<br />
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')<br />
conn = manager.ActivateService('audio')<br />
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')<br />
path = audio.CreateDevice('00:0D:3C:44:33:22')<br />
audio.ChangeDefaultDevice(path)<br />
sink = dbus.Interface(bus.get_object(conn, path), 'org.bluez.audio.Sink')<br />
sink.Connect()<br />
<br />
FINALLY: play a song<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay<br />
<br />
=== Headset Audio ===<br />
<br />
[[Neo1973_Audio_Subsystem]] has detail about alsa settings and a proposal for audio scenario management.<br />
<br />
To try this out, follow the instructions in the a2dp section to install software and run the passkey agent.<br />
<br />
Remove or disable the stuff you put in asound.conf. When using a voice headset, the application uses the regular system audio device and it gets routed to bluetooth in the codec.<br />
<br />
Put the headset in pairing mode. Replace the bluetooth address below with your headset's and run the python script:<br />
<br />
#!/usr/bin/python<br />
import dbus<br />
bus = dbus.SystemBus()<br />
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')<br />
conn = manager.ActivateService('audio')<br />
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')<br />
path = audio.CreateHeadset('00:0B:2E:39:33:22')<br />
audio.ChangeDefaultHeadset(path)<br />
headset = dbus.Interface (bus.get_object(conn, path), 'org.bluez.audio.Headset')<br />
headset.Connect()<br />
headset.Play()<br />
<br />
Now place a call and try to route it to bluetooth (after it's in progress):<br />
<br />
alsactl -f /etc/gsmbluetooth.state restore<br />
<br />
You may also be able to listen to system audio given the right state file:<br />
<br />
alsactl -f /etc/systembluetooth.state restore<br />
madplay song.mp3<br />
<br />
==Bluetooth Headset on Freerunner ==<br />
<br />
[http://lists.openmoko.org/pipermail/support/2008-September/thread.html#2627 This thread] suggests the following:<br />
<br />
:Turn on bluetooth. If some of the scripts below fail you may need to reboot [https://docs.openmoko.org/trac/ticket/1744 Bluetooth after suspend]<br />
<br />
:Pair your headset according to [http://wiki.bluez.org/ these] instructions or use the script below. The script will change your .asoundrc so make a backup before you run it.<br />
<br />
:http://handheldshell.com/BtConfigure.py<br />
:Put the headset in pairing mode ( this only needs to be done once for each new headset ) and run<br />
BtConfigure.py <br />
<br />
:Download the the following python scripts to set up the audio service and set the headset as the default device:<br />
<br />
:http://handheldshell.com/BtHeadset.py<br />
:http://handheldshell.com/passkey.py<br />
:http://handheldshell.com/BtHeadsetDisconnect.py<br />
:http://handheldshell.com/python-pyalsaaudio_0.3-ml0_armv4t.ipk - can someone add python-pyalsa to the feeds ?<br />
<br />
:Download the the following python scripts if you prefer not to mess around with alsactl:<br />
<br />
:http://handheldshell.com/pymixer.py<br />
:http://handheldshell.com/volume.desktop<br />
<br />
:put pymixer in /usr/bin<br />
<br />
chmod u+x /usr/bin/pymixer.py<br />
<br />
:put volume.desktop in /usr/share/applications<br />
<br />
:Get the [[http://handheldshell.com/gsm_headset.txt alsa state file]] - this state file _WORKS_, mic and earphones are properly routed<br />
<br />
cp gsm_headset.txt /usr/share/openmoko/scenarios/btheadset.state<br />
<br />
:from the home screen run Volume<br />
<br />
:from the terminal run<br />
<br />
BtHeadset.py <br />
<br />
:Wait until it says waiting for call to end, you should hear static in the headset. If you don't something has gone wrong.<br />
<br />
:Now start the call<br />
<br />
:In the volume control switch to the btheadset tab. press restore<br />
<br />
:You should now hear the call in your headset. <br />
<br />
:End the call<br />
<br />
BtHeadsetDisconnect.py <br />
<br />
:This was all done with the 2008-updates image from sept 4. <br />
<br />
:The new scripts rely on a specific format for the .asoundrc . A stanza like this is required :<br />
<br />
pcm.headset {<br />
type bluetooth<br />
device <headset mac><br />
profile "voice"<br />
}<br />
<br />
== Further reading ==<br />
<br />
http://www.holtmann.org/papers/bluetooth/ols2006_slides.pdf<br />
http://wiki.bluez.org/wiki/Audio#org.bluez.Audio<br />
http://www.gentoo.org/doc/en/bluetooth-guide.xml<br />
<br />
{{Languages|Manually_using_Bluetooth}}<br />
<br />
[[Category:Bluetooth| ]]<br />
[[Category:Networking]]<br />
[[Category:Application Developer]]</div>Erinhttp://wiki.openmoko.org/wiki/Manually_using_BluetoothManually using Bluetooth2008-12-02T08:37:36Z<p>Erin: /* OBEX */</p>
<hr />
<div>{{InProgress}}<br />
Bluetooth is one of the core functions of the Neo1973, however it is basically unimplemented on the software side at the moment.<br />
Hardware problems in the P1 phone mean that the CPU has to be active in order to wake on external bluetooth events, which will reduce the battery life to some 2 days at best in standby.<br />
<br />
This page details how to use bluetooth from the command line.<br />
We have quite a lot of plans about what exactly Bluetooth should be used for.<br />
<br />
== Power it up ==<br />
<br />
Power up the adapter by clicking on the bluetooth icon in the top bar and selecting power on.<br />
<br />
The old way to do it is a shell command (for kernels before 2.6.24):<br />
<br />
root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on<br />
<br />
For kernel 2.6.24 (or later) use<br />
<br />
root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br />
<br />
and on the GTA02 *only* (i.e. not on the GTA01) also use<br />
<br />
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
<br />
But nowadays[http://permalink.gmane.org/gmane.comp.hardware.smartphones.userland/165], one should use [[Dbus device API]]s!<br />
<br />
At the shell, "hciconfig" should print information about the adapter if it powered up properly:<br />
<br />
hciconfig<br />
<br />
The devices should show as UP. If not you can use<br />
<br />
hciconfig <device> up<br />
<br />
== Bluetooth Functions ==<br />
<br />
===Configuring Bluetooth on Openmoko 2007.2 (August 27 snapshot with kernel 2.6.21.6-moko11) ===<br />
<br />
In file /etc/bluetooth/hcid.conf you should change the passkey from BlueZ to something numeric. For testing you may use "0000". Also, you can set the name to "Neo (%d)".<br />
<br />
=== Scanning for bluetooth devices ===<br />
<br />
hcitool scan<br />
<br />
This will list the addresses of any discoverable bluetooth devices in the vicinity<br />
<br />
=== passkey agent example ===<br />
<br />
There should be a passkey agent built into openmoko, but for now you can start up the example passkey agent and set the pin code there. This will allow for new pairings to be made when you attempt a connection.<br />
<br />
passkey-agent --default 0000 &<br />
<br />
Note: the passkey-agent is not required in Openmoko 2007.2 with kernel 2.6.21.6 as of at least since August 27 (maybe earlier).<br />
<br />
=== HID (Human Input Device) ===<br />
<br />
==== Being able to use HID devices ====<br />
<br />
Using a bluetooth keyboard with the built-in terminal is a little funky... I can only type into the console using the bt keyboard if the onscreen keyboard is visible. Also, pressing "p" twice on the bt keyboard actually gives you a "q".<br />
<br />
We want to be able to use a bluetooth keyboard to type into the various applications of our Neo1973.<br />
To use a Bluetooth Keyboard type: (11:22:33:44:55:66 is the Address of your BT-Keyboard)<br />
<br />
hidd --connect 11:22:33:44:55:66<br />
<br />
and press "Connect" on your BT-KB. Alternately, if you know that only one BT-Keyboard is within range, you can just:<br />
<br />
hidd --search<br />
<br />
to find and connect to any BT-Keyboard. There are some bluetooth keyboard only support SPP profile can't direct using hidd comannd to connect. Please reference the discussion of this page for more information.<br />
<br />
Tested on:<br />
* [http://www.logitech.com/index.cfm/products/details/US/EN,CRID=2166,CONTENTID=10717 Logitech Dinovo Edge]<br />
* [http://www.logitech.com/index.cfm/keyboards/keyboard_mice_combos/devices/164&cl=us,en Logitech Dinovo Media Desktop (keyboard)]<br />
* [http://www.nokia.es/A4181580 Nokia SU-8W]. Switched on the BT keyboard, scanned for BT address and ran the connect statement above. Works fine.<br />
* [http://blog.russnelson.com/chordite Chordite]. This keyboard uses the Broadcom BCM2042 BT keyboard controller along with a custom driver.<br />
* [http://www.apple.com/keyboard/ Apple's Aluminum Keyboard]. You may have to add 'auth enable; encrypt enable;' to device {} in hcid.conf. Run the passkey agent the first time. --search works to pair and every time after. (Might be obvious for those who have used BT in other spots, but you have to type in y our passkey on the keyboard as the connect is happening, otherwise pairing doesn't take place. I don't think there is a prompt on the Neo for this)<br />
* [http://www.apple.com/support/keyboard/ Apple's white "Wireless Keyboard (original)"] - details may be the same as above. (tested some time ago)<br />
* [http://www.frogpad.com/ FrogPad] - as above<br />
* [http://freedominput.com The freedom keyboard] and its many rebranded models (they look like this: [http://rabenfrost.net/openmoko/keyboard.jpg]) need 'modprobe uinput' to circumvent the 'Can't open input device: No such file or directory (2)' error of 'hidd --search'. It works as of february 7th 2008.<br />
* [http://www.nextag.com/Playstation-3-Logitech-Cordless-564345667/prices-html?nxtg=f8320a24052a-7789F8FE732FF6E3 Logitech Playstation 3 Keyboard] Works well, Mouse pad works.<br />
* [http://corporate.igo.com/product_details.aspx?id=16 iGo Stowaway UltraSlim] (which was apparently discontinued early 2008, but can still be bought in some places) ([[user:ChristW]] I have 2008.8 on it, and using hidd --search to connect to the iGo works perfectly. I also used it to edit a new contact, dial a number and edit a settings text box in [[TangoGPS]]. So far, no problems...)<br />
* [http://www.vkb-support.com/ I-Tech Virtual Laser Keyboard] works. Cursor keys not recognized as such, but produce keycodes than can be mapped.<br />
<br />
==== Acting as HID device ====<br />
<br />
We want to be able to use the Neo as a HID device, being able to use it as controller for presentations. See [[ReMoko]]<br />
<br />
=== RFCOMM ===<br />
<br />
Here's how to connect to an external Bluetooth GPS and read NMEA data (Tested with a Holux GPSSlim236 and a Nokia LD-3W ).<br />
<br />
First, switch on the GPS and identify the BT address:<br />
<br />
hcitool scan<br />
<br />
Then, edit /etc/bluetooth/rfcomm.conf, which by default has all settings commented out, to something like this:<br />
<br />
rfcomm0 {<br />
# Automatically bind the device at startup<br />
bind no;<br />
# Bluetooth address of the device<br />
device 00:11:22:33:44:55;<br />
# RFCOMM channel for the connection (check your GPS docs for details)<br />
channel 1;<br />
# Description of the connection<br />
comment "Bluetooth GPS";<br />
}<br />
<br />
Restart the BT services:<br />
<br />
root@neo:~$ /etc/init.d/bluetooth stop<br />
root@neo:~$ /etc/init.d/bluetooth start<br />
<br />
You should now be able to bind the GPS to /dev/rfcomm0, like this:<br />
<br />
root@neo:~$ rfcomm bind 0<br />
<br />
Confirm the connect:<br />
<br />
root@neo:~$ rfcomm<br />
rfcomm0: 00:11:22:33:44:55 channel 1 clean <br />
<br />
... and watch the NMEA strings coming from your GPS:<br />
<br />
root@neo:~$ cat /dev/rfcomm0 <br />
$GPGGA,111748.000,5907.6964,N,01121.1787,E,1,06,1.2,57.7,M,40.1,M,,0000*6F<br />
$GPRMC,111748.000,A,5907.6964,N,01121.1787,E,0.00,94.94,160807,,,A*50<br />
$GPVTG,94.94,T,,M,0.00,N,0.0,K,A*3D<br />
<br />
If you have nothing better to do, you can now pinpoint my office :-).<br />
<br />
=== OBEX ===<br />
OBEX (abbreviation of OBject EXchange, also termed IrOBEX) is a communications protocol that facilitates the exchange of binary objects between devices. Here is the notes about how to use OBEX to send/receive files via bluetooth in NEO.<br />
<br />
power on bluetooth: <br />
if you use FSO image<br />
root@om-gta02:~# dbus-send --system --dest=org.freesmartphone.odeviced --type=method_call --print-reply <br />
/org/freesmartphone/Device/PowerControl/Bluetooth org.freesmartphone.Device.PowerControl.SetPower int32:1<br />
else: (GTA02 only)<br />
root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
<br />
[http://linux.die.net/man/5/hcid.conf hcid.conf] <br />
modify /etc/bluetooth/hcid.conf<br />
<br />
<pre><br />
#<br />
# HCI daemon configuration file.<br />
#<br />
<br />
# HCId options<br />
options {<br />
# Automatically initialize new devices<br />
autoinit yes;<br />
<br />
# Security Manager mode<br />
# none - Security manager disabled<br />
# auto - Use local PIN for incoming connections<br />
# user - Always ask user for a PIN<br />
#<br />
security auto;<br />
<br />
# Pairing mode<br />
# none - Pairing disabled<br />
# multi - Allow pairing with already paired devices<br />
# once - Pair once and deny successive attempts<br />
pairing multi;<br />
<br />
# Default PIN code for incoming connections<br />
passkey "1234";<br />
}<br />
<br />
# Default settings for HCI devices<br />
device {<br />
# Local device name<br />
# %d - device id<br />
# %h - host name<br />
name "%h-%d";<br />
<br />
# Local device class<br />
class 0x000100;<br />
<br />
# Default packet type<br />
pkt_type DH1,DM1,HV1;<br />
<br />
# Inquiry and Page scan<br />
iscan enable; pscan enable;<br />
<br />
# Default link mode<br />
# none - no specific policy <br />
# accept - always accept incoming connections<br />
# master - become master on incoming connections,<br />
# deny role switch on outgoing connections<br />
lm accept;<br />
<br />
# Default link policy<br />
# none - no specific policy<br />
# rswitch - allow role switch<br />
# hold - allow hold mode<br />
# sniff - allow sniff mode<br />
# park - allow park mode<br />
lp rswitch,hold,sniff,park;<br />
}<br />
</pre><br />
<br />
[http://linux.die.net/man/8/hcid hcid] - Bluetooth Host Controller Interface Daemon <br />
<br />
All paired devices information are stored in /var/lib/bluetooth/BT HW addr folder <br />
eg. <br />
<pre><br />
root@om-gta02:/var/lib/bluetooth/00:06:6E:16:EB:C7# ls<br />
classes features lastused names panu<br />
config gn manufacturers nap<br />
</pre><br />
<br />
Display local devices<br />
root@om-gta02:/# hcitool dev<br />
<br />
Scan all nearby bluetooth devices<br />
root@om-gta02:~# hcitool scan<br />
<br />
Browse what kind of services in this device<br />
root@om-gta02:~# sdptool browse 00:18:C5:42:18:78<br />
<br />
<pre><br />
Browsing 00:18:C5:42:18:78 ...<br />
<br />
Service Name: OBEX File Transfer<br />
Service RecHandle: 0x1005b<br />
Service Class ID List:<br />
"OBEX File Transfer" (0x1106)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 11<br />
"OBEX" (0x0008)<br />
Language Base Attr List:<br />
code_ISO639: 0x454e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"OBEX File Transfer" (0x1106)<br />
Version: 0x0100<br />
<br />
Service Name: OBEX Object Push<br />
Service RecHandle: 0x1005e<br />
Service Class ID List:<br />
"OBEX Object Push" (0x1105)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 9<br />
"OBEX" (0x0008)<br />
Language Base Attr List:<br />
code_ISO639: 0x454e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"OBEX Object Push" (0x1105)<br />
Version: 0x0100<br />
<br />
</pre><br />
<br />
Use obexpush and obexftp tools<br />
<br />
install obexpush, obexftp packages<br />
opkg install obexpush, [http://www.go2linux.org/linux-command-line-obexftp-man-page obexftp]<br />
<br />
obexpush would launch 'opd' and it's a obex data server. The default folder is \home\root and it would store all received files here.<br />
<br />
How to pair with a bluetooth device, check [http://wiki.bluez.org/wiki/bluez wiki]<br />
<br />
=== Networking ===<br />
<br />
==== Using PC's connection from Neo ====<br />
<br />
===== Bluetooth networking with a Linux system =====<br />
<br />
Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br />
<br />
'''On the laptop'''<br />
<br />
* Start bluetooth<br />
/etc/init.d/bluetooth start<br />
<br />
* Start pand as server<br />
pand -s<br />
<br />
* As soon as pand is started on the phone configure your IP address<br />
ip a add 10.0.0.1/24 dev bnep0<br />
ip l set bnep0 up<br />
<br />
* Configure IP forwarding and masquerading to your liking (see [[USB_Networking]]). You can even set up Udev rules to do this for you once the bnep0 interface appears.<br />
<br />
<br />
'''On the Neo'''<br />
<br />
* There is a little script that does the steps below (and retries the pand -c command; I had issues with it not working the first time every time) at [[Bt-net-script]] You shouldn't need the other steps below if you use the script.<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
00:0E:6D:C0:0l:6A Sho<br />
00:20:E0:5A:FE:C8 BlueZ (0)<br />
<br />
* Connect to the laptop pand<br />
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br />
<br />
* Configure your IP address<br />
ip a add 10.0.0.2/24 dev bnep0<br />
ip r add default via 10.0.0.1<br />
<br />
* Sometimes you may need to bring up the bnep0 on the phone as well:<br />
ip l set bnep0 up<br />
* Enjoy<br />
<br />
<br />
*--[[User:Mantis|Mantis]] 18:37, 15 October 2008 (UTC) Note for use on OpenSuse 11.0 - I was getting a connection failure with 'Host is down(112)' errors in /var/log/messages (on neo).<br />
I found that editing /etc/bluetooth/hcid.conf to set 'pscan enable' instead of 'pscan disable' and making passkey consistent with Neo Freerunner made it work.<br />
<br />
Should see log line like<br />
''pand[17965]: New connection from 00:06:6E:XX:XX:XX at bnep0''<br />
<br />
if connection is successful in server's /var/log/messages.<br />
<br />
===== Bluetooth networking with a MacOS X system =====<br />
<br />
Please refer to [[MacOS_X#Bluetooth_2]]<br />
<br />
For using the Neo as a dialup Bluetooth server and the Mac as the client, please see below at [[Manually_using_Bluetooth#PPP_Networking]]<br />
<br />
===== Bluetooth networking with a Windows XP system =====<br />
<br />
This was tested with a Windows XP SP2 on a IBM Thinkpad T41 with the Widcomm BT stack<br />
<br />
* Start bluetooth on Windows XP<br />
<br />
* Enable "Network Access" in the Bluetooth configuration<br />
<br />
* Scan for the Neo and pair with the Neo (right click, select pair)<br />
<br />
<br />
On the Neo<br />
<br />
* Enable PAN support on the Neo by changing Autostart from false to true in /etc/bluetooth/network.service<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
<laptop_bt_address> Thinkpad<br />
...<br />
<br />
<br />
* Connect to the laptop pand<br />
pand -c <laptop_bt_address> -r PANU -d NAP -e bnep0 -A -E -S<br />
(add '-n' to see the pand status messages until you get it right)<br />
<br />
For some reason, I was not able to initiate PAN connections from the Neo, I got 'Permission denied (13)' even when I had explicitly allowed the Neo to connect (right click on Neo icon, set properties, on Authorization tab). But initiating 'PAN User' from Windows worked when executing on Neo:<br />
pand -l -r PANU -d NAP -e bnep0 -A -E -S<br />
(add '-n' to see the pand status messages until you get it right)<br />
<br />
<br />
* Configure your IP address. It should work like when connecting to Linux:<br />
ip a add 10.0.0.2/24 dev bnep0<br />
ip r add default via 10.0.0.1<br />
If this does not work, the IP stacks may have auto-assigned network addresses to themselves. You can look this up with 'ifconfig' on the Neo and with 'ipconfig' on Windows.<br />
<br />
<br />
* You should now be able to ssh/putty from Windows to your Neo. Enjoy!<br />
By setting up the Windows Bluetooth connection properly, it should also be possible to share the Internet Connection of the Windows box with the Neo.<br />
<br />
===== PPP Networking =====<br />
<br />
If you are unable to use the 'BNEP' method described above, you may be able to use [[PPP]] and a DUN (dialup-networking) emulation mode. On the Neo:<br />
<br />
* Edit the /etc/default/bluetooth file and set the following options:<br />
RFCOMM_ENABLE=true<br />
DUND_ENABLE=true<br />
DUND_OPTIONS="--listen --persist call dun"<br />
<br />
* Create an /etc/ppp/peers/dun file with options like the following:<br />
115200<br />
192.168.2.202:192.168.2.200<br />
passive<br />
local<br />
noipdefault<br />
noauth<br />
nodefaultroute<br />
<br />
* Restart bluetooth (/etc/init.d/bluetooth stop ; /etc/init.d/bluetooth start)<br />
<br />
To connect from a MacOS 10.3 client:<br />
<br />
* Open "Applications/Utilities/Bluetooth Serial Utility"<br />
<br />
* Click on "New"<br />
<br />
* Choose a name, then click "Choose Device"<br />
<br />
* Locate your Neo, then select the "LAN Access Point" service. If your device is not found, or if this service does not show up, then you will need to troubleshoot and fix that before continuing. Bluetooth is designed for short-range communication, so make sure that the devices are physically close to each other. <br />
<br />
* Select "Port type: RS-232" and "Show in Network Preferences". Click OK.<br />
<br />
* Open the Network Preferences page then "Show: Network Port Configurations". Enable the new device that you defined in the previous step and drag it to the bottom of the device list (so that it will not interfere with your other network connections)<br />
<br />
* Choose "Show: <your-device-name>", then click "Modem"<br />
<br />
* Select "Null Modem 115200" from the list of available devices. Uncheck "Wait for dial tone" and "Enable error correction and compression in modem". Optionally check "Show modem status in menu bar". <br />
<br />
* Click "Connect". If everything worked, you will end up with a 'ppp0' device on your Mac with a local address of 192.168.2.200 and you will be able to access your Neo at 192.168.2.202.<br />
<br />
===== Bluetooth networking with a Linux system - More secure way =====<br />
<br />
''Check this, probably needs some corrections''<br />
<br />
Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br />
<br />
On the laptop<br />
<br />
* check these options in /etc/bluetooth/hcid.conf<br />
security auto;<br />
passkey "your pin";<br />
lm master;<br />
<br />
* Start bluetooth<br />
# /etc/init.d/bluetooth start<br />
<br />
* Start pand as server<br />
pand --listen --role NAP --encrypt<br />
<br />
* Add in /etc/network/interfaces (see [[USB_Networking]])<br />
auto bnep0<br />
iface bnep0 inet static<br />
address 192.168.1.1<br />
netmask 255.255.255.0<br />
network 192.168.1.0<br />
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.1.0/24<br />
post-up echo 1 > /proc/sys/net/ipv4/ip_forward<br />
post-up iptables -P FORWARD ACCEPT<br />
<br />
On the Neo<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
00:20:E0:5A:FE:C8 laptop<br />
<br />
* Set pin<br />
root@fic-gta01:~$ passkey-agent 'your pin' 00:20:E0:5A:FE:C8 &<br />
<br />
* Connect to the laptop pand<br />
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br />
<br />
* Configure your IP address<br />
root@fic-gta01:~$ ifconfig bnep0 192.168.1.2<br />
root@fic-gta01:~$ route add default gateway 192.168.1.1<br />
<br />
* Enjoy<br />
<br />
==== Using Neo's connection from PC ====<br />
<br />
===== Calling Neo's GPRS modem via Bluetooth =====<br />
<br />
In this mode, Neo would behave like any other phone which can be used from a PC to get a network connection.<br />
<br />
This section not written yet. Has someone set it up?<br />
<br />
===== Sharing existing Neo's connection =====<br />
<br />
In this mode, Neo already has a network connection (GPRS, WLAN, ...), and it should get shared to the PC. This guide is general on how to forward network connection from a machine running Linux to another machine. If interested, please see more information for example at http://www.gentoo.org/doc/en/bluetooth-guide.xml.<br />
<br />
On the PC<br />
# Check with hciconfig you have working Bluetooth<br />
On the Neo<br />
(if on Debian etc., remember modprobe ohci_hcd hci_usb)<br />
# Initialize Bluetooth as told before:<br />
## echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br />
## echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
# install iptables: opkg install http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/iptables_1.3.8-r4.1_armv4t.ipk<br />
# modprobe bnep<br />
# Check that hcid is running both on Neo and PC (Bluetooth 4.x: install bluez-compat)<br />
# Use default passkey "1234" in /etc/bluetooth/hcid.conf<br />
# pand --listen --role NAP --master --autozap # note: after this you might have to the the step 1 below ("On the PC") or the next step of getting the interface up does not work # note2: you could automate pand listener to start automatically when Bluetooth is turned on<br />
# ifconfig bnep0 10.0.5.2 up<br />
# echo 1 > /proc/sys/net/ipv4/ip_forward<br />
# iptables -t nat -A POSTROUTING -j MASQUERADE -o ppp0<br />
On the PC:<br />
# sudo pand --connect <your bluetooth mac address> --service NAP --autozap<br />
# ifconfig bnep0 10.0.5.1 up<br />
# You can test the connection with ping 10.0.5.2<br />
# sudo ip route add default via 10.0.5.2 dev bnep0<br />
# [not automated yet] add GPRS connection's nameservers to /etc/resolv.conf<br />
<br />
== Advanced Audio Distribution Profile (A2DP) ==<br />
<br />
=== A2DP quickie ===<br />
<br />
* If you experience problems with choppyness, try changing your hcid.conf to include "lm accept,master;" and "lp hold,sniff,park;" You may also have to bond (commonly known as 'pairing') your phone and your headset. See http://wiki.bluez.org/wiki/HOWTO/Bonding for details. [[User:Mercury|Mercury]] 17:36, 5 September 2008 (UTC)<br />
<br />
It's now possible (if a little hackish) to stream mp3 to a bluetooth headset. It's a known problem that the playback rate changes (pitch varies). Timing issues are also likely the reason for gaps in playback.<br />
<br />
If the bluez packages are recent enough, you can use a shortcut. I'll document it here and leave the longer version below (the long version also demonstrates the API used by the GUI to manage headsets)<br />
<br />
Create /etc/asound.conf with your bluetooth headset's address filled in:<br />
<br />
pcm.!default {<br />
type bluetooth<br />
device "xx:xx:xx:xx:xx:xx"<br />
}<br />
<br />
then play a song<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay<br />
<br />
or for smoother results...<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:song.wav<br />
aplay song.wav<br />
<br />
=== A2DP ===<br />
<br />
If that doesn't work... all the more hackish... install required packages:<br />
<br />
echo "src/gz python http://www.angstrom-distribution.org/unstable/feed/armv4t/python/" >> /etc/ipkg/angstrom-python.conf <br />
echo "src/gz base http://www.angstrom-distribution.org/unstable/feed/armv4t/base/" >> /etc/ipkg/angstrom-base.conf<br />
ipkg update ; ipkg install python-core python-xml python-dbus bluez-utils bluez-utils-alsa<br />
<br />
Create /etc/asound.conf:<br />
<br />
pcm.!default {<br />
type bluetooth<br />
}<br />
ctl.!default {<br />
type bluetooth<br />
}<br />
pcm.bluetooth {<br />
type bluetooth<br />
}<br />
ctl.bluetooth {<br />
type bluetooth<br />
}<br />
<br />
Run the passkey agent (see above in this page)<br />
<br />
Fill in your bluetooth headset address below and execute the python script (with your headset turned on)<br />
<br />
#!/usr/bin/python<br />
import dbus<br />
bus = dbus.SystemBus()<br />
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')<br />
conn = manager.ActivateService('audio')<br />
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')<br />
path = audio.CreateDevice('00:0D:3C:44:33:22')<br />
audio.ChangeDefaultDevice(path)<br />
sink = dbus.Interface(bus.get_object(conn, path), 'org.bluez.audio.Sink')<br />
sink.Connect()<br />
<br />
FINALLY: play a song<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay<br />
<br />
=== Headset Audio ===<br />
<br />
[[Neo1973_Audio_Subsystem]] has detail about alsa settings and a proposal for audio scenario management.<br />
<br />
To try this out, follow the instructions in the a2dp section to install software and run the passkey agent.<br />
<br />
Remove or disable the stuff you put in asound.conf. When using a voice headset, the application uses the regular system audio device and it gets routed to bluetooth in the codec.<br />
<br />
Put the headset in pairing mode. Replace the bluetooth address below with your headset's and run the python script:<br />
<br />
#!/usr/bin/python<br />
import dbus<br />
bus = dbus.SystemBus()<br />
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')<br />
conn = manager.ActivateService('audio')<br />
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')<br />
path = audio.CreateHeadset('00:0B:2E:39:33:22')<br />
audio.ChangeDefaultHeadset(path)<br />
headset = dbus.Interface (bus.get_object(conn, path), 'org.bluez.audio.Headset')<br />
headset.Connect()<br />
headset.Play()<br />
<br />
Now place a call and try to route it to bluetooth (after it's in progress):<br />
<br />
alsactl -f /etc/gsmbluetooth.state restore<br />
<br />
You may also be able to listen to system audio given the right state file:<br />
<br />
alsactl -f /etc/systembluetooth.state restore<br />
madplay song.mp3<br />
<br />
==Bluetooth Headset on Freerunner ==<br />
<br />
[http://lists.openmoko.org/pipermail/support/2008-September/thread.html#2627 This thread] suggests the following:<br />
<br />
:Turn on bluetooth. If some of the scripts below fail you may need to reboot [https://docs.openmoko.org/trac/ticket/1744 Bluetooth after suspend]<br />
<br />
:Pair your headset according to [http://wiki.bluez.org/ these] instructions or use the script below. The script will change your .asoundrc so make a backup before you run it.<br />
<br />
:http://handheldshell.com/BtConfigure.py<br />
:Put the headset in pairing mode ( this only needs to be done once for each new headset ) and run<br />
BtConfigure.py <br />
<br />
:Download the the following python scripts to set up the audio service and set the headset as the default device:<br />
<br />
:http://handheldshell.com/BtHeadset.py<br />
:http://handheldshell.com/passkey.py<br />
:http://handheldshell.com/BtHeadsetDisconnect.py<br />
:http://handheldshell.com/python-pyalsaaudio_0.3-ml0_armv4t.ipk - can someone add python-pyalsa to the feeds ?<br />
<br />
:Download the the following python scripts if you prefer not to mess around with alsactl:<br />
<br />
:http://handheldshell.com/pymixer.py<br />
:http://handheldshell.com/volume.desktop<br />
<br />
:put pymixer in /usr/bin<br />
<br />
chmod u+x /usr/bin/pymixer.py<br />
<br />
:put volume.desktop in /usr/share/applications<br />
<br />
:Get the [[http://handheldshell.com/gsm_headset.txt alsa state file]] - this state file _WORKS_, mic and earphones are properly routed<br />
<br />
cp gsm_headset.txt /usr/share/openmoko/scenarios/btheadset.state<br />
<br />
:from the home screen run Volume<br />
<br />
:from the terminal run<br />
<br />
BtHeadset.py <br />
<br />
:Wait until it says waiting for call to end, you should hear static in the headset. If you don't something has gone wrong.<br />
<br />
:Now start the call<br />
<br />
:In the volume control switch to the btheadset tab. press restore<br />
<br />
:You should now hear the call in your headset. <br />
<br />
:End the call<br />
<br />
BtHeadsetDisconnect.py <br />
<br />
:This was all done with the 2008-updates image from sept 4. <br />
<br />
:The new scripts rely on a specific format for the .asoundrc . A stanza like this is required :<br />
<br />
pcm.headset {<br />
type bluetooth<br />
device <headset mac><br />
profile "voice"<br />
}<br />
<br />
== Further reading ==<br />
<br />
http://www.holtmann.org/papers/bluetooth/ols2006_slides.pdf<br />
http://wiki.bluez.org/wiki/Audio#org.bluez.Audio<br />
http://www.gentoo.org/doc/en/bluetooth-guide.xml<br />
<br />
{{Languages|Manually_using_Bluetooth}}<br />
<br />
[[Category:Bluetooth| ]]<br />
[[Category:Networking]]<br />
[[Category:Application Developer]]</div>Erinhttp://wiki.openmoko.org/wiki/Manually_using_BluetoothManually using Bluetooth2008-12-02T08:20:36Z<p>Erin: /* OBEX */</p>
<hr />
<div>{{InProgress}}<br />
Bluetooth is one of the core functions of the Neo1973, however it is basically unimplemented on the software side at the moment.<br />
Hardware problems in the P1 phone mean that the CPU has to be active in order to wake on external bluetooth events, which will reduce the battery life to some 2 days at best in standby.<br />
<br />
This page details how to use bluetooth from the command line.<br />
We have quite a lot of plans about what exactly Bluetooth should be used for.<br />
<br />
== Power it up ==<br />
<br />
Power up the adapter by clicking on the bluetooth icon in the top bar and selecting power on.<br />
<br />
The old way to do it is a shell command (for kernels before 2.6.24):<br />
<br />
root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on<br />
<br />
For kernel 2.6.24 (or later) use<br />
<br />
root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br />
<br />
and on the GTA02 *only* (i.e. not on the GTA01) also use<br />
<br />
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
<br />
But nowadays[http://permalink.gmane.org/gmane.comp.hardware.smartphones.userland/165], one should use [[Dbus device API]]s!<br />
<br />
At the shell, "hciconfig" should print information about the adapter if it powered up properly:<br />
<br />
hciconfig<br />
<br />
The devices should show as UP. If not you can use<br />
<br />
hciconfig <device> up<br />
<br />
== Bluetooth Functions ==<br />
<br />
===Configuring Bluetooth on Openmoko 2007.2 (August 27 snapshot with kernel 2.6.21.6-moko11) ===<br />
<br />
In file /etc/bluetooth/hcid.conf you should change the passkey from BlueZ to something numeric. For testing you may use "0000". Also, you can set the name to "Neo (%d)".<br />
<br />
=== Scanning for bluetooth devices ===<br />
<br />
hcitool scan<br />
<br />
This will list the addresses of any discoverable bluetooth devices in the vicinity<br />
<br />
=== passkey agent example ===<br />
<br />
There should be a passkey agent built into openmoko, but for now you can start up the example passkey agent and set the pin code there. This will allow for new pairings to be made when you attempt a connection.<br />
<br />
passkey-agent --default 0000 &<br />
<br />
Note: the passkey-agent is not required in Openmoko 2007.2 with kernel 2.6.21.6 as of at least since August 27 (maybe earlier).<br />
<br />
=== HID (Human Input Device) ===<br />
<br />
==== Being able to use HID devices ====<br />
<br />
Using a bluetooth keyboard with the built-in terminal is a little funky... I can only type into the console using the bt keyboard if the onscreen keyboard is visible. Also, pressing "p" twice on the bt keyboard actually gives you a "q".<br />
<br />
We want to be able to use a bluetooth keyboard to type into the various applications of our Neo1973.<br />
To use a Bluetooth Keyboard type: (11:22:33:44:55:66 is the Address of your BT-Keyboard)<br />
<br />
hidd --connect 11:22:33:44:55:66<br />
<br />
and press "Connect" on your BT-KB. Alternately, if you know that only one BT-Keyboard is within range, you can just:<br />
<br />
hidd --search<br />
<br />
to find and connect to any BT-Keyboard. There are some bluetooth keyboard only support SPP profile can't direct using hidd comannd to connect. Please reference the discussion of this page for more information.<br />
<br />
Tested on:<br />
* [http://www.logitech.com/index.cfm/products/details/US/EN,CRID=2166,CONTENTID=10717 Logitech Dinovo Edge]<br />
* [http://www.logitech.com/index.cfm/keyboards/keyboard_mice_combos/devices/164&cl=us,en Logitech Dinovo Media Desktop (keyboard)]<br />
* [http://www.nokia.es/A4181580 Nokia SU-8W]. Switched on the BT keyboard, scanned for BT address and ran the connect statement above. Works fine.<br />
* [http://blog.russnelson.com/chordite Chordite]. This keyboard uses the Broadcom BCM2042 BT keyboard controller along with a custom driver.<br />
* [http://www.apple.com/keyboard/ Apple's Aluminum Keyboard]. You may have to add 'auth enable; encrypt enable;' to device {} in hcid.conf. Run the passkey agent the first time. --search works to pair and every time after. (Might be obvious for those who have used BT in other spots, but you have to type in y our passkey on the keyboard as the connect is happening, otherwise pairing doesn't take place. I don't think there is a prompt on the Neo for this)<br />
* [http://www.apple.com/support/keyboard/ Apple's white "Wireless Keyboard (original)"] - details may be the same as above. (tested some time ago)<br />
* [http://www.frogpad.com/ FrogPad] - as above<br />
* [http://freedominput.com The freedom keyboard] and its many rebranded models (they look like this: [http://rabenfrost.net/openmoko/keyboard.jpg]) need 'modprobe uinput' to circumvent the 'Can't open input device: No such file or directory (2)' error of 'hidd --search'. It works as of february 7th 2008.<br />
* [http://www.nextag.com/Playstation-3-Logitech-Cordless-564345667/prices-html?nxtg=f8320a24052a-7789F8FE732FF6E3 Logitech Playstation 3 Keyboard] Works well, Mouse pad works.<br />
* [http://corporate.igo.com/product_details.aspx?id=16 iGo Stowaway UltraSlim] (which was apparently discontinued early 2008, but can still be bought in some places) ([[user:ChristW]] I have 2008.8 on it, and using hidd --search to connect to the iGo works perfectly. I also used it to edit a new contact, dial a number and edit a settings text box in [[TangoGPS]]. So far, no problems...)<br />
* [http://www.vkb-support.com/ I-Tech Virtual Laser Keyboard] works. Cursor keys not recognized as such, but produce keycodes than can be mapped.<br />
<br />
==== Acting as HID device ====<br />
<br />
We want to be able to use the Neo as a HID device, being able to use it as controller for presentations. See [[ReMoko]]<br />
<br />
=== RFCOMM ===<br />
<br />
Here's how to connect to an external Bluetooth GPS and read NMEA data (Tested with a Holux GPSSlim236 and a Nokia LD-3W ).<br />
<br />
First, switch on the GPS and identify the BT address:<br />
<br />
hcitool scan<br />
<br />
Then, edit /etc/bluetooth/rfcomm.conf, which by default has all settings commented out, to something like this:<br />
<br />
rfcomm0 {<br />
# Automatically bind the device at startup<br />
bind no;<br />
# Bluetooth address of the device<br />
device 00:11:22:33:44:55;<br />
# RFCOMM channel for the connection (check your GPS docs for details)<br />
channel 1;<br />
# Description of the connection<br />
comment "Bluetooth GPS";<br />
}<br />
<br />
Restart the BT services:<br />
<br />
root@neo:~$ /etc/init.d/bluetooth stop<br />
root@neo:~$ /etc/init.d/bluetooth start<br />
<br />
You should now be able to bind the GPS to /dev/rfcomm0, like this:<br />
<br />
root@neo:~$ rfcomm bind 0<br />
<br />
Confirm the connect:<br />
<br />
root@neo:~$ rfcomm<br />
rfcomm0: 00:11:22:33:44:55 channel 1 clean <br />
<br />
... and watch the NMEA strings coming from your GPS:<br />
<br />
root@neo:~$ cat /dev/rfcomm0 <br />
$GPGGA,111748.000,5907.6964,N,01121.1787,E,1,06,1.2,57.7,M,40.1,M,,0000*6F<br />
$GPRMC,111748.000,A,5907.6964,N,01121.1787,E,0.00,94.94,160807,,,A*50<br />
$GPVTG,94.94,T,,M,0.00,N,0.0,K,A*3D<br />
<br />
If you have nothing better to do, you can now pinpoint my office :-).<br />
<br />
=== OBEX ===<br />
OBEX (abbreviation of OBject EXchange, also termed IrOBEX) is a communications protocol that facilitates the exchange of binary objects between devices. Here is the notes about how to use OBEX to send/receive files via bluetooth in NEO.<br />
<br />
power on bluetooth: <br />
if you use FSO image<br />
root@om-gta02:~# dbus-send --system --dest=org.freesmartphone.odeviced --type=method_call --print-reply <br />
/org/freesmartphone/Device/PowerControl/Bluetooth org.freesmartphone.Device.PowerControl.SetPower int32:1<br />
else: (GTA02 only)<br />
root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
<br />
[http://linux.die.net/man/5/hcid.conf hcid.conf] <br />
modify /etc/bluetooth/hcid.conf<br />
<br />
<pre><br />
#<br />
# HCI daemon configuration file.<br />
#<br />
<br />
# HCId options<br />
options {<br />
# Automatically initialize new devices<br />
autoinit yes;<br />
<br />
# Security Manager mode<br />
# none - Security manager disabled<br />
# auto - Use local PIN for incoming connections<br />
# user - Always ask user for a PIN<br />
#<br />
security auto;<br />
<br />
# Pairing mode<br />
# none - Pairing disabled<br />
# multi - Allow pairing with already paired devices<br />
# once - Pair once and deny successive attempts<br />
pairing multi;<br />
<br />
# Default PIN code for incoming connections<br />
passkey "1234";<br />
}<br />
<br />
# Default settings for HCI devices<br />
device {<br />
# Local device name<br />
# %d - device id<br />
# %h - host name<br />
name "%h-%d";<br />
<br />
# Local device class<br />
class 0x000100;<br />
<br />
# Default packet type<br />
pkt_type DH1,DM1,HV1;<br />
<br />
# Inquiry and Page scan<br />
iscan enable; pscan enable;<br />
<br />
# Default link mode<br />
# none - no specific policy <br />
# accept - always accept incoming connections<br />
# master - become master on incoming connections,<br />
# deny role switch on outgoing connections<br />
lm accept;<br />
<br />
# Default link policy<br />
# none - no specific policy<br />
# rswitch - allow role switch<br />
# hold - allow hold mode<br />
# sniff - allow sniff mode<br />
# park - allow park mode<br />
lp rswitch,hold,sniff,park;<br />
}<br />
</pre><br />
<br />
[http://linux.die.net/man/8/hcid hcid] - Bluetooth Host Controller Interface Daemon <br />
<br />
All paired devices information are stored in /var/lib/bluetooth/BT HW addr folder <br />
eg. <br />
<pre><br />
root@om-gta02:/var/lib/bluetooth/00:06:6E:16:EB:C7# ls<br />
classes features lastused names panu<br />
config gn manufacturers nap<br />
</pre><br />
<br />
Display local devices<br />
root@om-gta02:/# hcitool dev<br />
<br />
Scan all nearby bluetooth devices<br />
root@om-gta02:~# hcitool scan<br />
<br />
Browse what kind of services in this device<br />
root@om-gta02:~# sdptool browse 00:18:C5:42:18:78<br />
<br />
<pre><br />
Browsing 00:18:C5:42:18:78 ...<br />
<br />
Service Name: OBEX File Transfer<br />
Service RecHandle: 0x1005b<br />
Service Class ID List:<br />
"OBEX File Transfer" (0x1106)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 11<br />
"OBEX" (0x0008)<br />
Language Base Attr List:<br />
code_ISO639: 0x454e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"OBEX File Transfer" (0x1106)<br />
Version: 0x0100<br />
<br />
Service Name: OBEX Object Push<br />
Service RecHandle: 0x1005e<br />
Service Class ID List:<br />
"OBEX Object Push" (0x1105)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 9<br />
"OBEX" (0x0008)<br />
Language Base Attr List:<br />
code_ISO639: 0x454e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"OBEX Object Push" (0x1105)<br />
Version: 0x0100<br />
<br />
</pre><br />
<br />
How to pair with a bluetooth device, check [http://wiki.bluez.org/wiki/bluez wiki]<br />
<br />
Changing to discoverable mode and setting the timeout to 60 seconds <br />
root@om-gta02:~# dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 \<br />
org.bluez.Adapter.SetMode string:discoverable<br />
<br />
root@om-gta02:~# dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 \<br />
org.bluez.Adapter.SetDiscoverableTimeout uint32:60<br />
<br />
Create Bonding: eg. another bluetooth device hw address is 00:18:C5:42:18:78<br />
root@om-gta02:~# dbus-send --system --type=method_call --print-reply --dest=org.bluez \<br />
/org/bluez/hci0 org.bluez.Adapter.CreateBonding string:00:18:C5:42:18:78<br />
<br />
Use obexpush and obexftp tools<br />
<br />
install obexpush, obexftp packages<br />
opkg install obexpush, [http://www.go2linux.org/linux-command-line-obexftp-man-page obexftp]<br />
<br />
=== Networking ===<br />
<br />
==== Using PC's connection from Neo ====<br />
<br />
===== Bluetooth networking with a Linux system =====<br />
<br />
Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br />
<br />
'''On the laptop'''<br />
<br />
* Start bluetooth<br />
/etc/init.d/bluetooth start<br />
<br />
* Start pand as server<br />
pand -s<br />
<br />
* As soon as pand is started on the phone configure your IP address<br />
ip a add 10.0.0.1/24 dev bnep0<br />
ip l set bnep0 up<br />
<br />
* Configure IP forwarding and masquerading to your liking (see [[USB_Networking]]). You can even set up Udev rules to do this for you once the bnep0 interface appears.<br />
<br />
<br />
'''On the Neo'''<br />
<br />
* There is a little script that does the steps below (and retries the pand -c command; I had issues with it not working the first time every time) at [[Bt-net-script]] You shouldn't need the other steps below if you use the script.<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
00:0E:6D:C0:0l:6A Sho<br />
00:20:E0:5A:FE:C8 BlueZ (0)<br />
<br />
* Connect to the laptop pand<br />
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br />
<br />
* Configure your IP address<br />
ip a add 10.0.0.2/24 dev bnep0<br />
ip r add default via 10.0.0.1<br />
<br />
* Sometimes you may need to bring up the bnep0 on the phone as well:<br />
ip l set bnep0 up<br />
* Enjoy<br />
<br />
<br />
*--[[User:Mantis|Mantis]] 18:37, 15 October 2008 (UTC) Note for use on OpenSuse 11.0 - I was getting a connection failure with 'Host is down(112)' errors in /var/log/messages (on neo).<br />
I found that editing /etc/bluetooth/hcid.conf to set 'pscan enable' instead of 'pscan disable' and making passkey consistent with Neo Freerunner made it work.<br />
<br />
Should see log line like<br />
''pand[17965]: New connection from 00:06:6E:XX:XX:XX at bnep0''<br />
<br />
if connection is successful in server's /var/log/messages.<br />
<br />
===== Bluetooth networking with a MacOS X system =====<br />
<br />
Please refer to [[MacOS_X#Bluetooth_2]]<br />
<br />
For using the Neo as a dialup Bluetooth server and the Mac as the client, please see below at [[Manually_using_Bluetooth#PPP_Networking]]<br />
<br />
===== Bluetooth networking with a Windows XP system =====<br />
<br />
This was tested with a Windows XP SP2 on a IBM Thinkpad T41 with the Widcomm BT stack<br />
<br />
* Start bluetooth on Windows XP<br />
<br />
* Enable "Network Access" in the Bluetooth configuration<br />
<br />
* Scan for the Neo and pair with the Neo (right click, select pair)<br />
<br />
<br />
On the Neo<br />
<br />
* Enable PAN support on the Neo by changing Autostart from false to true in /etc/bluetooth/network.service<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
<laptop_bt_address> Thinkpad<br />
...<br />
<br />
<br />
* Connect to the laptop pand<br />
pand -c <laptop_bt_address> -r PANU -d NAP -e bnep0 -A -E -S<br />
(add '-n' to see the pand status messages until you get it right)<br />
<br />
For some reason, I was not able to initiate PAN connections from the Neo, I got 'Permission denied (13)' even when I had explicitly allowed the Neo to connect (right click on Neo icon, set properties, on Authorization tab). But initiating 'PAN User' from Windows worked when executing on Neo:<br />
pand -l -r PANU -d NAP -e bnep0 -A -E -S<br />
(add '-n' to see the pand status messages until you get it right)<br />
<br />
<br />
* Configure your IP address. It should work like when connecting to Linux:<br />
ip a add 10.0.0.2/24 dev bnep0<br />
ip r add default via 10.0.0.1<br />
If this does not work, the IP stacks may have auto-assigned network addresses to themselves. You can look this up with 'ifconfig' on the Neo and with 'ipconfig' on Windows.<br />
<br />
<br />
* You should now be able to ssh/putty from Windows to your Neo. Enjoy!<br />
By setting up the Windows Bluetooth connection properly, it should also be possible to share the Internet Connection of the Windows box with the Neo.<br />
<br />
===== PPP Networking =====<br />
<br />
If you are unable to use the 'BNEP' method described above, you may be able to use [[PPP]] and a DUN (dialup-networking) emulation mode. On the Neo:<br />
<br />
* Edit the /etc/default/bluetooth file and set the following options:<br />
RFCOMM_ENABLE=true<br />
DUND_ENABLE=true<br />
DUND_OPTIONS="--listen --persist call dun"<br />
<br />
* Create an /etc/ppp/peers/dun file with options like the following:<br />
115200<br />
192.168.2.202:192.168.2.200<br />
passive<br />
local<br />
noipdefault<br />
noauth<br />
nodefaultroute<br />
<br />
* Restart bluetooth (/etc/init.d/bluetooth stop ; /etc/init.d/bluetooth start)<br />
<br />
To connect from a MacOS 10.3 client:<br />
<br />
* Open "Applications/Utilities/Bluetooth Serial Utility"<br />
<br />
* Click on "New"<br />
<br />
* Choose a name, then click "Choose Device"<br />
<br />
* Locate your Neo, then select the "LAN Access Point" service. If your device is not found, or if this service does not show up, then you will need to troubleshoot and fix that before continuing. Bluetooth is designed for short-range communication, so make sure that the devices are physically close to each other. <br />
<br />
* Select "Port type: RS-232" and "Show in Network Preferences". Click OK.<br />
<br />
* Open the Network Preferences page then "Show: Network Port Configurations". Enable the new device that you defined in the previous step and drag it to the bottom of the device list (so that it will not interfere with your other network connections)<br />
<br />
* Choose "Show: <your-device-name>", then click "Modem"<br />
<br />
* Select "Null Modem 115200" from the list of available devices. Uncheck "Wait for dial tone" and "Enable error correction and compression in modem". Optionally check "Show modem status in menu bar". <br />
<br />
* Click "Connect". If everything worked, you will end up with a 'ppp0' device on your Mac with a local address of 192.168.2.200 and you will be able to access your Neo at 192.168.2.202.<br />
<br />
===== Bluetooth networking with a Linux system - More secure way =====<br />
<br />
''Check this, probably needs some corrections''<br />
<br />
Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br />
<br />
On the laptop<br />
<br />
* check these options in /etc/bluetooth/hcid.conf<br />
security auto;<br />
passkey "your pin";<br />
lm master;<br />
<br />
* Start bluetooth<br />
# /etc/init.d/bluetooth start<br />
<br />
* Start pand as server<br />
pand --listen --role NAP --encrypt<br />
<br />
* Add in /etc/network/interfaces (see [[USB_Networking]])<br />
auto bnep0<br />
iface bnep0 inet static<br />
address 192.168.1.1<br />
netmask 255.255.255.0<br />
network 192.168.1.0<br />
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.1.0/24<br />
post-up echo 1 > /proc/sys/net/ipv4/ip_forward<br />
post-up iptables -P FORWARD ACCEPT<br />
<br />
On the Neo<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
00:20:E0:5A:FE:C8 laptop<br />
<br />
* Set pin<br />
root@fic-gta01:~$ passkey-agent 'your pin' 00:20:E0:5A:FE:C8 &<br />
<br />
* Connect to the laptop pand<br />
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br />
<br />
* Configure your IP address<br />
root@fic-gta01:~$ ifconfig bnep0 192.168.1.2<br />
root@fic-gta01:~$ route add default gateway 192.168.1.1<br />
<br />
* Enjoy<br />
<br />
==== Using Neo's connection from PC ====<br />
<br />
===== Calling Neo's GPRS modem via Bluetooth =====<br />
<br />
In this mode, Neo would behave like any other phone which can be used from a PC to get a network connection.<br />
<br />
This section not written yet. Has someone set it up?<br />
<br />
===== Sharing existing Neo's connection =====<br />
<br />
In this mode, Neo already has a network connection (GPRS, WLAN, ...), and it should get shared to the PC. This guide is general on how to forward network connection from a machine running Linux to another machine. If interested, please see more information for example at http://www.gentoo.org/doc/en/bluetooth-guide.xml.<br />
<br />
On the PC<br />
# Check with hciconfig you have working Bluetooth<br />
On the Neo<br />
(if on Debian etc., remember modprobe ohci_hcd hci_usb)<br />
# Initialize Bluetooth as told before:<br />
## echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br />
## echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
# install iptables: opkg install http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/iptables_1.3.8-r4.1_armv4t.ipk<br />
# modprobe bnep<br />
# Check that hcid is running both on Neo and PC (Bluetooth 4.x: install bluez-compat)<br />
# Use default passkey "1234" in /etc/bluetooth/hcid.conf<br />
# pand --listen --role NAP --master --autozap # note: after this you might have to the the step 1 below ("On the PC") or the next step of getting the interface up does not work # note2: you could automate pand listener to start automatically when Bluetooth is turned on<br />
# ifconfig bnep0 10.0.5.2 up<br />
# echo 1 > /proc/sys/net/ipv4/ip_forward<br />
# iptables -t nat -A POSTROUTING -j MASQUERADE -o ppp0<br />
On the PC:<br />
# sudo pand --connect <your bluetooth mac address> --service NAP --autozap<br />
# ifconfig bnep0 10.0.5.1 up<br />
# You can test the connection with ping 10.0.5.2<br />
# sudo ip route add default via 10.0.5.2 dev bnep0<br />
# [not automated yet] add GPRS connection's nameservers to /etc/resolv.conf<br />
<br />
== Advanced Audio Distribution Profile (A2DP) ==<br />
<br />
=== A2DP quickie ===<br />
<br />
* If you experience problems with choppyness, try changing your hcid.conf to include "lm accept,master;" and "lp hold,sniff,park;" You may also have to bond (commonly known as 'pairing') your phone and your headset. See http://wiki.bluez.org/wiki/HOWTO/Bonding for details. [[User:Mercury|Mercury]] 17:36, 5 September 2008 (UTC)<br />
<br />
It's now possible (if a little hackish) to stream mp3 to a bluetooth headset. It's a known problem that the playback rate changes (pitch varies). Timing issues are also likely the reason for gaps in playback.<br />
<br />
If the bluez packages are recent enough, you can use a shortcut. I'll document it here and leave the longer version below (the long version also demonstrates the API used by the GUI to manage headsets)<br />
<br />
Create /etc/asound.conf with your bluetooth headset's address filled in:<br />
<br />
pcm.!default {<br />
type bluetooth<br />
device "xx:xx:xx:xx:xx:xx"<br />
}<br />
<br />
then play a song<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay<br />
<br />
or for smoother results...<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:song.wav<br />
aplay song.wav<br />
<br />
=== A2DP ===<br />
<br />
If that doesn't work... all the more hackish... install required packages:<br />
<br />
echo "src/gz python http://www.angstrom-distribution.org/unstable/feed/armv4t/python/" >> /etc/ipkg/angstrom-python.conf <br />
echo "src/gz base http://www.angstrom-distribution.org/unstable/feed/armv4t/base/" >> /etc/ipkg/angstrom-base.conf<br />
ipkg update ; ipkg install python-core python-xml python-dbus bluez-utils bluez-utils-alsa<br />
<br />
Create /etc/asound.conf:<br />
<br />
pcm.!default {<br />
type bluetooth<br />
}<br />
ctl.!default {<br />
type bluetooth<br />
}<br />
pcm.bluetooth {<br />
type bluetooth<br />
}<br />
ctl.bluetooth {<br />
type bluetooth<br />
}<br />
<br />
Run the passkey agent (see above in this page)<br />
<br />
Fill in your bluetooth headset address below and execute the python script (with your headset turned on)<br />
<br />
#!/usr/bin/python<br />
import dbus<br />
bus = dbus.SystemBus()<br />
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')<br />
conn = manager.ActivateService('audio')<br />
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')<br />
path = audio.CreateDevice('00:0D:3C:44:33:22')<br />
audio.ChangeDefaultDevice(path)<br />
sink = dbus.Interface(bus.get_object(conn, path), 'org.bluez.audio.Sink')<br />
sink.Connect()<br />
<br />
FINALLY: play a song<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay<br />
<br />
=== Headset Audio ===<br />
<br />
[[Neo1973_Audio_Subsystem]] has detail about alsa settings and a proposal for audio scenario management.<br />
<br />
To try this out, follow the instructions in the a2dp section to install software and run the passkey agent.<br />
<br />
Remove or disable the stuff you put in asound.conf. When using a voice headset, the application uses the regular system audio device and it gets routed to bluetooth in the codec.<br />
<br />
Put the headset in pairing mode. Replace the bluetooth address below with your headset's and run the python script:<br />
<br />
#!/usr/bin/python<br />
import dbus<br />
bus = dbus.SystemBus()<br />
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')<br />
conn = manager.ActivateService('audio')<br />
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')<br />
path = audio.CreateHeadset('00:0B:2E:39:33:22')<br />
audio.ChangeDefaultHeadset(path)<br />
headset = dbus.Interface (bus.get_object(conn, path), 'org.bluez.audio.Headset')<br />
headset.Connect()<br />
headset.Play()<br />
<br />
Now place a call and try to route it to bluetooth (after it's in progress):<br />
<br />
alsactl -f /etc/gsmbluetooth.state restore<br />
<br />
You may also be able to listen to system audio given the right state file:<br />
<br />
alsactl -f /etc/systembluetooth.state restore<br />
madplay song.mp3<br />
<br />
==Bluetooth Headset on Freerunner ==<br />
<br />
[http://lists.openmoko.org/pipermail/support/2008-September/thread.html#2627 This thread] suggests the following:<br />
<br />
:Turn on bluetooth. If some of the scripts below fail you may need to reboot [https://docs.openmoko.org/trac/ticket/1744 Bluetooth after suspend]<br />
<br />
:Pair your headset according to [http://wiki.bluez.org/ these] instructions or use the script below. The script will change your .asoundrc so make a backup before you run it.<br />
<br />
:http://handheldshell.com/BtConfigure.py<br />
:Put the headset in pairing mode ( this only needs to be done once for each new headset ) and run<br />
BtConfigure.py <br />
<br />
:Download the the following python scripts to set up the audio service and set the headset as the default device:<br />
<br />
:http://handheldshell.com/BtHeadset.py<br />
:http://handheldshell.com/passkey.py<br />
:http://handheldshell.com/BtHeadsetDisconnect.py<br />
:http://handheldshell.com/python-pyalsaaudio_0.3-ml0_armv4t.ipk - can someone add python-pyalsa to the feeds ?<br />
<br />
:Download the the following python scripts if you prefer not to mess around with alsactl:<br />
<br />
:http://handheldshell.com/pymixer.py<br />
:http://handheldshell.com/volume.desktop<br />
<br />
:put pymixer in /usr/bin<br />
<br />
chmod u+x /usr/bin/pymixer.py<br />
<br />
:put volume.desktop in /usr/share/applications<br />
<br />
:Get the [[http://handheldshell.com/gsm_headset.txt alsa state file]] - this state file _WORKS_, mic and earphones are properly routed<br />
<br />
cp gsm_headset.txt /usr/share/openmoko/scenarios/btheadset.state<br />
<br />
:from the home screen run Volume<br />
<br />
:from the terminal run<br />
<br />
BtHeadset.py <br />
<br />
:Wait until it says waiting for call to end, you should hear static in the headset. If you don't something has gone wrong.<br />
<br />
:Now start the call<br />
<br />
:In the volume control switch to the btheadset tab. press restore<br />
<br />
:You should now hear the call in your headset. <br />
<br />
:End the call<br />
<br />
BtHeadsetDisconnect.py <br />
<br />
:This was all done with the 2008-updates image from sept 4. <br />
<br />
:The new scripts rely on a specific format for the .asoundrc . A stanza like this is required :<br />
<br />
pcm.headset {<br />
type bluetooth<br />
device <headset mac><br />
profile "voice"<br />
}<br />
<br />
== Further reading ==<br />
<br />
http://www.holtmann.org/papers/bluetooth/ols2006_slides.pdf<br />
http://wiki.bluez.org/wiki/Audio#org.bluez.Audio<br />
http://www.gentoo.org/doc/en/bluetooth-guide.xml<br />
<br />
{{Languages|Manually_using_Bluetooth}}<br />
<br />
[[Category:Bluetooth| ]]<br />
[[Category:Networking]]<br />
[[Category:Application Developer]]</div>Erinhttp://wiki.openmoko.org/wiki/Manually_using_BluetoothManually using Bluetooth2008-12-02T08:14:24Z<p>Erin: /* OBEX */</p>
<hr />
<div>{{InProgress}}<br />
Bluetooth is one of the core functions of the Neo1973, however it is basically unimplemented on the software side at the moment.<br />
Hardware problems in the P1 phone mean that the CPU has to be active in order to wake on external bluetooth events, which will reduce the battery life to some 2 days at best in standby.<br />
<br />
This page details how to use bluetooth from the command line.<br />
We have quite a lot of plans about what exactly Bluetooth should be used for.<br />
<br />
== Power it up ==<br />
<br />
Power up the adapter by clicking on the bluetooth icon in the top bar and selecting power on.<br />
<br />
The old way to do it is a shell command (for kernels before 2.6.24):<br />
<br />
root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on<br />
<br />
For kernel 2.6.24 (or later) use<br />
<br />
root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br />
<br />
and on the GTA02 *only* (i.e. not on the GTA01) also use<br />
<br />
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
<br />
But nowadays[http://permalink.gmane.org/gmane.comp.hardware.smartphones.userland/165], one should use [[Dbus device API]]s!<br />
<br />
At the shell, "hciconfig" should print information about the adapter if it powered up properly:<br />
<br />
hciconfig<br />
<br />
The devices should show as UP. If not you can use<br />
<br />
hciconfig <device> up<br />
<br />
== Bluetooth Functions ==<br />
<br />
===Configuring Bluetooth on Openmoko 2007.2 (August 27 snapshot with kernel 2.6.21.6-moko11) ===<br />
<br />
In file /etc/bluetooth/hcid.conf you should change the passkey from BlueZ to something numeric. For testing you may use "0000". Also, you can set the name to "Neo (%d)".<br />
<br />
=== Scanning for bluetooth devices ===<br />
<br />
hcitool scan<br />
<br />
This will list the addresses of any discoverable bluetooth devices in the vicinity<br />
<br />
=== passkey agent example ===<br />
<br />
There should be a passkey agent built into openmoko, but for now you can start up the example passkey agent and set the pin code there. This will allow for new pairings to be made when you attempt a connection.<br />
<br />
passkey-agent --default 0000 &<br />
<br />
Note: the passkey-agent is not required in Openmoko 2007.2 with kernel 2.6.21.6 as of at least since August 27 (maybe earlier).<br />
<br />
=== HID (Human Input Device) ===<br />
<br />
==== Being able to use HID devices ====<br />
<br />
Using a bluetooth keyboard with the built-in terminal is a little funky... I can only type into the console using the bt keyboard if the onscreen keyboard is visible. Also, pressing "p" twice on the bt keyboard actually gives you a "q".<br />
<br />
We want to be able to use a bluetooth keyboard to type into the various applications of our Neo1973.<br />
To use a Bluetooth Keyboard type: (11:22:33:44:55:66 is the Address of your BT-Keyboard)<br />
<br />
hidd --connect 11:22:33:44:55:66<br />
<br />
and press "Connect" on your BT-KB. Alternately, if you know that only one BT-Keyboard is within range, you can just:<br />
<br />
hidd --search<br />
<br />
to find and connect to any BT-Keyboard. There are some bluetooth keyboard only support SPP profile can't direct using hidd comannd to connect. Please reference the discussion of this page for more information.<br />
<br />
Tested on:<br />
* [http://www.logitech.com/index.cfm/products/details/US/EN,CRID=2166,CONTENTID=10717 Logitech Dinovo Edge]<br />
* [http://www.logitech.com/index.cfm/keyboards/keyboard_mice_combos/devices/164&cl=us,en Logitech Dinovo Media Desktop (keyboard)]<br />
* [http://www.nokia.es/A4181580 Nokia SU-8W]. Switched on the BT keyboard, scanned for BT address and ran the connect statement above. Works fine.<br />
* [http://blog.russnelson.com/chordite Chordite]. This keyboard uses the Broadcom BCM2042 BT keyboard controller along with a custom driver.<br />
* [http://www.apple.com/keyboard/ Apple's Aluminum Keyboard]. You may have to add 'auth enable; encrypt enable;' to device {} in hcid.conf. Run the passkey agent the first time. --search works to pair and every time after. (Might be obvious for those who have used BT in other spots, but you have to type in y our passkey on the keyboard as the connect is happening, otherwise pairing doesn't take place. I don't think there is a prompt on the Neo for this)<br />
* [http://www.apple.com/support/keyboard/ Apple's white "Wireless Keyboard (original)"] - details may be the same as above. (tested some time ago)<br />
* [http://www.frogpad.com/ FrogPad] - as above<br />
* [http://freedominput.com The freedom keyboard] and its many rebranded models (they look like this: [http://rabenfrost.net/openmoko/keyboard.jpg]) need 'modprobe uinput' to circumvent the 'Can't open input device: No such file or directory (2)' error of 'hidd --search'. It works as of february 7th 2008.<br />
* [http://www.nextag.com/Playstation-3-Logitech-Cordless-564345667/prices-html?nxtg=f8320a24052a-7789F8FE732FF6E3 Logitech Playstation 3 Keyboard] Works well, Mouse pad works.<br />
* [http://corporate.igo.com/product_details.aspx?id=16 iGo Stowaway UltraSlim] (which was apparently discontinued early 2008, but can still be bought in some places) ([[user:ChristW]] I have 2008.8 on it, and using hidd --search to connect to the iGo works perfectly. I also used it to edit a new contact, dial a number and edit a settings text box in [[TangoGPS]]. So far, no problems...)<br />
* [http://www.vkb-support.com/ I-Tech Virtual Laser Keyboard] works. Cursor keys not recognized as such, but produce keycodes than can be mapped.<br />
<br />
==== Acting as HID device ====<br />
<br />
We want to be able to use the Neo as a HID device, being able to use it as controller for presentations. See [[ReMoko]]<br />
<br />
=== RFCOMM ===<br />
<br />
Here's how to connect to an external Bluetooth GPS and read NMEA data (Tested with a Holux GPSSlim236 and a Nokia LD-3W ).<br />
<br />
First, switch on the GPS and identify the BT address:<br />
<br />
hcitool scan<br />
<br />
Then, edit /etc/bluetooth/rfcomm.conf, which by default has all settings commented out, to something like this:<br />
<br />
rfcomm0 {<br />
# Automatically bind the device at startup<br />
bind no;<br />
# Bluetooth address of the device<br />
device 00:11:22:33:44:55;<br />
# RFCOMM channel for the connection (check your GPS docs for details)<br />
channel 1;<br />
# Description of the connection<br />
comment "Bluetooth GPS";<br />
}<br />
<br />
Restart the BT services:<br />
<br />
root@neo:~$ /etc/init.d/bluetooth stop<br />
root@neo:~$ /etc/init.d/bluetooth start<br />
<br />
You should now be able to bind the GPS to /dev/rfcomm0, like this:<br />
<br />
root@neo:~$ rfcomm bind 0<br />
<br />
Confirm the connect:<br />
<br />
root@neo:~$ rfcomm<br />
rfcomm0: 00:11:22:33:44:55 channel 1 clean <br />
<br />
... and watch the NMEA strings coming from your GPS:<br />
<br />
root@neo:~$ cat /dev/rfcomm0 <br />
$GPGGA,111748.000,5907.6964,N,01121.1787,E,1,06,1.2,57.7,M,40.1,M,,0000*6F<br />
$GPRMC,111748.000,A,5907.6964,N,01121.1787,E,0.00,94.94,160807,,,A*50<br />
$GPVTG,94.94,T,,M,0.00,N,0.0,K,A*3D<br />
<br />
If you have nothing better to do, you can now pinpoint my office :-).<br />
<br />
=== OBEX ===<br />
OBEX (abbreviation of OBject EXchange, also termed IrOBEX) is a communications protocol that facilitates the exchange of binary objects between devices. Here is the notes about how to use OBEX to send/receive files via bluetooth in NEO.<br />
<br />
power on bluetooth: <br />
if you use FSO image<br />
root@om-gta02:~# dbus-send --system --dest=org.freesmartphone.odeviced --type=method_call --print-reply <br />
/org/freesmartphone/Device/PowerControl/Bluetooth org.freesmartphone.Device.PowerControl.SetPower int32:1<br />
else: (GTA02 only)<br />
root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
<br />
[http://linux.die.net/man/5/hcid.conf hcid.conf] <br />
modify /etc/bluetooth/hcid.conf<br />
<br />
<pre><br />
#<br />
# HCI daemon configuration file.<br />
#<br />
<br />
# HCId options<br />
options {<br />
# Automatically initialize new devices<br />
autoinit yes;<br />
<br />
# Security Manager mode<br />
# none - Security manager disabled<br />
# auto - Use local PIN for incoming connections<br />
# user - Always ask user for a PIN<br />
#<br />
security auto;<br />
<br />
# Pairing mode<br />
# none - Pairing disabled<br />
# multi - Allow pairing with already paired devices<br />
# once - Pair once and deny successive attempts<br />
pairing multi;<br />
<br />
# Default PIN code for incoming connections<br />
passkey "1234";<br />
}<br />
<br />
# Default settings for HCI devices<br />
device {<br />
# Local device name<br />
# %d - device id<br />
# %h - host name<br />
name "%h-%d";<br />
<br />
# Local device class<br />
class 0x000100;<br />
<br />
# Default packet type<br />
pkt_type DH1,DM1,HV1;<br />
<br />
# Inquiry and Page scan<br />
iscan enable; pscan enable;<br />
<br />
# Default link mode<br />
# none - no specific policy <br />
# accept - always accept incoming connections<br />
# master - become master on incoming connections,<br />
# deny role switch on outgoing connections<br />
lm accept;<br />
<br />
# Default link policy<br />
# none - no specific policy<br />
# rswitch - allow role switch<br />
# hold - allow hold mode<br />
# sniff - allow sniff mode<br />
# park - allow park mode<br />
lp rswitch,hold,sniff,park;<br />
}<br />
</pre><br />
<br />
[http://linux.die.net/man/8/hcid hcid] - Bluetooth Host Controller Interface Daemon <br />
<br />
All paired devices information are stored in /var/lib/bluetooth/BT HW addr folder <br />
eg. <br />
<pre><br />
root@om-gta02:/var/lib/bluetooth/00:06:6E:16:EB:C7# ls<br />
classes features lastused names panu<br />
config gn manufacturers nap<br />
</pre><br />
<br />
Display local devices<br />
root@om-gta02:/# hcitool dev<br />
<br />
Scan all nearby bluetooth devices<br />
root@om-gta02:~# hcitool scan<br />
<br />
Browse what kind of services in this device<br />
sdptool browse 00:16:20:60:7C:36<br />
<br />
<pre><br />
Browsing 00:18:C5:42:18:78 ...<br />
<br />
Service Name: OBEX File Transfer<br />
Service RecHandle: 0x1005b<br />
Service Class ID List:<br />
"OBEX File Transfer" (0x1106)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 11<br />
"OBEX" (0x0008)<br />
Language Base Attr List:<br />
code_ISO639: 0x454e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"OBEX File Transfer" (0x1106)<br />
Version: 0x0100<br />
<br />
Service Name: OBEX Object Push<br />
Service RecHandle: 0x1005e<br />
Service Class ID List:<br />
"OBEX Object Push" (0x1105)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 9<br />
"OBEX" (0x0008)<br />
Language Base Attr List:<br />
code_ISO639: 0x454e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"OBEX Object Push" (0x1105)<br />
Version: 0x0100<br />
<br />
</pre><br />
<br />
How to pair with a bluetooth device, check [http://wiki.bluez.org/wiki/bluez wiki]<br />
<br />
Changing to discoverable mode and setting the timeout to 60 seconds<br />
$dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetMode string:discoverable<br />
$dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetDiscoverableTimeout uint32:60<br />
<br />
CREATE BONDING:<br />
$dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.CreateBonding string:00:18:C5:42:18:78<br />
<br />
Use obexpush and obexftp tools<br />
<br />
install obexpush, obexftp packages<br />
opkg install obexpush, [http://www.go2linux.org/linux-command-line-obexftp-man-page obexftp]<br />
<br />
=== Networking ===<br />
<br />
==== Using PC's connection from Neo ====<br />
<br />
===== Bluetooth networking with a Linux system =====<br />
<br />
Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br />
<br />
'''On the laptop'''<br />
<br />
* Start bluetooth<br />
/etc/init.d/bluetooth start<br />
<br />
* Start pand as server<br />
pand -s<br />
<br />
* As soon as pand is started on the phone configure your IP address<br />
ip a add 10.0.0.1/24 dev bnep0<br />
ip l set bnep0 up<br />
<br />
* Configure IP forwarding and masquerading to your liking (see [[USB_Networking]]). You can even set up Udev rules to do this for you once the bnep0 interface appears.<br />
<br />
<br />
'''On the Neo'''<br />
<br />
* There is a little script that does the steps below (and retries the pand -c command; I had issues with it not working the first time every time) at [[Bt-net-script]] You shouldn't need the other steps below if you use the script.<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
00:0E:6D:C0:0l:6A Sho<br />
00:20:E0:5A:FE:C8 BlueZ (0)<br />
<br />
* Connect to the laptop pand<br />
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br />
<br />
* Configure your IP address<br />
ip a add 10.0.0.2/24 dev bnep0<br />
ip r add default via 10.0.0.1<br />
<br />
* Sometimes you may need to bring up the bnep0 on the phone as well:<br />
ip l set bnep0 up<br />
* Enjoy<br />
<br />
<br />
*--[[User:Mantis|Mantis]] 18:37, 15 October 2008 (UTC) Note for use on OpenSuse 11.0 - I was getting a connection failure with 'Host is down(112)' errors in /var/log/messages (on neo).<br />
I found that editing /etc/bluetooth/hcid.conf to set 'pscan enable' instead of 'pscan disable' and making passkey consistent with Neo Freerunner made it work.<br />
<br />
Should see log line like<br />
''pand[17965]: New connection from 00:06:6E:XX:XX:XX at bnep0''<br />
<br />
if connection is successful in server's /var/log/messages.<br />
<br />
===== Bluetooth networking with a MacOS X system =====<br />
<br />
Please refer to [[MacOS_X#Bluetooth_2]]<br />
<br />
For using the Neo as a dialup Bluetooth server and the Mac as the client, please see below at [[Manually_using_Bluetooth#PPP_Networking]]<br />
<br />
===== Bluetooth networking with a Windows XP system =====<br />
<br />
This was tested with a Windows XP SP2 on a IBM Thinkpad T41 with the Widcomm BT stack<br />
<br />
* Start bluetooth on Windows XP<br />
<br />
* Enable "Network Access" in the Bluetooth configuration<br />
<br />
* Scan for the Neo and pair with the Neo (right click, select pair)<br />
<br />
<br />
On the Neo<br />
<br />
* Enable PAN support on the Neo by changing Autostart from false to true in /etc/bluetooth/network.service<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
<laptop_bt_address> Thinkpad<br />
...<br />
<br />
<br />
* Connect to the laptop pand<br />
pand -c <laptop_bt_address> -r PANU -d NAP -e bnep0 -A -E -S<br />
(add '-n' to see the pand status messages until you get it right)<br />
<br />
For some reason, I was not able to initiate PAN connections from the Neo, I got 'Permission denied (13)' even when I had explicitly allowed the Neo to connect (right click on Neo icon, set properties, on Authorization tab). But initiating 'PAN User' from Windows worked when executing on Neo:<br />
pand -l -r PANU -d NAP -e bnep0 -A -E -S<br />
(add '-n' to see the pand status messages until you get it right)<br />
<br />
<br />
* Configure your IP address. It should work like when connecting to Linux:<br />
ip a add 10.0.0.2/24 dev bnep0<br />
ip r add default via 10.0.0.1<br />
If this does not work, the IP stacks may have auto-assigned network addresses to themselves. You can look this up with 'ifconfig' on the Neo and with 'ipconfig' on Windows.<br />
<br />
<br />
* You should now be able to ssh/putty from Windows to your Neo. Enjoy!<br />
By setting up the Windows Bluetooth connection properly, it should also be possible to share the Internet Connection of the Windows box with the Neo.<br />
<br />
===== PPP Networking =====<br />
<br />
If you are unable to use the 'BNEP' method described above, you may be able to use [[PPP]] and a DUN (dialup-networking) emulation mode. On the Neo:<br />
<br />
* Edit the /etc/default/bluetooth file and set the following options:<br />
RFCOMM_ENABLE=true<br />
DUND_ENABLE=true<br />
DUND_OPTIONS="--listen --persist call dun"<br />
<br />
* Create an /etc/ppp/peers/dun file with options like the following:<br />
115200<br />
192.168.2.202:192.168.2.200<br />
passive<br />
local<br />
noipdefault<br />
noauth<br />
nodefaultroute<br />
<br />
* Restart bluetooth (/etc/init.d/bluetooth stop ; /etc/init.d/bluetooth start)<br />
<br />
To connect from a MacOS 10.3 client:<br />
<br />
* Open "Applications/Utilities/Bluetooth Serial Utility"<br />
<br />
* Click on "New"<br />
<br />
* Choose a name, then click "Choose Device"<br />
<br />
* Locate your Neo, then select the "LAN Access Point" service. If your device is not found, or if this service does not show up, then you will need to troubleshoot and fix that before continuing. Bluetooth is designed for short-range communication, so make sure that the devices are physically close to each other. <br />
<br />
* Select "Port type: RS-232" and "Show in Network Preferences". Click OK.<br />
<br />
* Open the Network Preferences page then "Show: Network Port Configurations". Enable the new device that you defined in the previous step and drag it to the bottom of the device list (so that it will not interfere with your other network connections)<br />
<br />
* Choose "Show: <your-device-name>", then click "Modem"<br />
<br />
* Select "Null Modem 115200" from the list of available devices. Uncheck "Wait for dial tone" and "Enable error correction and compression in modem". Optionally check "Show modem status in menu bar". <br />
<br />
* Click "Connect". If everything worked, you will end up with a 'ppp0' device on your Mac with a local address of 192.168.2.200 and you will be able to access your Neo at 192.168.2.202.<br />
<br />
===== Bluetooth networking with a Linux system - More secure way =====<br />
<br />
''Check this, probably needs some corrections''<br />
<br />
Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br />
<br />
On the laptop<br />
<br />
* check these options in /etc/bluetooth/hcid.conf<br />
security auto;<br />
passkey "your pin";<br />
lm master;<br />
<br />
* Start bluetooth<br />
# /etc/init.d/bluetooth start<br />
<br />
* Start pand as server<br />
pand --listen --role NAP --encrypt<br />
<br />
* Add in /etc/network/interfaces (see [[USB_Networking]])<br />
auto bnep0<br />
iface bnep0 inet static<br />
address 192.168.1.1<br />
netmask 255.255.255.0<br />
network 192.168.1.0<br />
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.1.0/24<br />
post-up echo 1 > /proc/sys/net/ipv4/ip_forward<br />
post-up iptables -P FORWARD ACCEPT<br />
<br />
On the Neo<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
00:20:E0:5A:FE:C8 laptop<br />
<br />
* Set pin<br />
root@fic-gta01:~$ passkey-agent 'your pin' 00:20:E0:5A:FE:C8 &<br />
<br />
* Connect to the laptop pand<br />
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br />
<br />
* Configure your IP address<br />
root@fic-gta01:~$ ifconfig bnep0 192.168.1.2<br />
root@fic-gta01:~$ route add default gateway 192.168.1.1<br />
<br />
* Enjoy<br />
<br />
==== Using Neo's connection from PC ====<br />
<br />
===== Calling Neo's GPRS modem via Bluetooth =====<br />
<br />
In this mode, Neo would behave like any other phone which can be used from a PC to get a network connection.<br />
<br />
This section not written yet. Has someone set it up?<br />
<br />
===== Sharing existing Neo's connection =====<br />
<br />
In this mode, Neo already has a network connection (GPRS, WLAN, ...), and it should get shared to the PC. This guide is general on how to forward network connection from a machine running Linux to another machine. If interested, please see more information for example at http://www.gentoo.org/doc/en/bluetooth-guide.xml.<br />
<br />
On the PC<br />
# Check with hciconfig you have working Bluetooth<br />
On the Neo<br />
(if on Debian etc., remember modprobe ohci_hcd hci_usb)<br />
# Initialize Bluetooth as told before:<br />
## echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br />
## echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
# install iptables: opkg install http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/iptables_1.3.8-r4.1_armv4t.ipk<br />
# modprobe bnep<br />
# Check that hcid is running both on Neo and PC (Bluetooth 4.x: install bluez-compat)<br />
# Use default passkey "1234" in /etc/bluetooth/hcid.conf<br />
# pand --listen --role NAP --master --autozap # note: after this you might have to the the step 1 below ("On the PC") or the next step of getting the interface up does not work # note2: you could automate pand listener to start automatically when Bluetooth is turned on<br />
# ifconfig bnep0 10.0.5.2 up<br />
# echo 1 > /proc/sys/net/ipv4/ip_forward<br />
# iptables -t nat -A POSTROUTING -j MASQUERADE -o ppp0<br />
On the PC:<br />
# sudo pand --connect <your bluetooth mac address> --service NAP --autozap<br />
# ifconfig bnep0 10.0.5.1 up<br />
# You can test the connection with ping 10.0.5.2<br />
# sudo ip route add default via 10.0.5.2 dev bnep0<br />
# [not automated yet] add GPRS connection's nameservers to /etc/resolv.conf<br />
<br />
== Advanced Audio Distribution Profile (A2DP) ==<br />
<br />
=== A2DP quickie ===<br />
<br />
* If you experience problems with choppyness, try changing your hcid.conf to include "lm accept,master;" and "lp hold,sniff,park;" You may also have to bond (commonly known as 'pairing') your phone and your headset. See http://wiki.bluez.org/wiki/HOWTO/Bonding for details. [[User:Mercury|Mercury]] 17:36, 5 September 2008 (UTC)<br />
<br />
It's now possible (if a little hackish) to stream mp3 to a bluetooth headset. It's a known problem that the playback rate changes (pitch varies). Timing issues are also likely the reason for gaps in playback.<br />
<br />
If the bluez packages are recent enough, you can use a shortcut. I'll document it here and leave the longer version below (the long version also demonstrates the API used by the GUI to manage headsets)<br />
<br />
Create /etc/asound.conf with your bluetooth headset's address filled in:<br />
<br />
pcm.!default {<br />
type bluetooth<br />
device "xx:xx:xx:xx:xx:xx"<br />
}<br />
<br />
then play a song<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay<br />
<br />
or for smoother results...<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:song.wav<br />
aplay song.wav<br />
<br />
=== A2DP ===<br />
<br />
If that doesn't work... all the more hackish... install required packages:<br />
<br />
echo "src/gz python http://www.angstrom-distribution.org/unstable/feed/armv4t/python/" >> /etc/ipkg/angstrom-python.conf <br />
echo "src/gz base http://www.angstrom-distribution.org/unstable/feed/armv4t/base/" >> /etc/ipkg/angstrom-base.conf<br />
ipkg update ; ipkg install python-core python-xml python-dbus bluez-utils bluez-utils-alsa<br />
<br />
Create /etc/asound.conf:<br />
<br />
pcm.!default {<br />
type bluetooth<br />
}<br />
ctl.!default {<br />
type bluetooth<br />
}<br />
pcm.bluetooth {<br />
type bluetooth<br />
}<br />
ctl.bluetooth {<br />
type bluetooth<br />
}<br />
<br />
Run the passkey agent (see above in this page)<br />
<br />
Fill in your bluetooth headset address below and execute the python script (with your headset turned on)<br />
<br />
#!/usr/bin/python<br />
import dbus<br />
bus = dbus.SystemBus()<br />
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')<br />
conn = manager.ActivateService('audio')<br />
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')<br />
path = audio.CreateDevice('00:0D:3C:44:33:22')<br />
audio.ChangeDefaultDevice(path)<br />
sink = dbus.Interface(bus.get_object(conn, path), 'org.bluez.audio.Sink')<br />
sink.Connect()<br />
<br />
FINALLY: play a song<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay<br />
<br />
=== Headset Audio ===<br />
<br />
[[Neo1973_Audio_Subsystem]] has detail about alsa settings and a proposal for audio scenario management.<br />
<br />
To try this out, follow the instructions in the a2dp section to install software and run the passkey agent.<br />
<br />
Remove or disable the stuff you put in asound.conf. When using a voice headset, the application uses the regular system audio device and it gets routed to bluetooth in the codec.<br />
<br />
Put the headset in pairing mode. Replace the bluetooth address below with your headset's and run the python script:<br />
<br />
#!/usr/bin/python<br />
import dbus<br />
bus = dbus.SystemBus()<br />
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')<br />
conn = manager.ActivateService('audio')<br />
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')<br />
path = audio.CreateHeadset('00:0B:2E:39:33:22')<br />
audio.ChangeDefaultHeadset(path)<br />
headset = dbus.Interface (bus.get_object(conn, path), 'org.bluez.audio.Headset')<br />
headset.Connect()<br />
headset.Play()<br />
<br />
Now place a call and try to route it to bluetooth (after it's in progress):<br />
<br />
alsactl -f /etc/gsmbluetooth.state restore<br />
<br />
You may also be able to listen to system audio given the right state file:<br />
<br />
alsactl -f /etc/systembluetooth.state restore<br />
madplay song.mp3<br />
<br />
==Bluetooth Headset on Freerunner ==<br />
<br />
[http://lists.openmoko.org/pipermail/support/2008-September/thread.html#2627 This thread] suggests the following:<br />
<br />
:Turn on bluetooth. If some of the scripts below fail you may need to reboot [https://docs.openmoko.org/trac/ticket/1744 Bluetooth after suspend]<br />
<br />
:Pair your headset according to [http://wiki.bluez.org/ these] instructions or use the script below. The script will change your .asoundrc so make a backup before you run it.<br />
<br />
:http://handheldshell.com/BtConfigure.py<br />
:Put the headset in pairing mode ( this only needs to be done once for each new headset ) and run<br />
BtConfigure.py <br />
<br />
:Download the the following python scripts to set up the audio service and set the headset as the default device:<br />
<br />
:http://handheldshell.com/BtHeadset.py<br />
:http://handheldshell.com/passkey.py<br />
:http://handheldshell.com/BtHeadsetDisconnect.py<br />
:http://handheldshell.com/python-pyalsaaudio_0.3-ml0_armv4t.ipk - can someone add python-pyalsa to the feeds ?<br />
<br />
:Download the the following python scripts if you prefer not to mess around with alsactl:<br />
<br />
:http://handheldshell.com/pymixer.py<br />
:http://handheldshell.com/volume.desktop<br />
<br />
:put pymixer in /usr/bin<br />
<br />
chmod u+x /usr/bin/pymixer.py<br />
<br />
:put volume.desktop in /usr/share/applications<br />
<br />
:Get the [[http://handheldshell.com/gsm_headset.txt alsa state file]] - this state file _WORKS_, mic and earphones are properly routed<br />
<br />
cp gsm_headset.txt /usr/share/openmoko/scenarios/btheadset.state<br />
<br />
:from the home screen run Volume<br />
<br />
:from the terminal run<br />
<br />
BtHeadset.py <br />
<br />
:Wait until it says waiting for call to end, you should hear static in the headset. If you don't something has gone wrong.<br />
<br />
:Now start the call<br />
<br />
:In the volume control switch to the btheadset tab. press restore<br />
<br />
:You should now hear the call in your headset. <br />
<br />
:End the call<br />
<br />
BtHeadsetDisconnect.py <br />
<br />
:This was all done with the 2008-updates image from sept 4. <br />
<br />
:The new scripts rely on a specific format for the .asoundrc . A stanza like this is required :<br />
<br />
pcm.headset {<br />
type bluetooth<br />
device <headset mac><br />
profile "voice"<br />
}<br />
<br />
== Further reading ==<br />
<br />
http://www.holtmann.org/papers/bluetooth/ols2006_slides.pdf<br />
http://wiki.bluez.org/wiki/Audio#org.bluez.Audio<br />
http://www.gentoo.org/doc/en/bluetooth-guide.xml<br />
<br />
{{Languages|Manually_using_Bluetooth}}<br />
<br />
[[Category:Bluetooth| ]]<br />
[[Category:Networking]]<br />
[[Category:Application Developer]]</div>Erinhttp://wiki.openmoko.org/wiki/Manually_using_BluetoothManually using Bluetooth2008-12-02T08:00:01Z<p>Erin: /* OBEX */</p>
<hr />
<div>{{InProgress}}<br />
Bluetooth is one of the core functions of the Neo1973, however it is basically unimplemented on the software side at the moment.<br />
Hardware problems in the P1 phone mean that the CPU has to be active in order to wake on external bluetooth events, which will reduce the battery life to some 2 days at best in standby.<br />
<br />
This page details how to use bluetooth from the command line.<br />
We have quite a lot of plans about what exactly Bluetooth should be used for.<br />
<br />
== Power it up ==<br />
<br />
Power up the adapter by clicking on the bluetooth icon in the top bar and selecting power on.<br />
<br />
The old way to do it is a shell command (for kernels before 2.6.24):<br />
<br />
root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on<br />
<br />
For kernel 2.6.24 (or later) use<br />
<br />
root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br />
<br />
and on the GTA02 *only* (i.e. not on the GTA01) also use<br />
<br />
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
<br />
But nowadays[http://permalink.gmane.org/gmane.comp.hardware.smartphones.userland/165], one should use [[Dbus device API]]s!<br />
<br />
At the shell, "hciconfig" should print information about the adapter if it powered up properly:<br />
<br />
hciconfig<br />
<br />
The devices should show as UP. If not you can use<br />
<br />
hciconfig <device> up<br />
<br />
== Bluetooth Functions ==<br />
<br />
===Configuring Bluetooth on Openmoko 2007.2 (August 27 snapshot with kernel 2.6.21.6-moko11) ===<br />
<br />
In file /etc/bluetooth/hcid.conf you should change the passkey from BlueZ to something numeric. For testing you may use "0000". Also, you can set the name to "Neo (%d)".<br />
<br />
=== Scanning for bluetooth devices ===<br />
<br />
hcitool scan<br />
<br />
This will list the addresses of any discoverable bluetooth devices in the vicinity<br />
<br />
=== passkey agent example ===<br />
<br />
There should be a passkey agent built into openmoko, but for now you can start up the example passkey agent and set the pin code there. This will allow for new pairings to be made when you attempt a connection.<br />
<br />
passkey-agent --default 0000 &<br />
<br />
Note: the passkey-agent is not required in Openmoko 2007.2 with kernel 2.6.21.6 as of at least since August 27 (maybe earlier).<br />
<br />
=== HID (Human Input Device) ===<br />
<br />
==== Being able to use HID devices ====<br />
<br />
Using a bluetooth keyboard with the built-in terminal is a little funky... I can only type into the console using the bt keyboard if the onscreen keyboard is visible. Also, pressing "p" twice on the bt keyboard actually gives you a "q".<br />
<br />
We want to be able to use a bluetooth keyboard to type into the various applications of our Neo1973.<br />
To use a Bluetooth Keyboard type: (11:22:33:44:55:66 is the Address of your BT-Keyboard)<br />
<br />
hidd --connect 11:22:33:44:55:66<br />
<br />
and press "Connect" on your BT-KB. Alternately, if you know that only one BT-Keyboard is within range, you can just:<br />
<br />
hidd --search<br />
<br />
to find and connect to any BT-Keyboard. There are some bluetooth keyboard only support SPP profile can't direct using hidd comannd to connect. Please reference the discussion of this page for more information.<br />
<br />
Tested on:<br />
* [http://www.logitech.com/index.cfm/products/details/US/EN,CRID=2166,CONTENTID=10717 Logitech Dinovo Edge]<br />
* [http://www.logitech.com/index.cfm/keyboards/keyboard_mice_combos/devices/164&cl=us,en Logitech Dinovo Media Desktop (keyboard)]<br />
* [http://www.nokia.es/A4181580 Nokia SU-8W]. Switched on the BT keyboard, scanned for BT address and ran the connect statement above. Works fine.<br />
* [http://blog.russnelson.com/chordite Chordite]. This keyboard uses the Broadcom BCM2042 BT keyboard controller along with a custom driver.<br />
* [http://www.apple.com/keyboard/ Apple's Aluminum Keyboard]. You may have to add 'auth enable; encrypt enable;' to device {} in hcid.conf. Run the passkey agent the first time. --search works to pair and every time after. (Might be obvious for those who have used BT in other spots, but you have to type in y our passkey on the keyboard as the connect is happening, otherwise pairing doesn't take place. I don't think there is a prompt on the Neo for this)<br />
* [http://www.apple.com/support/keyboard/ Apple's white "Wireless Keyboard (original)"] - details may be the same as above. (tested some time ago)<br />
* [http://www.frogpad.com/ FrogPad] - as above<br />
* [http://freedominput.com The freedom keyboard] and its many rebranded models (they look like this: [http://rabenfrost.net/openmoko/keyboard.jpg]) need 'modprobe uinput' to circumvent the 'Can't open input device: No such file or directory (2)' error of 'hidd --search'. It works as of february 7th 2008.<br />
* [http://www.nextag.com/Playstation-3-Logitech-Cordless-564345667/prices-html?nxtg=f8320a24052a-7789F8FE732FF6E3 Logitech Playstation 3 Keyboard] Works well, Mouse pad works.<br />
* [http://corporate.igo.com/product_details.aspx?id=16 iGo Stowaway UltraSlim] (which was apparently discontinued early 2008, but can still be bought in some places) ([[user:ChristW]] I have 2008.8 on it, and using hidd --search to connect to the iGo works perfectly. I also used it to edit a new contact, dial a number and edit a settings text box in [[TangoGPS]]. So far, no problems...)<br />
* [http://www.vkb-support.com/ I-Tech Virtual Laser Keyboard] works. Cursor keys not recognized as such, but produce keycodes than can be mapped.<br />
<br />
==== Acting as HID device ====<br />
<br />
We want to be able to use the Neo as a HID device, being able to use it as controller for presentations. See [[ReMoko]]<br />
<br />
=== RFCOMM ===<br />
<br />
Here's how to connect to an external Bluetooth GPS and read NMEA data (Tested with a Holux GPSSlim236 and a Nokia LD-3W ).<br />
<br />
First, switch on the GPS and identify the BT address:<br />
<br />
hcitool scan<br />
<br />
Then, edit /etc/bluetooth/rfcomm.conf, which by default has all settings commented out, to something like this:<br />
<br />
rfcomm0 {<br />
# Automatically bind the device at startup<br />
bind no;<br />
# Bluetooth address of the device<br />
device 00:11:22:33:44:55;<br />
# RFCOMM channel for the connection (check your GPS docs for details)<br />
channel 1;<br />
# Description of the connection<br />
comment "Bluetooth GPS";<br />
}<br />
<br />
Restart the BT services:<br />
<br />
root@neo:~$ /etc/init.d/bluetooth stop<br />
root@neo:~$ /etc/init.d/bluetooth start<br />
<br />
You should now be able to bind the GPS to /dev/rfcomm0, like this:<br />
<br />
root@neo:~$ rfcomm bind 0<br />
<br />
Confirm the connect:<br />
<br />
root@neo:~$ rfcomm<br />
rfcomm0: 00:11:22:33:44:55 channel 1 clean <br />
<br />
... and watch the NMEA strings coming from your GPS:<br />
<br />
root@neo:~$ cat /dev/rfcomm0 <br />
$GPGGA,111748.000,5907.6964,N,01121.1787,E,1,06,1.2,57.7,M,40.1,M,,0000*6F<br />
$GPRMC,111748.000,A,5907.6964,N,01121.1787,E,0.00,94.94,160807,,,A*50<br />
$GPVTG,94.94,T,,M,0.00,N,0.0,K,A*3D<br />
<br />
If you have nothing better to do, you can now pinpoint my office :-).<br />
<br />
=== OBEX ===<br />
OBEX (abbreviation of OBject EXchange, also termed IrOBEX) is a communications protocol that facilitates the exchange of binary objects between devices. Here is the notes about how to use OBEX to send/receive files via bluetooth in NEO.<br />
<br />
power on bluetooth: <br />
if you use FSO image<br />
root@om-gta02:~# dbus-send --system --dest=org.freesmartphone.odeviced --type=method_call --print-reply /org/freesmartphone/Device/PowerControl/Bluetooth org.freesmartphone.Device.PowerControl.SetPower int32:1<br />
else: (GTA02 only)<br />
root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
<br />
[http://linux.die.net/man/5/hcid.conf hcid.conf] <br />
modify /etc/bluetooth/hcid.conf<br />
<br />
<pre><br />
#<br />
# HCI daemon configuration file.<br />
#<br />
<br />
# HCId options<br />
options {<br />
# Automatically initialize new devices<br />
autoinit yes;<br />
<br />
# Security Manager mode<br />
# none - Security manager disabled<br />
# auto - Use local PIN for incoming connections<br />
# user - Always ask user for a PIN<br />
#<br />
security auto;<br />
<br />
# Pairing mode<br />
# none - Pairing disabled<br />
# multi - Allow pairing with already paired devices<br />
# once - Pair once and deny successive attempts<br />
pairing multi;<br />
<br />
# Default PIN code for incoming connections<br />
passkey "1234";<br />
}<br />
<br />
# Default settings for HCI devices<br />
device {<br />
# Local device name<br />
# %d - device id<br />
# %h - host name<br />
name "%h-%d";<br />
<br />
# Local device class<br />
class 0x000100;<br />
<br />
# Default packet type<br />
pkt_type DH1,DM1,HV1;<br />
<br />
# Inquiry and Page scan<br />
iscan enable; pscan enable;<br />
<br />
# Default link mode<br />
# none - no specific policy <br />
# accept - always accept incoming connections<br />
# master - become master on incoming connections,<br />
# deny role switch on outgoing connections<br />
lm accept;<br />
<br />
# Default link policy<br />
# none - no specific policy<br />
# rswitch - allow role switch<br />
# hold - allow hold mode<br />
# sniff - allow sniff mode<br />
# park - allow park mode<br />
lp rswitch,hold,sniff,park;<br />
}<br />
</pre><br />
<br />
3. all paired devices info are stored in this folder http://linux.die.net/man/8/hcid<br />
root@om-gta02:/var/lib/bluetooth/00:06:6E:16:EB:C7# ls<br />
classes features lastused names panu<br />
config gn manufacturers nap<br />
<br />
4. Display local devices<br />
root@om-gta02:/# hcitool dev<br />
Devices:<br />
hci0 00:06:6E:16:EB:C7<br />
<br />
5. Scan all nearby bluetooth devices<br />
root@om-gta02:~# hcitool scan<br />
Scanning ...<br />
00:11:67:C8:F3:23 daydreamer-0<br />
00:18:C5:42:18:78 Erin Nokia N73<br />
00:1A:92:7A:1E:C2 CHELSEA-PC<br />
00:1D:FD:04:E6:24 Dkay<br />
00:17:83:48:B3:66 HTC_TyTN_II<br />
<br />
6. Browse what kind of services in this device<br />
sdptool browse 00:16:20:60:7C:36<br />
<br />
root@om-gta02:~# sdptool browse 00:18:C5:42:18:78<br />
Browsing 00:18:C5:42:18:78 ...<br />
<br />
Service Name: OBEX File Transfer<br />
Service RecHandle: 0x1005b<br />
Service Class ID List:<br />
"OBEX File Transfer" (0x1106)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 11<br />
"OBEX" (0x0008)<br />
Language Base Attr List:<br />
code_ISO639: 0x454e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"OBEX File Transfer" (0x1106)<br />
Version: 0x0100<br />
<br />
Service Name: OBEX Object Push<br />
Service RecHandle: 0x1005e<br />
Service Class ID List:<br />
"OBEX Object Push" (0x1105)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 9<br />
"OBEX" (0x0008)<br />
Language Base Attr List:<br />
code_ISO639: 0x454e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"OBEX Object Push" (0x1105)<br />
Version: 0x0100<br />
<br />
7. pair with device, default pin is 1234<br />
http://wiki.bluez.org/wiki/PasskeyAgent<br />
<br />
* Changing to discoverable mode and setting the timeout to 60 seconds<br />
$dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetMode string:discoverable<br />
$dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetDiscoverableTimeout uint32:60<br />
<br />
CREATE BONDING:<br />
$dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.CreateBonding string:00:18:C5:42:18:78<br />
$dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.RemoveBonding string:00:18:C5:42:18:78<br />
$dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.ListBondings<br />
<br />
8. install obexpush, obexftp packages<br />
opkg install obexpush, obexftp<br />
<br />
http://www.go2linux.org/linux-command-line-obexftp-man-page<br />
<br />
obexpush: it would lauanch opd, use OBEX, channel 10, store received files in /home/root/ folder<br />
obexftp: list folders, download files, upload files<br />
<br />
=== Networking ===<br />
<br />
==== Using PC's connection from Neo ====<br />
<br />
===== Bluetooth networking with a Linux system =====<br />
<br />
Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br />
<br />
'''On the laptop'''<br />
<br />
* Start bluetooth<br />
/etc/init.d/bluetooth start<br />
<br />
* Start pand as server<br />
pand -s<br />
<br />
* As soon as pand is started on the phone configure your IP address<br />
ip a add 10.0.0.1/24 dev bnep0<br />
ip l set bnep0 up<br />
<br />
* Configure IP forwarding and masquerading to your liking (see [[USB_Networking]]). You can even set up Udev rules to do this for you once the bnep0 interface appears.<br />
<br />
<br />
'''On the Neo'''<br />
<br />
* There is a little script that does the steps below (and retries the pand -c command; I had issues with it not working the first time every time) at [[Bt-net-script]] You shouldn't need the other steps below if you use the script.<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
00:0E:6D:C0:0l:6A Sho<br />
00:20:E0:5A:FE:C8 BlueZ (0)<br />
<br />
* Connect to the laptop pand<br />
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br />
<br />
* Configure your IP address<br />
ip a add 10.0.0.2/24 dev bnep0<br />
ip r add default via 10.0.0.1<br />
<br />
* Sometimes you may need to bring up the bnep0 on the phone as well:<br />
ip l set bnep0 up<br />
* Enjoy<br />
<br />
<br />
*--[[User:Mantis|Mantis]] 18:37, 15 October 2008 (UTC) Note for use on OpenSuse 11.0 - I was getting a connection failure with 'Host is down(112)' errors in /var/log/messages (on neo).<br />
I found that editing /etc/bluetooth/hcid.conf to set 'pscan enable' instead of 'pscan disable' and making passkey consistent with Neo Freerunner made it work.<br />
<br />
Should see log line like<br />
''pand[17965]: New connection from 00:06:6E:XX:XX:XX at bnep0''<br />
<br />
if connection is successful in server's /var/log/messages.<br />
<br />
===== Bluetooth networking with a MacOS X system =====<br />
<br />
Please refer to [[MacOS_X#Bluetooth_2]]<br />
<br />
For using the Neo as a dialup Bluetooth server and the Mac as the client, please see below at [[Manually_using_Bluetooth#PPP_Networking]]<br />
<br />
===== Bluetooth networking with a Windows XP system =====<br />
<br />
This was tested with a Windows XP SP2 on a IBM Thinkpad T41 with the Widcomm BT stack<br />
<br />
* Start bluetooth on Windows XP<br />
<br />
* Enable "Network Access" in the Bluetooth configuration<br />
<br />
* Scan for the Neo and pair with the Neo (right click, select pair)<br />
<br />
<br />
On the Neo<br />
<br />
* Enable PAN support on the Neo by changing Autostart from false to true in /etc/bluetooth/network.service<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
<laptop_bt_address> Thinkpad<br />
...<br />
<br />
<br />
* Connect to the laptop pand<br />
pand -c <laptop_bt_address> -r PANU -d NAP -e bnep0 -A -E -S<br />
(add '-n' to see the pand status messages until you get it right)<br />
<br />
For some reason, I was not able to initiate PAN connections from the Neo, I got 'Permission denied (13)' even when I had explicitly allowed the Neo to connect (right click on Neo icon, set properties, on Authorization tab). But initiating 'PAN User' from Windows worked when executing on Neo:<br />
pand -l -r PANU -d NAP -e bnep0 -A -E -S<br />
(add '-n' to see the pand status messages until you get it right)<br />
<br />
<br />
* Configure your IP address. It should work like when connecting to Linux:<br />
ip a add 10.0.0.2/24 dev bnep0<br />
ip r add default via 10.0.0.1<br />
If this does not work, the IP stacks may have auto-assigned network addresses to themselves. You can look this up with 'ifconfig' on the Neo and with 'ipconfig' on Windows.<br />
<br />
<br />
* You should now be able to ssh/putty from Windows to your Neo. Enjoy!<br />
By setting up the Windows Bluetooth connection properly, it should also be possible to share the Internet Connection of the Windows box with the Neo.<br />
<br />
===== PPP Networking =====<br />
<br />
If you are unable to use the 'BNEP' method described above, you may be able to use [[PPP]] and a DUN (dialup-networking) emulation mode. On the Neo:<br />
<br />
* Edit the /etc/default/bluetooth file and set the following options:<br />
RFCOMM_ENABLE=true<br />
DUND_ENABLE=true<br />
DUND_OPTIONS="--listen --persist call dun"<br />
<br />
* Create an /etc/ppp/peers/dun file with options like the following:<br />
115200<br />
192.168.2.202:192.168.2.200<br />
passive<br />
local<br />
noipdefault<br />
noauth<br />
nodefaultroute<br />
<br />
* Restart bluetooth (/etc/init.d/bluetooth stop ; /etc/init.d/bluetooth start)<br />
<br />
To connect from a MacOS 10.3 client:<br />
<br />
* Open "Applications/Utilities/Bluetooth Serial Utility"<br />
<br />
* Click on "New"<br />
<br />
* Choose a name, then click "Choose Device"<br />
<br />
* Locate your Neo, then select the "LAN Access Point" service. If your device is not found, or if this service does not show up, then you will need to troubleshoot and fix that before continuing. Bluetooth is designed for short-range communication, so make sure that the devices are physically close to each other. <br />
<br />
* Select "Port type: RS-232" and "Show in Network Preferences". Click OK.<br />
<br />
* Open the Network Preferences page then "Show: Network Port Configurations". Enable the new device that you defined in the previous step and drag it to the bottom of the device list (so that it will not interfere with your other network connections)<br />
<br />
* Choose "Show: <your-device-name>", then click "Modem"<br />
<br />
* Select "Null Modem 115200" from the list of available devices. Uncheck "Wait for dial tone" and "Enable error correction and compression in modem". Optionally check "Show modem status in menu bar". <br />
<br />
* Click "Connect". If everything worked, you will end up with a 'ppp0' device on your Mac with a local address of 192.168.2.200 and you will be able to access your Neo at 192.168.2.202.<br />
<br />
===== Bluetooth networking with a Linux system - More secure way =====<br />
<br />
''Check this, probably needs some corrections''<br />
<br />
Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br />
<br />
On the laptop<br />
<br />
* check these options in /etc/bluetooth/hcid.conf<br />
security auto;<br />
passkey "your pin";<br />
lm master;<br />
<br />
* Start bluetooth<br />
# /etc/init.d/bluetooth start<br />
<br />
* Start pand as server<br />
pand --listen --role NAP --encrypt<br />
<br />
* Add in /etc/network/interfaces (see [[USB_Networking]])<br />
auto bnep0<br />
iface bnep0 inet static<br />
address 192.168.1.1<br />
netmask 255.255.255.0<br />
network 192.168.1.0<br />
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.1.0/24<br />
post-up echo 1 > /proc/sys/net/ipv4/ip_forward<br />
post-up iptables -P FORWARD ACCEPT<br />
<br />
On the Neo<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
00:20:E0:5A:FE:C8 laptop<br />
<br />
* Set pin<br />
root@fic-gta01:~$ passkey-agent 'your pin' 00:20:E0:5A:FE:C8 &<br />
<br />
* Connect to the laptop pand<br />
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br />
<br />
* Configure your IP address<br />
root@fic-gta01:~$ ifconfig bnep0 192.168.1.2<br />
root@fic-gta01:~$ route add default gateway 192.168.1.1<br />
<br />
* Enjoy<br />
<br />
==== Using Neo's connection from PC ====<br />
<br />
===== Calling Neo's GPRS modem via Bluetooth =====<br />
<br />
In this mode, Neo would behave like any other phone which can be used from a PC to get a network connection.<br />
<br />
This section not written yet. Has someone set it up?<br />
<br />
===== Sharing existing Neo's connection =====<br />
<br />
In this mode, Neo already has a network connection (GPRS, WLAN, ...), and it should get shared to the PC. This guide is general on how to forward network connection from a machine running Linux to another machine. If interested, please see more information for example at http://www.gentoo.org/doc/en/bluetooth-guide.xml.<br />
<br />
On the PC<br />
# Check with hciconfig you have working Bluetooth<br />
On the Neo<br />
(if on Debian etc., remember modprobe ohci_hcd hci_usb)<br />
# Initialize Bluetooth as told before:<br />
## echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br />
## echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
# install iptables: opkg install http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/iptables_1.3.8-r4.1_armv4t.ipk<br />
# modprobe bnep<br />
# Check that hcid is running both on Neo and PC (Bluetooth 4.x: install bluez-compat)<br />
# Use default passkey "1234" in /etc/bluetooth/hcid.conf<br />
# pand --listen --role NAP --master --autozap # note: after this you might have to the the step 1 below ("On the PC") or the next step of getting the interface up does not work # note2: you could automate pand listener to start automatically when Bluetooth is turned on<br />
# ifconfig bnep0 10.0.5.2 up<br />
# echo 1 > /proc/sys/net/ipv4/ip_forward<br />
# iptables -t nat -A POSTROUTING -j MASQUERADE -o ppp0<br />
On the PC:<br />
# sudo pand --connect <your bluetooth mac address> --service NAP --autozap<br />
# ifconfig bnep0 10.0.5.1 up<br />
# You can test the connection with ping 10.0.5.2<br />
# sudo ip route add default via 10.0.5.2 dev bnep0<br />
# [not automated yet] add GPRS connection's nameservers to /etc/resolv.conf<br />
<br />
== Advanced Audio Distribution Profile (A2DP) ==<br />
<br />
=== A2DP quickie ===<br />
<br />
* If you experience problems with choppyness, try changing your hcid.conf to include "lm accept,master;" and "lp hold,sniff,park;" You may also have to bond (commonly known as 'pairing') your phone and your headset. See http://wiki.bluez.org/wiki/HOWTO/Bonding for details. [[User:Mercury|Mercury]] 17:36, 5 September 2008 (UTC)<br />
<br />
It's now possible (if a little hackish) to stream mp3 to a bluetooth headset. It's a known problem that the playback rate changes (pitch varies). Timing issues are also likely the reason for gaps in playback.<br />
<br />
If the bluez packages are recent enough, you can use a shortcut. I'll document it here and leave the longer version below (the long version also demonstrates the API used by the GUI to manage headsets)<br />
<br />
Create /etc/asound.conf with your bluetooth headset's address filled in:<br />
<br />
pcm.!default {<br />
type bluetooth<br />
device "xx:xx:xx:xx:xx:xx"<br />
}<br />
<br />
then play a song<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay<br />
<br />
or for smoother results...<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:song.wav<br />
aplay song.wav<br />
<br />
=== A2DP ===<br />
<br />
If that doesn't work... all the more hackish... install required packages:<br />
<br />
echo "src/gz python http://www.angstrom-distribution.org/unstable/feed/armv4t/python/" >> /etc/ipkg/angstrom-python.conf <br />
echo "src/gz base http://www.angstrom-distribution.org/unstable/feed/armv4t/base/" >> /etc/ipkg/angstrom-base.conf<br />
ipkg update ; ipkg install python-core python-xml python-dbus bluez-utils bluez-utils-alsa<br />
<br />
Create /etc/asound.conf:<br />
<br />
pcm.!default {<br />
type bluetooth<br />
}<br />
ctl.!default {<br />
type bluetooth<br />
}<br />
pcm.bluetooth {<br />
type bluetooth<br />
}<br />
ctl.bluetooth {<br />
type bluetooth<br />
}<br />
<br />
Run the passkey agent (see above in this page)<br />
<br />
Fill in your bluetooth headset address below and execute the python script (with your headset turned on)<br />
<br />
#!/usr/bin/python<br />
import dbus<br />
bus = dbus.SystemBus()<br />
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')<br />
conn = manager.ActivateService('audio')<br />
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')<br />
path = audio.CreateDevice('00:0D:3C:44:33:22')<br />
audio.ChangeDefaultDevice(path)<br />
sink = dbus.Interface(bus.get_object(conn, path), 'org.bluez.audio.Sink')<br />
sink.Connect()<br />
<br />
FINALLY: play a song<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay<br />
<br />
=== Headset Audio ===<br />
<br />
[[Neo1973_Audio_Subsystem]] has detail about alsa settings and a proposal for audio scenario management.<br />
<br />
To try this out, follow the instructions in the a2dp section to install software and run the passkey agent.<br />
<br />
Remove or disable the stuff you put in asound.conf. When using a voice headset, the application uses the regular system audio device and it gets routed to bluetooth in the codec.<br />
<br />
Put the headset in pairing mode. Replace the bluetooth address below with your headset's and run the python script:<br />
<br />
#!/usr/bin/python<br />
import dbus<br />
bus = dbus.SystemBus()<br />
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')<br />
conn = manager.ActivateService('audio')<br />
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')<br />
path = audio.CreateHeadset('00:0B:2E:39:33:22')<br />
audio.ChangeDefaultHeadset(path)<br />
headset = dbus.Interface (bus.get_object(conn, path), 'org.bluez.audio.Headset')<br />
headset.Connect()<br />
headset.Play()<br />
<br />
Now place a call and try to route it to bluetooth (after it's in progress):<br />
<br />
alsactl -f /etc/gsmbluetooth.state restore<br />
<br />
You may also be able to listen to system audio given the right state file:<br />
<br />
alsactl -f /etc/systembluetooth.state restore<br />
madplay song.mp3<br />
<br />
==Bluetooth Headset on Freerunner ==<br />
<br />
[http://lists.openmoko.org/pipermail/support/2008-September/thread.html#2627 This thread] suggests the following:<br />
<br />
:Turn on bluetooth. If some of the scripts below fail you may need to reboot [https://docs.openmoko.org/trac/ticket/1744 Bluetooth after suspend]<br />
<br />
:Pair your headset according to [http://wiki.bluez.org/ these] instructions or use the script below. The script will change your .asoundrc so make a backup before you run it.<br />
<br />
:http://handheldshell.com/BtConfigure.py<br />
:Put the headset in pairing mode ( this only needs to be done once for each new headset ) and run<br />
BtConfigure.py <br />
<br />
:Download the the following python scripts to set up the audio service and set the headset as the default device:<br />
<br />
:http://handheldshell.com/BtHeadset.py<br />
:http://handheldshell.com/passkey.py<br />
:http://handheldshell.com/BtHeadsetDisconnect.py<br />
:http://handheldshell.com/python-pyalsaaudio_0.3-ml0_armv4t.ipk - can someone add python-pyalsa to the feeds ?<br />
<br />
:Download the the following python scripts if you prefer not to mess around with alsactl:<br />
<br />
:http://handheldshell.com/pymixer.py<br />
:http://handheldshell.com/volume.desktop<br />
<br />
:put pymixer in /usr/bin<br />
<br />
chmod u+x /usr/bin/pymixer.py<br />
<br />
:put volume.desktop in /usr/share/applications<br />
<br />
:Get the [[http://handheldshell.com/gsm_headset.txt alsa state file]] - this state file _WORKS_, mic and earphones are properly routed<br />
<br />
cp gsm_headset.txt /usr/share/openmoko/scenarios/btheadset.state<br />
<br />
:from the home screen run Volume<br />
<br />
:from the terminal run<br />
<br />
BtHeadset.py <br />
<br />
:Wait until it says waiting for call to end, you should hear static in the headset. If you don't something has gone wrong.<br />
<br />
:Now start the call<br />
<br />
:In the volume control switch to the btheadset tab. press restore<br />
<br />
:You should now hear the call in your headset. <br />
<br />
:End the call<br />
<br />
BtHeadsetDisconnect.py <br />
<br />
:This was all done with the 2008-updates image from sept 4. <br />
<br />
:The new scripts rely on a specific format for the .asoundrc . A stanza like this is required :<br />
<br />
pcm.headset {<br />
type bluetooth<br />
device <headset mac><br />
profile "voice"<br />
}<br />
<br />
== Further reading ==<br />
<br />
http://www.holtmann.org/papers/bluetooth/ols2006_slides.pdf<br />
http://wiki.bluez.org/wiki/Audio#org.bluez.Audio<br />
http://www.gentoo.org/doc/en/bluetooth-guide.xml<br />
<br />
{{Languages|Manually_using_Bluetooth}}<br />
<br />
[[Category:Bluetooth| ]]<br />
[[Category:Networking]]<br />
[[Category:Application Developer]]</div>Erinhttp://wiki.openmoko.org/wiki/Manually_using_BluetoothManually using Bluetooth2008-12-02T07:49:38Z<p>Erin: /* OBEX */</p>
<hr />
<div>{{InProgress}}<br />
Bluetooth is one of the core functions of the Neo1973, however it is basically unimplemented on the software side at the moment.<br />
Hardware problems in the P1 phone mean that the CPU has to be active in order to wake on external bluetooth events, which will reduce the battery life to some 2 days at best in standby.<br />
<br />
This page details how to use bluetooth from the command line.<br />
We have quite a lot of plans about what exactly Bluetooth should be used for.<br />
<br />
== Power it up ==<br />
<br />
Power up the adapter by clicking on the bluetooth icon in the top bar and selecting power on.<br />
<br />
The old way to do it is a shell command (for kernels before 2.6.24):<br />
<br />
root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on<br />
<br />
For kernel 2.6.24 (or later) use<br />
<br />
root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br />
<br />
and on the GTA02 *only* (i.e. not on the GTA01) also use<br />
<br />
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
<br />
But nowadays[http://permalink.gmane.org/gmane.comp.hardware.smartphones.userland/165], one should use [[Dbus device API]]s!<br />
<br />
At the shell, "hciconfig" should print information about the adapter if it powered up properly:<br />
<br />
hciconfig<br />
<br />
The devices should show as UP. If not you can use<br />
<br />
hciconfig <device> up<br />
<br />
== Bluetooth Functions ==<br />
<br />
===Configuring Bluetooth on Openmoko 2007.2 (August 27 snapshot with kernel 2.6.21.6-moko11) ===<br />
<br />
In file /etc/bluetooth/hcid.conf you should change the passkey from BlueZ to something numeric. For testing you may use "0000". Also, you can set the name to "Neo (%d)".<br />
<br />
=== Scanning for bluetooth devices ===<br />
<br />
hcitool scan<br />
<br />
This will list the addresses of any discoverable bluetooth devices in the vicinity<br />
<br />
=== passkey agent example ===<br />
<br />
There should be a passkey agent built into openmoko, but for now you can start up the example passkey agent and set the pin code there. This will allow for new pairings to be made when you attempt a connection.<br />
<br />
passkey-agent --default 0000 &<br />
<br />
Note: the passkey-agent is not required in Openmoko 2007.2 with kernel 2.6.21.6 as of at least since August 27 (maybe earlier).<br />
<br />
=== HID (Human Input Device) ===<br />
<br />
==== Being able to use HID devices ====<br />
<br />
Using a bluetooth keyboard with the built-in terminal is a little funky... I can only type into the console using the bt keyboard if the onscreen keyboard is visible. Also, pressing "p" twice on the bt keyboard actually gives you a "q".<br />
<br />
We want to be able to use a bluetooth keyboard to type into the various applications of our Neo1973.<br />
To use a Bluetooth Keyboard type: (11:22:33:44:55:66 is the Address of your BT-Keyboard)<br />
<br />
hidd --connect 11:22:33:44:55:66<br />
<br />
and press "Connect" on your BT-KB. Alternately, if you know that only one BT-Keyboard is within range, you can just:<br />
<br />
hidd --search<br />
<br />
to find and connect to any BT-Keyboard. There are some bluetooth keyboard only support SPP profile can't direct using hidd comannd to connect. Please reference the discussion of this page for more information.<br />
<br />
Tested on:<br />
* [http://www.logitech.com/index.cfm/products/details/US/EN,CRID=2166,CONTENTID=10717 Logitech Dinovo Edge]<br />
* [http://www.logitech.com/index.cfm/keyboards/keyboard_mice_combos/devices/164&cl=us,en Logitech Dinovo Media Desktop (keyboard)]<br />
* [http://www.nokia.es/A4181580 Nokia SU-8W]. Switched on the BT keyboard, scanned for BT address and ran the connect statement above. Works fine.<br />
* [http://blog.russnelson.com/chordite Chordite]. This keyboard uses the Broadcom BCM2042 BT keyboard controller along with a custom driver.<br />
* [http://www.apple.com/keyboard/ Apple's Aluminum Keyboard]. You may have to add 'auth enable; encrypt enable;' to device {} in hcid.conf. Run the passkey agent the first time. --search works to pair and every time after. (Might be obvious for those who have used BT in other spots, but you have to type in y our passkey on the keyboard as the connect is happening, otherwise pairing doesn't take place. I don't think there is a prompt on the Neo for this)<br />
* [http://www.apple.com/support/keyboard/ Apple's white "Wireless Keyboard (original)"] - details may be the same as above. (tested some time ago)<br />
* [http://www.frogpad.com/ FrogPad] - as above<br />
* [http://freedominput.com The freedom keyboard] and its many rebranded models (they look like this: [http://rabenfrost.net/openmoko/keyboard.jpg]) need 'modprobe uinput' to circumvent the 'Can't open input device: No such file or directory (2)' error of 'hidd --search'. It works as of february 7th 2008.<br />
* [http://www.nextag.com/Playstation-3-Logitech-Cordless-564345667/prices-html?nxtg=f8320a24052a-7789F8FE732FF6E3 Logitech Playstation 3 Keyboard] Works well, Mouse pad works.<br />
* [http://corporate.igo.com/product_details.aspx?id=16 iGo Stowaway UltraSlim] (which was apparently discontinued early 2008, but can still be bought in some places) ([[user:ChristW]] I have 2008.8 on it, and using hidd --search to connect to the iGo works perfectly. I also used it to edit a new contact, dial a number and edit a settings text box in [[TangoGPS]]. So far, no problems...)<br />
* [http://www.vkb-support.com/ I-Tech Virtual Laser Keyboard] works. Cursor keys not recognized as such, but produce keycodes than can be mapped.<br />
<br />
==== Acting as HID device ====<br />
<br />
We want to be able to use the Neo as a HID device, being able to use it as controller for presentations. See [[ReMoko]]<br />
<br />
=== RFCOMM ===<br />
<br />
Here's how to connect to an external Bluetooth GPS and read NMEA data (Tested with a Holux GPSSlim236 and a Nokia LD-3W ).<br />
<br />
First, switch on the GPS and identify the BT address:<br />
<br />
hcitool scan<br />
<br />
Then, edit /etc/bluetooth/rfcomm.conf, which by default has all settings commented out, to something like this:<br />
<br />
rfcomm0 {<br />
# Automatically bind the device at startup<br />
bind no;<br />
# Bluetooth address of the device<br />
device 00:11:22:33:44:55;<br />
# RFCOMM channel for the connection (check your GPS docs for details)<br />
channel 1;<br />
# Description of the connection<br />
comment "Bluetooth GPS";<br />
}<br />
<br />
Restart the BT services:<br />
<br />
root@neo:~$ /etc/init.d/bluetooth stop<br />
root@neo:~$ /etc/init.d/bluetooth start<br />
<br />
You should now be able to bind the GPS to /dev/rfcomm0, like this:<br />
<br />
root@neo:~$ rfcomm bind 0<br />
<br />
Confirm the connect:<br />
<br />
root@neo:~$ rfcomm<br />
rfcomm0: 00:11:22:33:44:55 channel 1 clean <br />
<br />
... and watch the NMEA strings coming from your GPS:<br />
<br />
root@neo:~$ cat /dev/rfcomm0 <br />
$GPGGA,111748.000,5907.6964,N,01121.1787,E,1,06,1.2,57.7,M,40.1,M,,0000*6F<br />
$GPRMC,111748.000,A,5907.6964,N,01121.1787,E,0.00,94.94,160807,,,A*50<br />
$GPVTG,94.94,T,,M,0.00,N,0.0,K,A*3D<br />
<br />
If you have nothing better to do, you can now pinpoint my office :-).<br />
<br />
=== OBEX ===<br />
OBEX (abbreviation of OBject EXchange, also termed IrOBEX) is a communications protocol that facilitates the exchange of binary objects between devices.<br />
<br />
1. power on bluetooth:<br />
<br />
root@om-gta02:~# dbus-send --system --dest=org.freesmartphone.odeviced --type=method_call --print-reply /org/freesmartphone/Device/PowerControl/Bluetooth org.freesmartphone.Device.PowerControl.SetPower int32:1<br />
<br />
2. make sure hcid.conf http://linux.die.net/man/5/hcid.conf<br />
/etc/bluetooth/hcid.conf<br />
<br />
#<br />
# HCI daemon configuration file.<br />
#<br />
<br />
# HCId options<br />
options {<br />
# Automatically initialize new devices<br />
autoinit yes;<br />
<br />
# Security Manager mode<br />
# none - Security manager disabled<br />
# auto - Use local PIN for incoming connections<br />
# user - Always ask user for a PIN<br />
#<br />
security user;<br />
<br />
# Pairing mode<br />
# none - Pairing disabled<br />
# multi - Allow pairing with already paired devices<br />
# once - Pair once and deny successive attempts<br />
pairing multi;<br />
<br />
# Default PIN code for incoming connections<br />
passkey "1234";<br />
}<br />
<br />
# Default settings for HCI devices<br />
device {<br />
# Local device name<br />
# %d - device id<br />
# %h - host name<br />
name "%h-%d";<br />
<br />
# Local device class<br />
class 0x000100;<br />
<br />
# Default packet type<br />
pkt_type DH1,DM1,HV1;<br />
<br />
# Inquiry and Page scan<br />
iscan enable; pscan enable;<br />
<br />
# Default link mode<br />
# none - no specific policy <br />
# accept - always accept incoming connections<br />
# master - become master on incoming connections,<br />
# deny role switch on outgoing connections<br />
lm accept;<br />
<br />
# Default link policy<br />
# none - no specific policy<br />
# rswitch - allow role switch<br />
# hold - allow hold mode<br />
# sniff - allow sniff mode<br />
# park - allow park mode<br />
lp rswitch,hold,sniff,park;<br />
}<br />
<br />
3. all paired devices info are stored in this folder http://linux.die.net/man/8/hcid<br />
root@om-gta02:/var/lib/bluetooth/00:06:6E:16:EB:C7# ls<br />
classes features lastused names panu<br />
config gn manufacturers nap<br />
<br />
4. Display local devices<br />
root@om-gta02:/# hcitool dev<br />
Devices:<br />
hci0 00:06:6E:16:EB:C7<br />
<br />
5. Scan all nearby bluetooth devices<br />
root@om-gta02:~# hcitool scan<br />
Scanning ...<br />
00:11:67:C8:F3:23 daydreamer-0<br />
00:18:C5:42:18:78 Erin Nokia N73<br />
00:1A:92:7A:1E:C2 CHELSEA-PC<br />
00:1D:FD:04:E6:24 Dkay<br />
00:17:83:48:B3:66 HTC_TyTN_II<br />
<br />
6. Browse what kind of services in this device<br />
sdptool browse 00:16:20:60:7C:36<br />
<br />
root@om-gta02:~# sdptool browse 00:18:C5:42:18:78<br />
Browsing 00:18:C5:42:18:78 ...<br />
<br />
Service Name: OBEX File Transfer<br />
Service RecHandle: 0x1005b<br />
Service Class ID List:<br />
"OBEX File Transfer" (0x1106)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 11<br />
"OBEX" (0x0008)<br />
Language Base Attr List:<br />
code_ISO639: 0x454e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"OBEX File Transfer" (0x1106)<br />
Version: 0x0100<br />
<br />
Service Name: OBEX Object Push<br />
Service RecHandle: 0x1005e<br />
Service Class ID List:<br />
"OBEX Object Push" (0x1105)<br />
Protocol Descriptor List:<br />
"L2CAP" (0x0100)<br />
"RFCOMM" (0x0003)<br />
Channel: 9<br />
"OBEX" (0x0008)<br />
Language Base Attr List:<br />
code_ISO639: 0x454e<br />
encoding: 0x6a<br />
base_offset: 0x100<br />
Profile Descriptor List:<br />
"OBEX Object Push" (0x1105)<br />
Version: 0x0100<br />
<br />
7. pair with device, default pin is 1234<br />
http://wiki.bluez.org/wiki/PasskeyAgent<br />
<br />
* Changing to discoverable mode and setting the timeout to 60 seconds<br />
$dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetMode string:discoverable<br />
$dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetDiscoverableTimeout uint32:60<br />
<br />
CREATE BONDING:<br />
$dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.CreateBonding string:00:18:C5:42:18:78<br />
$dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.RemoveBonding string:00:18:C5:42:18:78<br />
$dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.ListBondings<br />
<br />
8. install obexpush, obexftp packages<br />
opkg install obexpush, obexftp<br />
<br />
http://www.go2linux.org/linux-command-line-obexftp-man-page<br />
<br />
obexpush: it would lauanch opd, use OBEX, channel 10, store received files in /home/root/ folder<br />
obexftp: list folders, download files, upload files<br />
<br />
=== Networking ===<br />
<br />
==== Using PC's connection from Neo ====<br />
<br />
===== Bluetooth networking with a Linux system =====<br />
<br />
Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br />
<br />
'''On the laptop'''<br />
<br />
* Start bluetooth<br />
/etc/init.d/bluetooth start<br />
<br />
* Start pand as server<br />
pand -s<br />
<br />
* As soon as pand is started on the phone configure your IP address<br />
ip a add 10.0.0.1/24 dev bnep0<br />
ip l set bnep0 up<br />
<br />
* Configure IP forwarding and masquerading to your liking (see [[USB_Networking]]). You can even set up Udev rules to do this for you once the bnep0 interface appears.<br />
<br />
<br />
'''On the Neo'''<br />
<br />
* There is a little script that does the steps below (and retries the pand -c command; I had issues with it not working the first time every time) at [[Bt-net-script]] You shouldn't need the other steps below if you use the script.<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
00:0E:6D:C0:0l:6A Sho<br />
00:20:E0:5A:FE:C8 BlueZ (0)<br />
<br />
* Connect to the laptop pand<br />
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br />
<br />
* Configure your IP address<br />
ip a add 10.0.0.2/24 dev bnep0<br />
ip r add default via 10.0.0.1<br />
<br />
* Sometimes you may need to bring up the bnep0 on the phone as well:<br />
ip l set bnep0 up<br />
* Enjoy<br />
<br />
<br />
*--[[User:Mantis|Mantis]] 18:37, 15 October 2008 (UTC) Note for use on OpenSuse 11.0 - I was getting a connection failure with 'Host is down(112)' errors in /var/log/messages (on neo).<br />
I found that editing /etc/bluetooth/hcid.conf to set 'pscan enable' instead of 'pscan disable' and making passkey consistent with Neo Freerunner made it work.<br />
<br />
Should see log line like<br />
''pand[17965]: New connection from 00:06:6E:XX:XX:XX at bnep0''<br />
<br />
if connection is successful in server's /var/log/messages.<br />
<br />
===== Bluetooth networking with a MacOS X system =====<br />
<br />
Please refer to [[MacOS_X#Bluetooth_2]]<br />
<br />
For using the Neo as a dialup Bluetooth server and the Mac as the client, please see below at [[Manually_using_Bluetooth#PPP_Networking]]<br />
<br />
===== Bluetooth networking with a Windows XP system =====<br />
<br />
This was tested with a Windows XP SP2 on a IBM Thinkpad T41 with the Widcomm BT stack<br />
<br />
* Start bluetooth on Windows XP<br />
<br />
* Enable "Network Access" in the Bluetooth configuration<br />
<br />
* Scan for the Neo and pair with the Neo (right click, select pair)<br />
<br />
<br />
On the Neo<br />
<br />
* Enable PAN support on the Neo by changing Autostart from false to true in /etc/bluetooth/network.service<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
<laptop_bt_address> Thinkpad<br />
...<br />
<br />
<br />
* Connect to the laptop pand<br />
pand -c <laptop_bt_address> -r PANU -d NAP -e bnep0 -A -E -S<br />
(add '-n' to see the pand status messages until you get it right)<br />
<br />
For some reason, I was not able to initiate PAN connections from the Neo, I got 'Permission denied (13)' even when I had explicitly allowed the Neo to connect (right click on Neo icon, set properties, on Authorization tab). But initiating 'PAN User' from Windows worked when executing on Neo:<br />
pand -l -r PANU -d NAP -e bnep0 -A -E -S<br />
(add '-n' to see the pand status messages until you get it right)<br />
<br />
<br />
* Configure your IP address. It should work like when connecting to Linux:<br />
ip a add 10.0.0.2/24 dev bnep0<br />
ip r add default via 10.0.0.1<br />
If this does not work, the IP stacks may have auto-assigned network addresses to themselves. You can look this up with 'ifconfig' on the Neo and with 'ipconfig' on Windows.<br />
<br />
<br />
* You should now be able to ssh/putty from Windows to your Neo. Enjoy!<br />
By setting up the Windows Bluetooth connection properly, it should also be possible to share the Internet Connection of the Windows box with the Neo.<br />
<br />
===== PPP Networking =====<br />
<br />
If you are unable to use the 'BNEP' method described above, you may be able to use [[PPP]] and a DUN (dialup-networking) emulation mode. On the Neo:<br />
<br />
* Edit the /etc/default/bluetooth file and set the following options:<br />
RFCOMM_ENABLE=true<br />
DUND_ENABLE=true<br />
DUND_OPTIONS="--listen --persist call dun"<br />
<br />
* Create an /etc/ppp/peers/dun file with options like the following:<br />
115200<br />
192.168.2.202:192.168.2.200<br />
passive<br />
local<br />
noipdefault<br />
noauth<br />
nodefaultroute<br />
<br />
* Restart bluetooth (/etc/init.d/bluetooth stop ; /etc/init.d/bluetooth start)<br />
<br />
To connect from a MacOS 10.3 client:<br />
<br />
* Open "Applications/Utilities/Bluetooth Serial Utility"<br />
<br />
* Click on "New"<br />
<br />
* Choose a name, then click "Choose Device"<br />
<br />
* Locate your Neo, then select the "LAN Access Point" service. If your device is not found, or if this service does not show up, then you will need to troubleshoot and fix that before continuing. Bluetooth is designed for short-range communication, so make sure that the devices are physically close to each other. <br />
<br />
* Select "Port type: RS-232" and "Show in Network Preferences". Click OK.<br />
<br />
* Open the Network Preferences page then "Show: Network Port Configurations". Enable the new device that you defined in the previous step and drag it to the bottom of the device list (so that it will not interfere with your other network connections)<br />
<br />
* Choose "Show: <your-device-name>", then click "Modem"<br />
<br />
* Select "Null Modem 115200" from the list of available devices. Uncheck "Wait for dial tone" and "Enable error correction and compression in modem". Optionally check "Show modem status in menu bar". <br />
<br />
* Click "Connect". If everything worked, you will end up with a 'ppp0' device on your Mac with a local address of 192.168.2.200 and you will be able to access your Neo at 192.168.2.202.<br />
<br />
===== Bluetooth networking with a Linux system - More secure way =====<br />
<br />
''Check this, probably needs some corrections''<br />
<br />
Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br />
<br />
On the laptop<br />
<br />
* check these options in /etc/bluetooth/hcid.conf<br />
security auto;<br />
passkey "your pin";<br />
lm master;<br />
<br />
* Start bluetooth<br />
# /etc/init.d/bluetooth start<br />
<br />
* Start pand as server<br />
pand --listen --role NAP --encrypt<br />
<br />
* Add in /etc/network/interfaces (see [[USB_Networking]])<br />
auto bnep0<br />
iface bnep0 inet static<br />
address 192.168.1.1<br />
netmask 255.255.255.0<br />
network 192.168.1.0<br />
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.1.0/24<br />
post-up echo 1 > /proc/sys/net/ipv4/ip_forward<br />
post-up iptables -P FORWARD ACCEPT<br />
<br />
On the Neo<br />
<br />
* Power on bluetooth (see above)<br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
00:20:E0:5A:FE:C8 laptop<br />
<br />
* Set pin<br />
root@fic-gta01:~$ passkey-agent 'your pin' 00:20:E0:5A:FE:C8 &<br />
<br />
* Connect to the laptop pand<br />
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br />
<br />
* Configure your IP address<br />
root@fic-gta01:~$ ifconfig bnep0 192.168.1.2<br />
root@fic-gta01:~$ route add default gateway 192.168.1.1<br />
<br />
* Enjoy<br />
<br />
==== Using Neo's connection from PC ====<br />
<br />
===== Calling Neo's GPRS modem via Bluetooth =====<br />
<br />
In this mode, Neo would behave like any other phone which can be used from a PC to get a network connection.<br />
<br />
This section not written yet. Has someone set it up?<br />
<br />
===== Sharing existing Neo's connection =====<br />
<br />
In this mode, Neo already has a network connection (GPRS, WLAN, ...), and it should get shared to the PC. This guide is general on how to forward network connection from a machine running Linux to another machine. If interested, please see more information for example at http://www.gentoo.org/doc/en/bluetooth-guide.xml.<br />
<br />
On the PC<br />
# Check with hciconfig you have working Bluetooth<br />
On the Neo<br />
(if on Debian etc., remember modprobe ohci_hcd hci_usb)<br />
# Initialize Bluetooth as told before:<br />
## echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br />
## echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br />
# install iptables: opkg install http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/iptables_1.3.8-r4.1_armv4t.ipk<br />
# modprobe bnep<br />
# Check that hcid is running both on Neo and PC (Bluetooth 4.x: install bluez-compat)<br />
# Use default passkey "1234" in /etc/bluetooth/hcid.conf<br />
# pand --listen --role NAP --master --autozap # note: after this you might have to the the step 1 below ("On the PC") or the next step of getting the interface up does not work # note2: you could automate pand listener to start automatically when Bluetooth is turned on<br />
# ifconfig bnep0 10.0.5.2 up<br />
# echo 1 > /proc/sys/net/ipv4/ip_forward<br />
# iptables -t nat -A POSTROUTING -j MASQUERADE -o ppp0<br />
On the PC:<br />
# sudo pand --connect <your bluetooth mac address> --service NAP --autozap<br />
# ifconfig bnep0 10.0.5.1 up<br />
# You can test the connection with ping 10.0.5.2<br />
# sudo ip route add default via 10.0.5.2 dev bnep0<br />
# [not automated yet] add GPRS connection's nameservers to /etc/resolv.conf<br />
<br />
== Advanced Audio Distribution Profile (A2DP) ==<br />
<br />
=== A2DP quickie ===<br />
<br />
* If you experience problems with choppyness, try changing your hcid.conf to include "lm accept,master;" and "lp hold,sniff,park;" You may also have to bond (commonly known as 'pairing') your phone and your headset. See http://wiki.bluez.org/wiki/HOWTO/Bonding for details. [[User:Mercury|Mercury]] 17:36, 5 September 2008 (UTC)<br />
<br />
It's now possible (if a little hackish) to stream mp3 to a bluetooth headset. It's a known problem that the playback rate changes (pitch varies). Timing issues are also likely the reason for gaps in playback.<br />
<br />
If the bluez packages are recent enough, you can use a shortcut. I'll document it here and leave the longer version below (the long version also demonstrates the API used by the GUI to manage headsets)<br />
<br />
Create /etc/asound.conf with your bluetooth headset's address filled in:<br />
<br />
pcm.!default {<br />
type bluetooth<br />
device "xx:xx:xx:xx:xx:xx"<br />
}<br />
<br />
then play a song<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay<br />
<br />
or for smoother results...<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:song.wav<br />
aplay song.wav<br />
<br />
=== A2DP ===<br />
<br />
If that doesn't work... all the more hackish... install required packages:<br />
<br />
echo "src/gz python http://www.angstrom-distribution.org/unstable/feed/armv4t/python/" >> /etc/ipkg/angstrom-python.conf <br />
echo "src/gz base http://www.angstrom-distribution.org/unstable/feed/armv4t/base/" >> /etc/ipkg/angstrom-base.conf<br />
ipkg update ; ipkg install python-core python-xml python-dbus bluez-utils bluez-utils-alsa<br />
<br />
Create /etc/asound.conf:<br />
<br />
pcm.!default {<br />
type bluetooth<br />
}<br />
ctl.!default {<br />
type bluetooth<br />
}<br />
pcm.bluetooth {<br />
type bluetooth<br />
}<br />
ctl.bluetooth {<br />
type bluetooth<br />
}<br />
<br />
Run the passkey agent (see above in this page)<br />
<br />
Fill in your bluetooth headset address below and execute the python script (with your headset turned on)<br />
<br />
#!/usr/bin/python<br />
import dbus<br />
bus = dbus.SystemBus()<br />
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')<br />
conn = manager.ActivateService('audio')<br />
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')<br />
path = audio.CreateDevice('00:0D:3C:44:33:22')<br />
audio.ChangeDefaultDevice(path)<br />
sink = dbus.Interface(bus.get_object(conn, path), 'org.bluez.audio.Sink')<br />
sink.Connect()<br />
<br />
FINALLY: play a song<br />
<br />
madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay<br />
<br />
=== Headset Audio ===<br />
<br />
[[Neo1973_Audio_Subsystem]] has detail about alsa settings and a proposal for audio scenario management.<br />
<br />
To try this out, follow the instructions in the a2dp section to install software and run the passkey agent.<br />
<br />
Remove or disable the stuff you put in asound.conf. When using a voice headset, the application uses the regular system audio device and it gets routed to bluetooth in the codec.<br />
<br />
Put the headset in pairing mode. Replace the bluetooth address below with your headset's and run the python script:<br />
<br />
#!/usr/bin/python<br />
import dbus<br />
bus = dbus.SystemBus()<br />
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')<br />
conn = manager.ActivateService('audio')<br />
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')<br />
path = audio.CreateHeadset('00:0B:2E:39:33:22')<br />
audio.ChangeDefaultHeadset(path)<br />
headset = dbus.Interface (bus.get_object(conn, path), 'org.bluez.audio.Headset')<br />
headset.Connect()<br />
headset.Play()<br />
<br />
Now place a call and try to route it to bluetooth (after it's in progress):<br />
<br />
alsactl -f /etc/gsmbluetooth.state restore<br />
<br />
You may also be able to listen to system audio given the right state file:<br />
<br />
alsactl -f /etc/systembluetooth.state restore<br />
madplay song.mp3<br />
<br />
==Bluetooth Headset on Freerunner ==<br />
<br />
[http://lists.openmoko.org/pipermail/support/2008-September/thread.html#2627 This thread] suggests the following:<br />
<br />
:Turn on bluetooth. If some of the scripts below fail you may need to reboot [https://docs.openmoko.org/trac/ticket/1744 Bluetooth after suspend]<br />
<br />
:Pair your headset according to [http://wiki.bluez.org/ these] instructions or use the script below. The script will change your .asoundrc so make a backup before you run it.<br />
<br />
:http://handheldshell.com/BtConfigure.py<br />
:Put the headset in pairing mode ( this only needs to be done once for each new headset ) and run<br />
BtConfigure.py <br />
<br />
:Download the the following python scripts to set up the audio service and set the headset as the default device:<br />
<br />
:http://handheldshell.com/BtHeadset.py<br />
:http://handheldshell.com/passkey.py<br />
:http://handheldshell.com/BtHeadsetDisconnect.py<br />
:http://handheldshell.com/python-pyalsaaudio_0.3-ml0_armv4t.ipk - can someone add python-pyalsa to the feeds ?<br />
<br />
:Download the the following python scripts if you prefer not to mess around with alsactl:<br />
<br />
:http://handheldshell.com/pymixer.py<br />
:http://handheldshell.com/volume.desktop<br />
<br />
:put pymixer in /usr/bin<br />
<br />
chmod u+x /usr/bin/pymixer.py<br />
<br />
:put volume.desktop in /usr/share/applications<br />
<br />
:Get the [[http://handheldshell.com/gsm_headset.txt alsa state file]] - this state file _WORKS_, mic and earphones are properly routed<br />
<br />
cp gsm_headset.txt /usr/share/openmoko/scenarios/btheadset.state<br />
<br />
:from the home screen run Volume<br />
<br />
:from the terminal run<br />
<br />
BtHeadset.py <br />
<br />
:Wait until it says waiting for call to end, you should hear static in the headset. If you don't something has gone wrong.<br />
<br />
:Now start the call<br />
<br />
:In the volume control switch to the btheadset tab. press restore<br />
<br />
:You should now hear the call in your headset. <br />
<br />
:End the call<br />
<br />
BtHeadsetDisconnect.py <br />
<br />
:This was all done with the 2008-updates image from sept 4. <br />
<br />
:The new scripts rely on a specific format for the .asoundrc . A stanza like this is required :<br />
<br />
pcm.headset {<br />
type bluetooth<br />
device <headset mac><br />
profile "voice"<br />
}<br />
<br />
== Further reading ==<br />
<br />
http://www.holtmann.org/papers/bluetooth/ols2006_slides.pdf<br />
http://wiki.bluez.org/wiki/Audio#org.bluez.Audio<br />
http://www.gentoo.org/doc/en/bluetooth-guide.xml<br />
<br />
{{Languages|Manually_using_Bluetooth}}<br />
<br />
[[Category:Bluetooth| ]]<br />
[[Category:Networking]]<br />
[[Category:Application Developer]]</div>Erinhttp://wiki.openmoko.org/wiki/Community_Updates/2008-11-16Community Updates/2008-11-162008-11-19T03:11:36Z<p>Erin: /* Infrastructure: X and OE */</p>
<hr />
<div>Hello everybody, and welcome to the Openmoko Community Newsletter, for the <br />
November 3th to November 16th timespan. During these two weeks, we had [[FSO]] milestone IV and a testing [[SHR]] image released. Openmoko pulled the download server offline due to an mp3 copyright issue, they are rebuilding everything without any questionable codecs. Werner announced a firmware update for the GSM chip that will allow 3G chips compatibility. And there is movement again towards a better driver for the glamo graphic chip.<br />
<br />
== Distributions ==<br />
<br />
FSO team released Milestone IV 'Homework', see the [[OpenmokoFramework/Status Update 5]]. To accomodate the forthcoming release of other FSO API consumers like paroli or the SHR phone stack, from now on three FSO-compliant images are build:<br />
# fso-console-image: minimal system with frameworkd, no user interface manager.<br />
# fso-illume-image: everything in console-image plus X-Window, plus Enlightenment plus Illume window manager.<br />
# fso-image: everything in illume-image plus Zhone. Can be used for phone calls. Like previous milestones. But Zhone is going to be faded out.<br />
<br />
[[Debian]]: Joachim announced that the preferred installer script is now [http://git.debian.org/?p=pkg-fso/files.git;a=blob_plain;f=install.sh the one in the git]. The [http://pkg-fso.alioth.debian.org/freerunner/install.sh old URL] does redirect to it. Thanks mostly to Luca “Gismo” Capello’s great work, recent improvements include:<br />
# The use of the general auto-login script “nodm” instead of zhone-session. Session configuration can now be done by modifying /root/.xsession.<br />
# Device independent frameworkd and accompanying configuration packages. If apt-get upgrade breaks your FreeRunner, try to run ''apt-get install fso-config-gta02''.<br />
# openmoko-panel-plugin installed by default (running in trayer), to provide keyboard toggle and device control.<br />
# The use of the packaged kernel instead of wget/tar. To get this going, ''run apt-get install linux-image-2.6.24-openmoko-gta02''<br />
<br />
[[SHR]] is getting closer to a first milestone release. According to BillK and others who kindly tested the latest version, the ergonomy feels generally better than other distros. But its early days yet, if you need a phone use 2008.9. Julien Cassignol [http://lists.openmoko.org/nabble.html#nabble-f832940 invites the braves out here] to install a preview [http://shr.bearstech.com/shr-testing/images/neo1973/ SHR-testing] ([http://shr.bearstech.com/trac/wiki/Get_Started wiki help]) and join the Internet Relay Chat on #openmoko-cdevel on FreeNode.<br />
<br />
[[FDOM]] is considering wether to [http://lists.projects.openmoko.org/pipermail/fdom-development/2008-November/000178.html move to OpenEmbeded], as this would solve the source redistribution issue nicely.<br />
<br />
On November 12th, http://downloads.openmoko.org/releases/ were taken offline due to the discovery of an [http://lists.openmoko.org/pipermail/community/2008-November/035635.html MP3 licensing issue]. Openmoko collaborates with the Software Freedom Law Center in New York on this kind of issues.<br />
<br />
== Applications ==<br />
<br />
[http://www.cs.helsinki.fi/u/rantalai/freerunner/numptyphysics/ Aapo] compiled a newer version of [[Numptyphysics]] package on Debian, which can be played landscaped, without keyboard and it uses same datafiles than any other numptyphysics-port is at: http://www.opkg.org/package_3.html.<br />
<br />
Signal Applications To Any (Audio) Network, or, ehm, {{opkg.org|34|SATAN}}, was born... This is a tracker to create simple music, or just jam on the train, bus or café.<br />
<br />
Debian users rejoice: [http://lists.openmoko.org/pipermail/community/2008-November/035251.html openmoko-panel-plugin reaches 0.5]. Show and modify you the state of the hardware in you FreeRunner(i.e. gsm, gps ...) with any gtk based windowmanager (i.e. xfce). ([http://lists.openmoko.org/pipermail/community/2008-November/035251.html thread], [http://pkg-fso.alioth.debian.org/debian/pool/main/o/openmoko-panel-plugin/ download]).<br />
<br />
[http://www.centerim.org/ Centerim], a terminal-based instant messager, ported on the freerunner ([http://www.opkg.org/package_32.html package], [http://www.cs.helsinki.fi/u/rantalai/freerunner/centerim/ port page])<br />
<br />
In the wiki, the [[Applications]] and [[Distributions]] pages were revised. We are having trouble with an engine extention that eats up whitespace, the workaround is to wrap pre formatted text in<br />
<br />
<nowiki><pre></nowiki> tags. The thematic ''List of X applications'' pages are going away, we want to keep just one big directory style application linkfarm. The idea is that presenting applications in organized ways is better done by http://opkg.org . This directory already has 45 entries, please register and go populate it.<br />
<br />
== Infrastructure: X and OE ==<br />
<br />
Reports from the [http://n2.nabble.com/Optimization-team-update-%2811-02-%7E-11-08%29-tp1472782p1472782.html optimization team] have been landing weekly. They include patches to fix {{Ticket|1884}} ([suspend/resume] if press power batton right after suspend, the device won't wake up) and patches to [http://git.openmoko.org/?p=qtopia.git;a=commit;h=beb921e93e33c18f451247636a3b460a7c1da361 improve the network registering time]. The openmoko-mediaplayer2: dependency on pulseaudio was removed to use alsa instead. And various utilities should appear shortly in the distributions, including telnet, wget, tcptraceroute, wmiconfig, a bunch of X system fonts and more.<br />
<br />
The lack of [http://lists.openmoko.org/pipermail/community/2008-November/035748.html GLamo OpenGL] is still a major dark hole on the FreeRunner's phone liberation front. Hacker culture factoid: did you know that as a software project X is older and about as large as the kernel with a penguin on it, but has an order of magnitude less contributors to it ?<br />
<br />
Openmoko will share the glamo documentation with any serious programmer out there who wants to improve the glamo driver. Wolfgang [http://lists.openmoko.org/pipermail/community/2008-November/035768.html wrote:]<br />
''If someone wants to seriously develop for the glamo, please get in touch with me and we will find a legally correct way to extend the smedia documentation to you. In fact we have done that in a few cases before already, but I'm not<br />
sure how much actual codes have come out of that. I think very little ;-) So we need some really serious coders that don't mind a tough challenge.''<br />
<br />
Following that call, several community members expressed interest, and Andy made a few [http://lists.openmoko.org/pipermail/community/2008-November/035903.html suggestions]. Work on 2D/3D acceleration should be coordinated with Graeme (XorA), who [http://lists.openmoko.org/pipermail/community/2008-November/035551.html is updating the X.org] version in OpenEmbeded to 7.4 (it now completely autodetects hardware on GTA02 with the Framebuffer driver). Over the next few weeks he will be working on Xglamo to bring it into the Xorg family of drivers (''kdrive'' is an evolutionary deadend).<br />
<br />
== Kernel ==<br />
<br />
The kernel guys are working to switch from the ''stable'' to the ''stable-tracking'' branch. The rationale is that a newer 2.6.28 kernel should improve resume/suspend. And staying closer to upstream allows to spot problems early and one at a time, while branching every X months implies a great effort to jump the gap.<br />
* NAND/ECC kernel issues are supposedly solved by [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-November/006279.html this patch].<br />
* Warnings from WLAN driver about "warn_on_slowpath" are gone.<br />
* Page flipping support added to glamo (seem to be a framebuffer feature, necessary for Android).<br />
* Accelerometers are working but the driver is still under discussion.<br />
* Glamo GPIO is still not working on resume, leading to WSOD.<br />
At the same time, openmoko's kernels and bootloaders are gearing up to support more devices beyond GTA01 and GTA02: GTA03 and another non-Openmoko ARM-based freephone, the E-TEN glofiish M800.<br />
<br />
What is coming in the future:<br />
* Improve WLAN latency: On the same wireless network on which the Neo has an average ping of 70+ms, with large excursions, where a laptop gets an average of 1.7ms and a maximum of about 5-6ms.<br />
* The [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-November/006256.html replacement of the Atheros SDIO stack underneath the WLAN driver with the Linux SDIO stack] is planned but not scheduled.<br />
* Jonas Bonn is working on [http://kerneltrap.org/mailarchive/openmoko-kernel/2008/11/5/3922964 Variable Clock Frequency and Power Saving].<br />
* A /sys interface to disable the touchscreen<br />
* Userspace breakage, especially in /sys, when the kernel jumps from 2.6.26 to 2.6.28.<br />
<br />
== Hardware ==<br />
<br />
And I thought that we were waiting on Sean et al. to give mechanical legs to the Neo. I was so [http://tw.youtube.com/watch?v=SG3fAHFNs2c literally wrong] ! ([http://lists.openmoko.org/pipermail/community/2008-November/035522.html thread]).<br />
<br />
Werner [http://lists.openmoko.org/pipermail/devel/2008-November/003150.html announced] a coming upgrade to the Calypso GSM chip firmware (meanwhile, [[GSM/Flashing|the wiki]] is your friend). The goal with the ''moko9'' firmware is to fix {{Ticket|666}} and introduce a new command AT+CSIM. Than means 3G SIM cards should work. There will be a self-contained update image that can be copied to a uSD card, then booted from there leading to a simple GUI to kick off the upgrade. Release date given: 'soon'. Fixing registration bouncing is not scheduled for this update.<br />
<br />
The [http://lists.openmoko.org/pipermail/hardware/2008-October/000768.html GSM-noise buzz issue] is a serious defect that make some phones practically unusable. Electrical engineering is black magick to me, but I get that Joerg and other OM hardware engineers have traced which circuit were interfering, and are experimenting [http://lists.openmoko.org/pipermail/hardware/2008-October/000753.html hardware fixes]. It is unclear how this applies to the A7 hardware revision which seems due soon. Problems with the poor low-frequency audio response with low-impedance headphones are [http://lists.openmoko.org/nabble.html#nabble-td1502610 still with us].<br />
<br />
[[Category:Community]]</div>Erinhttp://wiki.openmoko.org/wiki/Improving_user_experienceImproving user experience2008-10-21T03:13:36Z<p>Erin: /* ToDO */</p>
<hr />
<div>'''[http://lists.openmoko.org/nabble.html#nabble-td1336450 Please check the discussion page]'''<br />
<br />
=Overview=<br />
<br />
Like Wolfgang said in http://n2.nabble.com/Weekly-Engineering-News-41-2008-td1336450.html , Openmoko assembled a team to focus on improving the user experience. The focus and coverage of this group is:<br />
<br />
* We improve the current stack instead of creating new features.<br />
* Prefer stuffs which could be brought over to gta03 instead of gta02/om2008 specific.<br />
* Won't work on om2007 stack. Won't do hardware.<br />
* May cooperate with Paroli, FSO or system team but we're not them.<br />
* Will work on Qtopia but with lower priority.<br />
<br />
=ToDO=<br />
<br />
Here is the current ''draft'' and it will be updated frequently.<br />
<br />
* call quality +1<br />
** echo (in testing [http://docs.openmoko.org/trac/ticket/1267 #1267])<br />
** volume (alsa-state?)<br />
* Reduce boot time ([http://docs.openmoko.org/trac/ticket/69 #69],[http://docs.openmoko.org/trac/ticket/1722 #1722])<br />
* Optimize the touch screen driver on freerunner for finger usage.(in testing [http://docs.openmoko.org/trac/ticket/2031 #2031])<br />
* A generic python loader to enhance the start up time of python scripts.<br />
* qtopia<br />
** bugfix<br />
** program startup speed<br />
** response time<br />
* network<br />
** scripts: resolv.conf, etc.<br />
<br />
==Evaluating==<br />
<br />
* Reliably make and receive phone calls and SMS messages<br />
* suspend/resume<br />
** resume reliably ([http://docs.openmoko.org/trac/ticket/1884 #1884],[http://docs.openmoko.org/trac/ticket/1991 #1991])<br />
** take a screenshot before suspend. display it on screen first thing on resume.<br />
** do not suspend when usb connected, qtopia indexing, etc.<br />
* qtopia<br />
** change the button order of "end call" or "ans call"<br />
** put speaker button on the dialer app<br />
* peripherals<br />
** LED & button behavior [[FreeRunner/Buttons and LEDs]], [[FreeRunner LED signals]]<br />
***illume: disable suspend by power button when screen blanked<br />
* devices (command line improvement first)<br />
** GPRS<br />
** bluetooth<br />
** wifi userspace<br />
* misc<br />
** opkg: faster algorithm<br />
<br />
== Other Wish list==<br />
<br />
See [[Wish list from community]]<br />
<br />
[[Category:Community]]</div>Erinhttp://wiki.openmoko.org/wiki/Who_is_WhoWho is Who2008-10-17T07:03:22Z<p>Erin: /* Officials members of the Openmoko Team */</p>
<hr />
<div>If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:<br />
* Who is who?<br />
* Who can I trust when they say something?<br />
<br />
So I propose to fill out this list to help people get to know each other.<br />
<br />
== Officials members of the Openmoko Team ==<br />
<br />
The Openmoko team (alphabetical by last name):<br />
{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"<br />
! Name !! email !! Wiki username !! IRC nickname !! Position<br />
|-<br />
| Allen Chang || || {{user|allen_chang}} || || GTA Hardware Engineer<br />
|-<br />
| Andy Green || ''andy'' at openmoko dot ''com'' || {{user|warmcat}} || agreen || Software Developer<br />
|-<br />
| Anthony Chang || || || || Software Developer<br />
|-<br />
| Candy Chou || || {{user|candy_chou}} || || GTA/HXD Hardware Engineer<br />
|-<br />
| Dkay Chen || || {{user|dkay_chen}} || || GTA/HXD Hardware Engineer<br />
|-<br />
| Jeremy Chang || || || || Software Developer<br />
|-<br />
| Jollen Chen || || || || Marketing<br />
|-<br />
| Tick Chen || || || || Software Developer<br />
|-<br />
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || ||<br />
|-<br />
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer<br />
|-<br />
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer<br />
|-<br />
| Graeme Gregory || ''graeme'' at openmoko dot ''org'' || || XorA ||<br />
|-<br />
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || raster || (Left Openmoko. Here for archives.)<br />
|-<br />
| Matt Hsu || || {{user|Matt}} || || Software Developer<br />
|-<br />
| Wendy Hung || || || || Testing<br />
|-<br />
| Regina Kim || || || || Testing<br />
|-<br />
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager<br />
|-<br />
| Michael 'Mickey' Lauer || || {{user|Mickey}} || || Software Developer<br />
|-<br />
| John Lee || || || || Software Developer<br />
|-<br />
| Tim Lee || || {{user|Tim}} || || Hardware Manager<br />
|-<br />
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer<br />
|-<br />
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || || || Software Developer<br />
|-<br />
| Jan 'Shoragan' Luebbe || || || || Openmoko student (part-time)<br />
|-<br />
| Steven Mosher || || {{user|steve}} || || Vice President of Marketing<br />
|-<br />
| Sean Moss-Pultz || || {{user|Sean}} || || CEO<br />
|-<br />
| Shawn Lin || || {{user|shawn_lin}} || || RF Engineer<br />
|-<br />
| Joerg Reisenweber || || {{user|jOERG}} || || Hardware Engineer<br />
|-<br />
| Michael Shiloh || ''michael'' at openmoko dot ''org'' || {{user|Michaelshiloh}} || || Head of Developer Relations<br />
|-<br />
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering<br />
|-<br />
| Joachim Steiger || ''roh'' at openmoko dot ''org'' || {{user|Roh}} || roh || Central Services<br />
|-<br />
| Harry Tsai || ''harry'' at openmoko dot ''com'' || || || Vice President of Sales<br />
|-<br />
| Neng-Yu 'Tony' Tu || || {{user|Tony Tu}} || || Software Developer<br />
|-<br />
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || {{user|Coolcat}} || || Wiki editor<br />
|-<br />
| Harald Welte || ''laforge'' at openmoko dot ''org'' || {{user|HaraldWelte}} || LaF0rge || (Left Openmoko. Here for archives.)<br />
|-<br />
| Daniel 'Alphaone' Willmann || || {{user|DanielWillmann}} || || Software Developer<br />
|-<br />
| Thomas Wood || || {{user|ThomasWood}} || ||<br />
|-<br />
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer<br />
|-<br />
| Erin Yeh || ''erin_yueh'' at openmoko dot ''org''||{{user|erin}} || || Software Developer<br />
|}<br />
<br />
== Proeminent community members ==<br />
<br />
Only add people who made a significant contribution to the Openmoko community.<br />
<br />
{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"<br />
! Name !! email !! Wiki username !! IRC nickname !! Position<br />
|-<br />
| Lorn Potter || ''lpotter'' at ''trolltech'' dot ''com'' || || lpotter || Qtopia developer<br />
|-<br />
| Rod Whitby || || {{user|RodWhitby}} || rwhitby || [[MokoMakefile]] author<br />
|}<br />
<br />
<br />
<br />
[[Category:Openmoko Inc]]</div>Erinhttp://wiki.openmoko.org/wiki/Om_2008_LocationsOm 2008 Locations2008-09-10T07:35:26Z<p>Erin: /* Development */</p>
<hr />
<div>{{Languages|Om 2008.8 Locations}}<br />
{{Om 2008.8}}<br />
== Introduction ==<br />
'''Locations''' (codenamed ''Splinter'') is a location sharing application based on GPS and SMS. It<br />
uses [http://www.openstreetmap.org OpenStreetMap] as its map source and allows users to manage and share saved locations.<br />
<br />
{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; width:100%;floating="center"; "<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " | <br />
[[Image:Main.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Edit1.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Om locations4.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:List.png|200px|center]]<br />
|}<br />
<br />
== Usage ==<br />
In addition to downloading map images from the OSM server, '''Locations''' also supports local maps, which can be downloaded through the [[Installer]]. You can also create your own maps if your city is not available. For more information, refer to the [[#Create Your Own Maps]] section below. <br />
<br />
=== Map === <br />
Use the '''MAP''' view to manage ''Tags'' with options to ''save'', ''edit'' or ''send''. '''MAP''' view also allows users to browse maps with zoom in and zoom out for accurate locating. If you get lost while browsing, simply tap the '''REFRESH''' button to return to your current position. It's that easy.<br />
<br />
=== List ===<br />
'''LIST''' view is a a centralized place to view all of your ''Tags''. The '''LIST''' view is a combination of your own saved ''Tags'' and ''Tags'' received by friends. <br />
Selecting a ''Tag'' takes you to the exact position of the Tag in the '''MAP''' view.<br />
<br />
=== Save & Send Tags ===<br />
Once you are connected to GPS, saving and sending tags to friends is fun and simple.<br />
<br />
* '''Save''' a Tag<br />
# Press the '''touch me''' bubble that hovers above your current position.<br />
# After the message box appears, tap directly into the text boxes under ''Edit Title'' and ''Edit Messages'' to add your ''Tag'' title or message.<br />
# After entering your title or message, press '''SAVE''', at which point your newly created ''Tag'' will appear in both '''MAP''' and '''LIST''' views.<br />
# In the '''MAP''' view, tapping on the text of your ''Tag'' provides further options to ''edit'' or ''send'' your your ''Tag'' to a friend.<br />
<br />
* '''Send''' a Tag<br />
# In the '''MAP''' view, tap on the text of your ''Tag'', launching the '''edit * send''' bubble.<br />
# Pressing on ''send'' will launch the ''Send a Tag'' message box<br />
# Tap directly within the text boxes to edit your ''Tag'' before sending, or press ''Send'' and your ''Tag'' will be on its way.<br />
<br />
== Maps ==<br />
<br />
=== Installation ===<br />
Maps can be installed from [http://wiki.openmoko.org/wiki/Om2008.8_Installer Installer].<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
[[Image:Install.png|200px|thumb|catogory]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:Install_maps2.png|200px|thumb|choose map]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:Install_maps3.png|200px|thumb|install map]]<br />
|}<br />
<br />
=== Create Your Own Maps ===<br />
<br />
{{Note | Map packing eats lots of memory and fails easily on NEO.}} <br />
<br />
'''Locations''' comes with a tool called '''om-locations-map-pack'''. It can be used to pack tile images downloaded from the OSM server into a map package:<br />
<br />
<pre><br />
om-locations-map-pack /tmp/diversity-maps my_map.eet<br />
</pre><br />
<br />
Place '''my_map.eet''' in either of the directories<br />
<br />
<pre><br />
/usr/share/om-locations/maps<br />
/media/card/om-maps<br />
</pre><br />
<br />
and '''Locations''' will find it automatically.<br />
<br />
=== Share Maps ===<br />
To share maps for other Neo users to install, see directions on how to * [[CommunityRepository#How_to_release_packages | Add a package to Openmoko Repository]]<br />
<br />
=== Use SD Card for Tile Storage (git only) ===<br />
By default, tiles downloaded from the OSM server are stored in '''/tmp/diversity-maps'''. They disappear after rebooting. This default path can be changed to, for example, use SD card by adding/editing one line<br />
<pre><br />
tile_path = /media/card<br />
</pre><br />
<br />
to '''~/.om-locations/config/om-locations.cfg'''.<br />
<br />
<pre><br />
config file may reside in ~/diversity-nav/config/diversity-nav.cfg<br />
</pre><br />
<br />
=== Download Tiles of a Region (git only) ===<br />
You can download tiles of a region by specifying '''-d''' option in '''om-locations-map-pack'''. The usage is<br />
<br />
<pre><br />
om-locations-map-pack -d version,source,min_level,max_level,lon,lat,width,height <tile-path><br />
</pre><br />
<br />
'''version''' can be any integer and '''source''' should be "osm". For example, to download tiles of Taipei and store them on the SD card, one can<br />
<br />
<pre><br />
om-locations-map-pack -d `date "+%Y%m%d"`,osm,5,16,121.5,25.0,0.1,0.1 /media/card<br />
</pre><br />
<br />
In this example, a region of longitude between '''121.5''' to '''121.6''' and of latitude bwtween '''25.0''' to '''25.1''' is specified. Tiles in this region and of levels from '''5''' to '''16''' are downloaded to '''/media/card'''. By instructing '''Locations''' to use '''/media/card''' as its tile path, one could pre-download tiles of any region and have '''Locations''' use them.<br />
<br />
== Turn on GPS Logging ==<br />
For now, nmea logging is off by default. To get nmea log for being used, we can send dbus message after om-locations launched as below:<br />
<pre><br />
dbus-send --session --dest=org.openmoko.Diversity --type=method_call --print-reply /org/openmoko/Diversity/objects/0/equipments/nmea org.openmoko.Diversity.Equipment.SetConfig string:log variant:string:/home/root/nmealog<br />
</pre><br />
Then the log will be saved to /home/root/nmealog in this example. <br />
<br />
After om-locations terminated, logging will stop.<br />
<br />
The size of log file will increase soon. For now be warned, if the dbus message was sent again, then the log will be overrridden. So backup or do some hacking first before doing that.<br />
<br />
== Development ==<br />
'''Locations''' is written in C and [http://enlightenment.org/p.php?p=about/efl EFL]. It talks to '''diversity-daemon''' through [http://www.freedesktop.org/wiki/Software/dbus D-Bus] to, for example, send tags and download tiles.<br />
<br />
To compile diversity-daemon,<br />
<br />
<pre><br />
$ svn checkout svn://svn.projects.openmoko.org/svnroot/diversity/trunk/diversity-daemon<br />
$ cd diversity-daemon<br />
$ ./configure --enable-session-bus<br />
$ make<br />
$ sudo make install<br />
</pre><br />
<br />
Please ensure that at least Control and OpenStreetMap backends are enabled. If not, check that you have libdbus-glib-1-dev and libcurl4-gnutls-dev (on debian) or similar packages installed.<br />
<br />
To compile Locations,<br />
<br />
<pre><br />
$ git clone git://git.openmoko.org/git/om-locations.git<br />
$ cd om-locations<br />
$ ./autogen.sh<br />
$ ./configure<br />
$ make<br />
$ sudo make install<br />
</pre><br />
<br />
Locations depends directly on recent versions of eet, evas, ecore, edje, and etk from EFL. Please consult its website for instructions to build them.<br />
<br />
== Feedbacks ==<br />
'''Locations''' uses [https://docs.openmoko.org/trac/ Trac] for bug tracking. When report bugs, please choose category Locations so that they go to the developers directly. There is no mailing list specific for '''Locations'''. Please use http://lists.openmoko.org/mailman/listinfo/ for discussion.<br />
<br />
== Translations ==<br />
'''Locations''' will be I18N-aware (support multi-languages) in the next release. To have your language(s) in the supported list, one can take this [http://people.openmoko.org/olv/tmp/om-locations_0.2.pot POT file] and upload your translation to [https://docs.openmoko.org/trac/ Trac] by creating a new ticket.<br />
<br />
== Reference ==<br />
[1] git repository of Locations - http://git.openmoko.org/?p=om-locations.git;a=summary<br />
<br />
[2] Diversity project - http://diversity.projects.openmoko.org/<br />
<br />
[3] Assassin project - http://code.google.com/p/om-assassin/<br />
<br />
[4] OpenStreetMap - http://www.openstreetmap.org/<br />
<br />
<br />
[[Category:Applications]]<br />
[[Category:Om 2008.8]]</div>Erinhttp://wiki.openmoko.org/wiki/Om_2008_LocationsOm 2008 Locations2008-08-11T09:46:02Z<p>Erin: /* Install Maps */</p>
<hr />
<div>{{Om 2008.8}}<br />
== Introduction ==<br />
'''Locations''' (codenamed ''Splinter'') is a UI application within the [http://diversity.projects.openmoko.org/ Diversity project]. <br />
'''Locations''' uses [http://www.openstreetmap.org OpenStreetMap] allowing users to browse maps and manage saved locations called ''Tags''.<br />
<br />
{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; width:100%;floating="center"; "<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " | <br />
[[Image:Main.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Edit1.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Om locations4.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:List.png|200px|center]]<br />
|}<br />
<br />
== Usage ==<br />
In addition to downloading map images from the OSM server, '''Locations''' also supports local maps, which can be downloaded through the [[Installer]]. You can also create your own maps if your city is not available. For more information, refer to the [http://wiki.openmoko.org/wiki/Om2008.8_Locations#Create_Offline_Maps Create Offline Maps] section below. <br />
<br />
=== Map === <br />
Use the '''MAP''' view to manage ''Tags'' with options to ''save'', ''edit'' or ''send''. '''MAP''' view also allows users to browse maps with zoom in and zoom out for accurate locating. If you get lost while browsing, simply tap the '''REFRESH''' button to return to your current position. It's that easy.<br />
<br />
=== List ===<br />
'''LIST''' view is a a centralized place to view all of your ''Tags''. The '''LIST''' view is a combination of your own saved ''Tags'' and ''Tags'' received by friends. <br />
Selecting a ''Tag'' takes you to the exact position of the Tag in the '''MAP''' view.<br />
<br />
=== Save & Send Tags ===<br />
Once you are connected to GPS, saving and sending tags to friends is fun and simple.<br />
<br />
* '''Save''' a Tag<br />
# Press the '''touch me''' bubble that hovers above your current position.<br />
# After the message box appears, tap directly into the text boxes under ''Edit Title'' and ''Edit Messages'' to add your ''Tag'' title or message.<br />
# After entering your title or message, press '''SAVE''', at which point your newly created ''Tag'' will appear in bot '''MAP''' and '''LIST''' views.<br />
# In the '''MAP''' view, tapping on the text of your ''Tag'' provides further options to ''edit'' or ''send'' your your ''Tag'' to a friend.<br />
<br />
* '''Send''' a Tag<br />
# In the '''MAP''' view, tap on the text of your ''Tag'', launching the '''edit * send''' bubble.<br />
# Pressing on ''send'' will launch the ''Send a Tag'' message box<br />
# Tap directly within the text boxes to edit your ''Tag'' before sending, or press ''Send'' and your ''Tag'' will be on its way.<br />
<br />
== Architecture ==<br />
'''Locations''' is a UI application, communicating with the diversity-daemon dbus interface to get all the data it needs.<br />
What '''Locations''' does and shows is based on and through diversity-daemon, like tag management, sharing, map downloading and GPS status.<br />
<br />
=== Design ===<br />
'''Locations''' uses the [http://enlightenment.org/p.php?p=about&l=en EFL library] to implement UI.<br />
Synced with diversity-daemon, '''Locations''' has objects, world and viewport concepts. There is a dbus wrapper layer for the diversity-daemon. <br />
In the UI, we have widgets like dialogs, menus, different objects like tags, map tilesets, etc.<br />
<br />
In control part, we have a nav object for controlling the navigation, showing the tileset.<br />
<br />
== Create Offline Maps ==<br />
'''Locations''' comes with a tool called '''om-locations-map-pack'''. It can be used to pack tile images downloaded from OSM server into a map package:<br />
<br />
<pre><br />
om-locations-map-pack /tmp/diversity-maps my_map.eet<br />
</pre><br />
<br />
Place '''my_map.eet''' in either of the directories<br />
<br />
<pre><br />
/usr/share/om-locations/maps<br />
/media/card/om-maps<br />
</pre><br />
<br />
and '''Locations''' will find it automatically.<br />
<br />
=== Share Maps ===<br />
To share maps for other Neo users to install, see directions on how to * [[CommunityRepository#How_to_release_packages | Add a package to Openmoko Repository]]<br />
<br />
== Install Maps ==<br />
To install maps from [http://wiki.openmoko.org/wiki/Om2008.8_Installer Installer].<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
[[Image:Install.png|200px|thumb|catogory]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:Install_maps2.png|200px|thumb|choose map]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:Install_maps3.png|200px|thumb|install map]]<br />
|}<br />
<br />
== Reference ==<br />
[1] Diversity project - http://diversity.projects.openmoko.org/<br />
<br />
[2] Assassin project - http://code.google.com/p/om-assassin/<br />
<br />
[3] OpenStreetMap - http://www.openstreetmap.org/<br />
<br />
<br />
[[Category:Applications]]<br />
[[Category:Openmoko2008.8]]</div>Erinhttp://wiki.openmoko.org/wiki/Om_2008_LocationsOm 2008 Locations2008-08-11T09:44:00Z<p>Erin: /* install maps */</p>
<hr />
<div>{{Om 2008.8}}<br />
== Introduction ==<br />
'''Locations''' (codenamed ''Splinter'') is a UI application within the [http://diversity.projects.openmoko.org/ Diversity project]. <br />
'''Locations''' uses [http://www.openstreetmap.org OpenStreetMap] allowing users to browse maps and manage saved locations called ''Tags''.<br />
<br />
{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; width:100%;floating="center"; "<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " | <br />
[[Image:Main.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Edit1.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Om locations4.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:List.png|200px|center]]<br />
|}<br />
<br />
== Usage ==<br />
In addition to downloading map images from the OSM server, '''Locations''' also supports local maps, which can be downloaded through the [[Installer]]. You can also create your own maps if your city is not available. For more information, refer to the [http://wiki.openmoko.org/wiki/Om2008.8_Locations#Create_Offline_Maps Create Offline Maps] section below. <br />
<br />
=== Map === <br />
Use the '''MAP''' view to manage ''Tags'' with options to ''save'', ''edit'' or ''send''. '''MAP''' view also allows users to browse maps with zoom in and zoom out for accurate locating. If you get lost while browsing, simply tap the '''REFRESH''' button to return to your current position. It's that easy.<br />
<br />
=== List ===<br />
'''LIST''' view is a a centralized place to view all of your ''Tags''. The '''LIST''' view is a combination of your own saved ''Tags'' and ''Tags'' received by friends. <br />
Selecting a ''Tag'' takes you to the exact position of the Tag in the '''MAP''' view.<br />
<br />
=== Save & Send Tags ===<br />
Once you are connected to GPS, saving and sending tags to friends is fun and simple.<br />
<br />
* '''Save''' a Tag<br />
# Press the '''touch me''' bubble that hovers above your current position.<br />
# After the message box appears, tap directly into the text boxes under ''Edit Title'' and ''Edit Messages'' to add your ''Tag'' title or message.<br />
# After entering your title or message, press '''SAVE''', at which point your newly created ''Tag'' will appear in bot '''MAP''' and '''LIST''' views.<br />
# In the '''MAP''' view, tapping on the text of your ''Tag'' provides further options to ''edit'' or ''send'' your your ''Tag'' to a friend.<br />
<br />
* '''Send''' a Tag<br />
# In the '''MAP''' view, tap on the text of your ''Tag'', launching the '''edit * send''' bubble.<br />
# Pressing on ''send'' will launch the ''Send a Tag'' message box<br />
# Tap directly within the text boxes to edit your ''Tag'' before sending, or press ''Send'' and your ''Tag'' will be on its way.<br />
<br />
== Architecture ==<br />
'''Locations''' is a UI application, communicating with the diversity-daemon dbus interface to get all the data it needs.<br />
What '''Locations''' does and shows is based on and through diversity-daemon, like tag management, sharing, map downloading and GPS status.<br />
<br />
=== Design ===<br />
'''Locations''' uses the [http://enlightenment.org/p.php?p=about&l=en EFL library] to implement UI.<br />
Synced with diversity-daemon, '''Locations''' has objects, world and viewport concepts. There is a dbus wrapper layer for the diversity-daemon. <br />
In the UI, we have widgets like dialogs, menus, different objects like tags, map tilesets, etc.<br />
<br />
In control part, we have a nav object for controlling the navigation, showing the tileset.<br />
<br />
== Create Offline Maps ==<br />
'''Locations''' comes with a tool called '''om-locations-map-pack'''. It can be used to pack tile images downloaded from OSM server into a map package:<br />
<br />
<pre><br />
om-locations-map-pack /tmp/diversity-maps my_map.eet<br />
</pre><br />
<br />
Place '''my_map.eet''' in either of the directories<br />
<br />
<pre><br />
/usr/share/om-locations/maps<br />
/media/card/om-maps<br />
</pre><br />
<br />
and '''Locations''' will find it automatically.<br />
<br />
=== Share Maps ===<br />
To share maps for other Neo users to install, see directions on how to * [[CommunityRepository#How_to_release_packages | Add a package to Openmoko Repository]]<br />
<br />
== Install Maps ==<br />
To install maps from [http://wiki.openmoko.org/wiki/Om2008.8_Installer Installer].<br />
<br />
<br />
== Reference ==<br />
[1] Diversity project - http://diversity.projects.openmoko.org/<br />
<br />
[2] Assassin project - http://code.google.com/p/om-assassin/<br />
<br />
[3] OpenStreetMap - http://www.openstreetmap.org/<br />
<br />
<br />
[[Category:Applications]]<br />
[[Category:Openmoko2008.8]]</div>Erinhttp://wiki.openmoko.org/wiki/File:Install_maps3.pngFile:Install maps3.png2008-08-11T09:43:35Z<p>Erin: </p>
<hr />
<div></div>Erinhttp://wiki.openmoko.org/wiki/File:Install_maps2.pngFile:Install maps2.png2008-08-11T09:43:01Z<p>Erin: </p>
<hr />
<div></div>Erinhttp://wiki.openmoko.org/wiki/Om_2008_SudokuOm 2008 Sudoku2008-08-07T06:57:54Z<p>Erin: /* notes */</p>
<hr />
<div>{{Om 2008.8}}<br />
== Introduction ==<br />
'''Sudoku''' is a UI application and it plays like normal sudoku puzzle games. It is a logic-based number-placement puzzle. The objective is to fill a 9×9 grid so that each column, each row, and each of the nine 3×3 boxes (also called blocks or regions) contains the digits from 1 to 9 only one time each. The puzzle setter provides a partially completed grid. For more information, refer to the [http://en.wikipedia.org/wiki/Sudoku Sudoku rules].<br />
<br />
{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; width:100%;floating="center"; "<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " | <br />
[[Image:Sudoku-1.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Sudoku-2.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Sudoku-3.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Sudoku-4.png|200px|center]]<br />
|}<br />
<br />
== Usage ==<br />
There are 5 icons and a number keyboard at the bottom. Choose one empty grid and pick up one suitable number to fill in! If the number is wrong/illegal, then number color becomes red. <br />
<br />
* icons (from left to right)<br />
# Create New puzzle<br />
# Undo a step <br />
# Redo a step<br />
# Clear all filled-in numbers<br />
# Check solved or not solved<br />
<br />
* 1-9 number keyboard <br />
<br />
== Source code ==<br />
This UI application is written by python. Download the source code, it comes with a generator and solver. You can generate different level of puzzles. Code is from [https://svn.projects.openmoko.org/svnroot/pyefl-sudoku here]. Check the [http://projects.openmoko.org/plugins/scmsvn/viewcvs.php/README?rev=16&root=pyefl-sudoku&view=markup README] document!<br />
<br />
<br />
== Reference ==<br />
[1] Sudoku project - http://projects.openmoko.org/projects/pyefl-sudoku/<br />
<br />
<br />
[[Category:Applications]]<br />
[[Category:Openmoko2008.8]]</div>Erinhttp://wiki.openmoko.org/wiki/File:Sudoku-4.pngFile:Sudoku-4.png2008-08-07T06:32:20Z<p>Erin: om-soduok 004 screenshot</p>
<hr />
<div>om-soduok 004 screenshot</div>Erinhttp://wiki.openmoko.org/wiki/File:Sudoku-3.pngFile:Sudoku-3.png2008-08-07T06:32:01Z<p>Erin: om-soduok 003 screenshot</p>
<hr />
<div>om-soduok 003 screenshot</div>Erinhttp://wiki.openmoko.org/wiki/File:Sudoku-2.pngFile:Sudoku-2.png2008-08-07T06:31:35Z<p>Erin: om-soduok 002 screenshot</p>
<hr />
<div>om-soduok 002 screenshot</div>Erinhttp://wiki.openmoko.org/wiki/File:Sudoku-1.pngFile:Sudoku-1.png2008-08-07T06:31:09Z<p>Erin: om-soduok 001 screenshot</p>
<hr />
<div>om-soduok 001 screenshot</div>Erinhttp://wiki.openmoko.org/wiki/Om_2008_InstallerOm 2008 Installer2008-08-07T03:22:33Z<p>Erin: /* Reference */</p>
<hr />
<div>{{Om 2008.8}}<br />
<br />
==Introduction==<br />
'''Installer''' is a tool for ''installing'', ''updating'' and ''uninstalling'' programs on your Neo. <br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
[[Image:Install.png|200px|thumb|catogory]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:Install1.png|200px|thumb|choose program]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:Installer4.png|200px|thumb|install application]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:Om2008 installer2.png|200px|thumb|install application]]<br />
|}<br />
==Install an Application ==<br />
'''Installer''' uses a WiFi or [http://svn.openmoko.org/developers/tick/Test_env_script_GTA02A5/setneo USB] network connection to connect to repositories.<br />
<br />
===Instructions===<br />
<br />
'''[1]''' Connect to a WiFi network in the '''Settings''' application, or manually connect to a [http://svn.openmoko.org/developers/tick/Test_env_script_GTA02A5/setneo USB] network connection before proceeding to '''Installer'''.<br />
<br />
'''[2]''' In '''Installer''', press the '''INSTALL''' button from the bottom bar to view a list of Categories. This is also the default page of the Installer application.<br />
<br />
'''[3]''' Select a Category from the category list, then select a package to install.<br />
<br />
'''[4]''' In the package information page, press the image box and confirm to begin.<br />
<br />
'''[5]''' Once the progress bar shows '''Done''', you will return to the Installer default page. Installation is then complete.<br />
<br />
* To ''update'' or ''uninstall'' packages, simply replace step '''[2]''' with the desired function '''UPDATE''' or '''UNINSTALL''' and repeat steps '''[3]''' through '''[5]'''.<br />
<br />
==Sharing Applications==<br />
Sharing applications amongst users and developers is easy using the [[CommunityRepository | Multiverse]]. Anyone can upload applications or even their own repository to share with fellow Neo owners.<br />
<br />
===How to add a package to Openmoko Repository===<br />
<br />
You can release your package with ipk file. <br />
<br />
* [[Create package on projects.openmoko.org and upload]]<br />
* '''Create ipk files'''<br />
** Using OE<br />
** [[Toolchain|Meta-toolchain]]<br />
<br />
==== Package Tags ====<br />
Packages in '''Installer''' are displayed according to '''Package Tags'''.<br />
To display a package through [[Om2008.8_Installer |Installer]], add the appropriate tag message. <br />
{|<br />
! Category !! Tag <br />
|- <br />
| Communication || group::communication <br />
|-<br />
| Development || group::programming<br />
|-<br />
| Games || group::games<br />
|-<br />
| Maps || group::maps<br />
|-<br />
| Miscellaneous || group::unknown<br />
|-<br />
| Network || group::network<br />
|-<br />
|Repos || group::repos<br />
|}<br />
<br />
* For OpenEmbedded users, add a Tag by adding one line in your bb file<br />
:For [http://code.google.com/p/comic-reader/source/browse/trunk/data/comic-reader_svn.bb example]:<br />
PKG_TAGS_${PN} = "group::games"<br />
<br />
==== Add a Repository ==== <br />
===== Add repositories by installing repository packages =====<br />
* The community-repository is installed by default in [[Om2008.8 | Om 2008.8]].<br />
<br />
===== Add repository manually =====<br />
* Create a file, here we call it community-repos.conf<br />
> echo "arch community-repos 50" > community-repos.conf<br />
> echo "src community-repos http://downloads.openmoko.org/repository/Multiverse/" >> community-repos.conf<br />
* Connect to your Neo with USB<br />
> sudo ifconfig usb0 192.168.0.200<br />
> scp community-repos.conf root@192.168.0.202:/etc/opkg/<br />
* Let your Neo connect to the Internet<br />
** For USB users:<br />
> echo 1 | sudo tee /proc/sys/net/ipv4/ip_forward<br />
> sudo iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE<br />
> scp /etc/resolv.conf root@192.168.0.202:/etc/<br />
** For geek users:<br />
> ssh root@192.168.0.202<br />
> iwlist eth0 scan<br />
Find a usable AP lets say OpenMind (Support it's an open AP)<br />
> iwconfig eth0 essid OpenMind<br />
> udhcpc eth0<br />
Then pray, if successfull, remove default gw *twice*.<br />
> route -n # to see your gateway of eth0 say 192.168.1.1<br />
> route del default<br />
> route del default<br />
> route add default gw 192.168.1.1 eth0<br />
Then you can ping wiki.openmoko.org for testing :)<br />
** For GUI WiFi user:<br />
Click Settings<br />
Click WiFi<br />
Select an AP<br />
Input password if needed<br />
<br />
* Refresh the opkg metadata database<br />
after connecting to Neo<br />
> opkg update<br />
<br />
== Technical Features ==<br />
* '''Installer''' is a specialized GUI front-end of [http://packagekit.org/ Packagekit] over DBus interface.<br />
<br />
* Please run '''Installer''' under stable network conditions and enough power supply. Once '''Installer''' is launched, it will actually try to detect repositories you installed. This will take some time if your network condition is not stable.<br />
** If you do not have access to WiFi, a [http://svn.openmoko.org/developers/tick/Test_env_script_GTA02A5/setneo USB] connection is recommended.<br />
* The default Packagekit backend on Neo is [[opkg]], but is not restricted to opkg. <br />
<br />
* '''Installer''' refreshes the package meta-data every 2 days.<br />
<br />
* While running '''Installer''', it will also launch packagekitd automatically, in which it will lock the libopkg for synchronization issues. If you want to use opkg, you may terminate '''Installer''' and killall packagekitd.<br />
<br />
* You can also talk with Packagekit through DBus.<br />
<br />
For more information, refer to the reference section below.<br />
<br />
== Reference ==<br />
[1] Installer project - http://code.google.com/p/om-assassin/<br />
<br />
[2] Packagekit project - http://packagekit.org/<br />
<br />
[3] Opkg package management - http://wiki.openmoko.org/wiki/Opkg<br />
<br />
[[Category:Applications]]<br />
[[Category:Openmoko2008.8]]</div>Erinhttp://wiki.openmoko.org/wiki/Om2008.8Om2008.82008-08-07T03:18:34Z<p>Erin: /* Share */</p>
<hr />
<div>{{Languages|Openmoko2008.8}}<br />
{{Om 2008.8}}<br />
<br />
{{Distributions|Openmoko2008.8}}<br />
<br />
=Introduction=<br />
'''Om 2008.8''' is the successor to [[OM2007.2|Om 2007.2]] and had '''ASU''' as a codename. It will be launched on August 08, 2008. Om2008.8 uses EFL for the launcher, custom UI applications and [[QtopiaOnX11|Qtopia on X11]] for telephony.<br />
It is the first step from [[GTK+]] on x11 to using multiple toolkits in combination. Om2008.8 now supports [http://www.enlightenment.org/ EFL], [http://trolltech.com/products/qtopia Qtopia] and [[GTK+]] applications.<br />
<br />
{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; width:100%;floating="center"; "<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " | <br />
[[Image:Om2008 uboot.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Om2008 home.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Installer4.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Om2008 installer1.png|200px|center]]<br />
|-<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " | <br />
[[Image:Main.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Edit1.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Om locations4.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:List.png|200px|center]]<br />
|}<br />
<br />
== What's New ==<br />
'''Om 2008.8''' was designed to be as empty as possible, for the very purpose of showcasing your ideas.<br />
<br />
Think of our products as museums. We're building the environment. Each one different from the next. You'll get all the free art supplies you could imagine because we want you to add your own meaning. You choose: consume, create, or both.<br />
<br />
Either way you create your own meaning. It's about you. <br />
<br />
=== Customize ===<br />
'''Om 2008.8''' allows you to customize your Neo in many aspects.<br />
<br />
* '''Use the Installer''' to find apps and modifications for your Neo.<br />
* '''Re-design themes''' by customizing your own [[Edje]] files.<br />
* '''Source Codes''' are publicly available, allowing for customization all the way down to low level sytems.<br />
<br />
=== Share ===<br />
* share your locations ([[Om2008.8_Locations|Locations]])<br />
:you can use splinter to save your location and even send it to friends via sms. How cool is that?!<br />
* share your applications ([[Om2008.8_Installer|Installer]])<br />
:share your ideas with the world by adding packages to the [http://wiki.openmoko.org/wiki/CommunityRepository Community Repository]. It is a great database for all things openmoko and can easily be accessed by any user through the [[Om2008.8 Installer|Installer]].<br />
<br />
== Feature Plan ==<br />
<br />
You can see a list of available and planned features at [[Om2008.8 Feature Plan|Om 2008.8 Feature Plan]].<br />
<br />
== Download ==<br />
<br />
[http://buildhost.openmoko.org/daily/freerunner/200808/ Download images]<br />
<br />
== Installing ==<br />
For instructions on how to flash your device, please refer to [[Flashing the Neo FreeRunner]].<br />
<br />
[[Category:Distributions]]<br />
[[Category:Openmoko2008.8]]<br />
<br />
== Known Issues ==<br />
''Last updated on'' '''August 7th, 2008'''</div>Erinhttp://wiki.openmoko.org/wiki/Om2008.8Om2008.82008-08-07T03:16:14Z<p>Erin: /* Share */</p>
<hr />
<div>{{Languages|Openmoko2008.8}}<br />
{{Om 2008.8}}<br />
<br />
{{Distributions|Openmoko2008.8}}<br />
<br />
=Introduction=<br />
'''Om 2008.8''' is the successor to [[OM2007.2|Om 2007.2]] and had '''ASU''' as a codename. It will be launched on August 08, 2008. Om2008.8 uses EFL for the launcher, custom UI applications and [[QtopiaOnX11|Qtopia on X11]] for telephony.<br />
It is the first step from [[GTK+]] on x11 to using multiple toolkits in combination. Om2008.8 now supports [http://www.enlightenment.org/ EFL], [http://trolltech.com/products/qtopia Qtopia] and [[GTK+]] applications.<br />
<br />
{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; width:100%;floating="center"; "<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " | <br />
[[Image:Om2008 uboot.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Om2008 home.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Installer4.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Om2008 installer1.png|200px|center]]<br />
|-<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " | <br />
[[Image:Main.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Edit1.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:Om locations4.png|200px|center]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |<br />
[[Image:List.png|200px|center]]<br />
|}<br />
<br />
== What's New ==<br />
'''Om 2008.8''' was designed to be as empty as possible, for the very purpose of showcasing your ideas.<br />
<br />
Think of our products as museums. We're building the environment. Each one different from the next. You'll get all the free art supplies you could imagine because we want you to add your own meaning. You choose: consume, create, or both.<br />
<br />
Either way you create your own meaning. It's about you. <br />
<br />
=== Customize ===<br />
'''Om 2008.8''' allows you to customize your Neo in many aspects.<br />
<br />
* '''Use the Installer''' to find apps and modifications for your Neo.<br />
* '''Re-design themes''' by customizing your own [[Edje]] files.<br />
* '''Source Codes''' are publicly available, allowing for customization all the way down to low level sytems.<br />
<br />
=== Share ===<br />
* share your locations ([[Om2008.8_Locations|Locations]])<br />
:you can use splinter to save your location and even send it to friends via sms. How cool is that?!<br />
* share your applications ([[Om2008.8_Installer|Installer]])<br />
:share your ideas with the world by adding packages to the [http://downloads.openmoko.org/communityrepository/ Openmoko Repository]. It is a great database for all things openmoko and can easily be accessed by any user through the [[Om2008.8 Installer|Installer]].<br />
<br />
== Feature Plan ==<br />
<br />
You can see a list of available and planned features at [[Om2008.8 Feature Plan|Om 2008.8 Feature Plan]].<br />
<br />
== Download ==<br />
<br />
[http://buildhost.openmoko.org/daily/freerunner/200808/ Download images]<br />
<br />
== Installing ==<br />
For instructions on how to flash your device, please refer to [[Flashing the Neo FreeRunner]].<br />
<br />
[[Category:Distributions]]<br />
[[Category:Openmoko2008.8]]<br />
<br />
== Known Issues ==<br />
''Last updated on'' '''August 7th, 2008'''</div>Erinhttp://wiki.openmoko.org/wiki/Main_PageMain Page2008-08-04T07:17:27Z<p>Erin: </p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
<br />
[[Image:Freerunner02.gif|thumb|200px|right|Neo Freerunners]]<br />
<br />
<div style="padding: 2ex; text-align: center; font: bold x-large sans">[[Openmoko]]™ - Open. Mobile. Free.</div><br />
<br />
Openmoko™ born as an Open Source project under GPL and LGPL license and dedicated to delivering an open software stack on mobile platforms, shipped its first product, the Neo 1973, on July 9 2007; and then, turned the project into a start-up company with one aim: create great mobile products using the Openmoko stack: Open. Mobile. Free. <br />
<br />
<br />
<div style="clear:both">&nbsp;</div><br />
<br />
<table class="wikitable" cellspacing="4" cellpadding="6" width="100%" style="color:white"><br />
<tr style="background:#ff6600; text-align:center; font-weight:bold"><br />
<td width="50%">News and events</td><br />
<td width="50%">New to Openmoko?</td><br />
</tr><br />
<tr valign="top" style="background:#333333"><br />
<td><br />
* 4-5/8: Openmoko is at Linuxworld, San Francisco<br />
* 30/7: The FSO distribution releases [http://downloads.openmoko.org/framework/milestone2/ milestone 2] <br />
* 25/7: Community helps, [[GPS Problems]] fixed<br />
* 20/7: [http://wiki.openmoko.org/wiki/Debian Debian] added to the Distributions page<br />
* 27/6: GTA 02 shipping in the [http://lists.openmoko.org/pipermail/community/2008-June/019943.html material world]<br />
</td><br />
<td><br />
===<font color=white>About Openmoko</font>===<br />
* [[Introduction]]<br />
* [[Neo FreeRunner|Neo FreeRunner phone]]<br />
* [[Supported Hardware]]<br />
* [[FAQ]]<br />
<br />
===<font color=white>Getting Openmoko</font>===<br />
* [[Getting Openmoko]]<br />
* [http://www.openmoko.com Openmoko Inc.]<br />
<br />
</td><br />
</tr><br />
<tr style="background:#ff6600; text-align:center; font-weight:bold"><br />
<td width="50%">for Users</td><br />
<td width="50%">for Developers</td><br />
</tr><br />
<tr valign="top" style="background:#333333"><br />
<td><br />
===<font color=white>Getting started</font>===<br />
* [[Getting Started with your Neo FreeRunner | Neo FreeRunner getting started guide]]<br />
* [[Getting Started FAQ]]<br />
<br />
===<font color=white>Software</font>===<br />
* [[Distributions|Openmoko software distributions]]<br />
* [[OpenmokoFramework|FSO distribution]]<br />
* [[Openmoko2007.2|2007.2 distribution]]<br />
* [[ASU|ASU distribution]]<br />
* [[Qtopia_on_FreeRunner|Qtopia Distribution]]<br />
<br />
===<font color=white>Openmoko community</font>===<br />
* [[Discussion_Forums| Discussion Forums]]<br />
* [[CommunityRepository|Community repository]]<br />
* [[Development resources | Development resources]]<br />
</td><br />
<td><br />
===<font color=white>Applications development</font>===<br />
* [[Toolchain|The toolchain]]<br />
<!-- * <font color=white>VMware</font> --><br />
* [[Python|Introduction to Python]]<br />
* [http://projects.openmoko.org/ Projects hosted in our GForge]<br />
<br />
===<font color=white>Integration and distributions</font>===<br />
* [[OpenEmbedded|The OpenEmbedded distribution building framework]]<br />
* [[MokoMakefile|Building Openmoko using the MokoMakefile ]]<br />
* [[Opkg|Opkg the package manager]]<br />
<br />
===<font color=white>Emulation</font>===<br />
* [[Openmoko under QEMU]] <br />
</td><br />
</tr><br />
</table><br />
<br />
<div style="padding: 2ex; margin-top: 1ex; text-align: center; font: bold x-large sans">What do we mean by Open. Mobile. Free. ?</div><br />
<br />
The Openmoko stack, which includes a full X server, allows users and developers to transform mobile hardware platforms into a unique products. Our licence gives developers and users freedom from the "iron to the eyeballs," freedom to cosmetically customize their device or radically remix it; change the wallpaper or rebuild the entire house! It grants them the freedom, for example, to transform a phone into a medical device or point of sale device or the freedom to simply install their own favorite software. Beyond freeing the software on our devices we have also released our CAD files under Creative Commons. By freeing the software under GPL, we enable the community of FOSS developers to "make it new." By freeing the CAD files we give industrial designers and engineers this same opportunity. And at Linux world 2008, we will announce the release of the Schematics for our products. <br />
<br />
<br />
{{Languages|Main Page}}<br />
<br />
[[Category:Information| ]]</div>Erinhttp://wiki.openmoko.org/wiki/File:Diversity-radar_intro.pdfFile:Diversity-radar intro.pdf2008-06-09T03:46:06Z<p>Erin: diversity radar introduction slide for regular training</p>
<hr />
<div>diversity radar introduction slide for regular training</div>Erinhttp://wiki.openmoko.org/wiki/Regular_Training_ProgramsRegular Training Programs2008-06-09T03:45:07Z<p>Erin: /* Programs */</p>
<hr />
<div>== Introduction ==<br />
To practice and improve the skills for team work, every software engineer at openmoko Taipei office would attend weekly training / experience sharing events. and be one of the speakers of the regular events by turns.<br />
<br />
== Orientations ==<br />
The orientations and topics are dedicated to the purpose as following:<br />
# [[OpenMoko_FOSS_Tools_Introduction]]<br />
# Manufacturing process and Factory testing procedure<br />
# Case study for OpenMoko software architecture and designs<br />
# Phone functionality and inter-connectivity<br />
# Recent development progress of [[OpenLab]]<br />
<br />
== Programs ==<br />
Rough schedule for each of the events/programs done and planned by openmoko software team as following:<br />
<br />
{|<br />
! Topic !! Speaker !! Date !! Summary / Notes !! Slides / Reference Materials<br />
|- style="background-color:#eeeedd;"<br />
! colspan="5"|Regular Training Program<br />
|-<br />
|Introduction to Autotools || [[User:jserv|Jim Huang]] || Jul 8, 2007 || Brief introduction to GNU Autotools (automake, autoconf, and libtool), which are useful for cross development and diverse environments. || [[Media:moko-autotools.pdf|moko-autotools.pdf]]<br />
|-<br />
|Text Layout in GTK+ World || olv || Jul 20, 2007 || An introduction to pango and text layout. || [[Media:Text_layout_in_gtk.pdf|Text_layout_in_gtk.pdf]]<br />
|-<br />
|Introduction to GSM Multiplexer || Sweden Hsu ||Jul 27, 2007 || Overview to GSM Multiplexer (GSM 07.10) and analyze current implementation of OpenMoko and Linux kernel support.<br />
|-<br />
|OpenMoko GSM/GPRS Overview || [[User:Jserv|Jim Huang]] || Aug 3, 2007 || Overview to OpenMoko gsmd/libgsmd/gsmmux for GSM/GPRS functions in the aspect of system-level architecture and designs. || [[Media:openmokogsm.pdf|openmokogsm.pdf]]<br />
|-<br />
|Factory and Production Test|| Nod Huang || Aug 24, 2007 || Experience for GTA01 production in Suzhou. The presentation will cover testing procedure, related software, and possible issues. Also, he will share his thoughts about GTA01/HXD8/GTA02 production considerations. ||[[Media:Dash_Production_Flow.pdf|Dash_Production_Flow.pdf]]<br />
|-<br />
|3G Feature Phone Case Study || Erin Yuen || Sep 7, 2007 || Take BenQ 3G Feature Phone design and production as case study. || <br />
|-<br />
|Three levels of Fun in Graphics || olv || Sep 14, 2007 || There are three things to do in designing a GUI toolkit: graphics, human interaction, and widgets... || [[Media:graphics_fun.pdf|graphics_fun.pdf]]<br />
|-<br />
|Automatic Approaches for Building, Deployment, and Testing || [[User:John|John Lee]] || Sep 21, 2007 || A brief introduction to the current automatic build/deploy/test method. || [[Media:auto.pdf|auto.pdf]]<br />
|-<br />
|Case Study: Linux-based Skype/GSM dual-mode phone || IFan "Tick" Chen || Sep 28, 2007 || Share the experience of Linux-based Skype/GSM dual-mode phone project inside Compal Communications Inc. as case study. || [[Media:Dual.pdf|dual.pdf]]<br />
|-<br />
|Graphics and stuff (TBD) || Raster || Nov 02, 2007 || Will talk about Graphics and stuff || TBA<br />
|-<br />
|EFL introduction || Jeremy Chang || Nov 16, 2007 || Enlightenment Foundation Libraries overview . || [[Media:EFL_intro.pdf|EFL introduction]] <br />
|-<br />
|Introduction to Boot and Application Launching Time Optimizations for Linux-based products || [[User:Jserv|Jim Huang]] || Nov 23, 2007 || How fast do we need in product expectations? Analyzing boot time and application launching. Optimizations to boot time. Tweaking in user-space. || <br />
|-<br />
|Introduction of the PBE|| [[User:Nod|Nod Huang]] || Nov 30, 2007 || 1. PBE file system 2. how to create a new package in PBE 3. PBE file system 4. how to create a new package in PBE || [[Media:PBE.pdf|PBE.pdf]] <br />
|-<br />
|Power consumption in kernel|| [[User:Willie|Willie Chen]] || Dec 7, 2007 || 1. How to reduce power consumption 2. Utilities 3. GTA01/GTA02 issues || [[Media:power.pdf|Power]]<br />
|-<br />
|ARM Exception System Introduction (HXD8 example)|| [[User:Alec|Alec Tsai]] || Jan 11, 2008 || 1. Exceptions 2. System Memory Map || [[Media:Exception.pdf|Exception]]<br />
|-<br />
| Object files Introduction|| [[User:tick | Tick]] || Feb, 22 2008 || A brief introductions to a.out and ELF || [[Media:elf.pdf| ELF]]<br />
|- <br />
| Kboot || [[User:werner| Werner]] || Feb, 29 2009 || An introduction and discussion about Kboot ||<br />
|- <br />
| Small introduction to Qtopia || [[User: zecke | Zecke]] || Mar, 07 2008 || A small introduction to Qtopia || [[Media: qtopia.pdf | Qtopia]]<br />
|-<br />
| Some daemons in OM-2007.2|| [[User:olv | olv]] || Mar, 14 2008 || A brief introduction to daemons running behind OM-2007.2 || [[Media:om-daemons.pdf| om-daemons.pdf]]<br />
|-<br />
| Introduce to Audio || [[User:graeme | Graeme]] || Mar, 21 2008 || An introduction to the Audio system || [[Media: audio_presentation.pdf | Audio]]<br />
|-<br />
| Assassin || [[User:tick| Tick]] || April, 11, 2008 || An Introduction of Assassin || [[Media:assassin.pdf | Assassin]]<br />
|-<br />
| Xglamo Graphics || [[User:olv| olv]] || May, 16, 2008 || Introduction to X and Xglamo graphics and accelerations || [[Media:xglamo-graphics.pdf | xglamo-graphics.pdf]]<br />
|-<br />
| Diversity-radar || [[User:Erin| Erin]] || June, 6, 2008 || Introduction of Diversity-radar|| [[Media:diversity-radar_intro.pdf | diversity-radar_intro.pdf]]<br />
|<br />
<br />
<br />
[[Category:Training| ]]</div>Erinhttp://wiki.openmoko.org/wiki/Regular_Training_ProgramsRegular Training Programs2008-04-07T15:43:40Z<p>Erin: /* Programs */</p>
<hr />
<div>== Introduction ==<br />
To practice and improve the skills for team work, every software engineer at openmoko Taipei office would attend weekly training / experience sharing events. and be one of the speakers of the regular events by turns.<br />
<br />
== Orientations ==<br />
The orientations and topics are dedicated to the purpose as following:<br />
# [[OpenMoko_FOSS_Tools_Introduction]]<br />
# Manufacturing process and Factory testing procedure<br />
# Case study for OpenMoko software architecture and designs<br />
# Phone functionality and inter-connectivity<br />
# Recent development progress of [[OpenLab]]<br />
<br />
== Programs ==<br />
Rough schedule for each of the events/programs done and planned by openmoko software team as following:<br />
<br />
{|<br />
! Topic !! Speaker !! Date !! Summary / Notes !! Slides / Reference Materials<br />
|- style="background-color:#eeeedd;"<br />
! colspan="5"|Regular Training Program<br />
|-<br />
|Introduction to Autotools || [[User:jserv|Jim Huang]] || Jul 8, 2007 || Brief introduction to GNU Autotools (automake, autoconf, and libtool), which are useful for cross development and diverse environments. || [[Media:moko-autotools.pdf|moko-autotools.pdf]]<br />
|-<br />
|Text Layout in GTK+ World || olv || Jul 20, 2007 || An introduction to pango and text layout. || [[Media:Text_layout_in_gtk.pdf|Text_layout_in_gtk.pdf]]<br />
|-<br />
|Introduction to GSM Multiplexer || Sweden Hsu ||Jul 27, 2007 || Overview to GSM Multiplexer (GSM 07.10) and analyze current implementation of OpenMoko and Linux kernel support.<br />
|-<br />
|OpenMoko GSM/GPRS Overview || [[User:Jserv|Jim Huang]] || Aug 3, 2007 || Overview to OpenMoko gsmd/libgsmd/gsmmux for GSM/GPRS functions in the aspect of system-level architecture and designs. || [[Media:openmokogsm.pdf|openmokogsm.pdf]]<br />
|-<br />
|Factory and Production Test|| Nod Huang || Aug 24, 2007 || Experience for GTA01 production in Suzhou. The presentation will cover testing procedure, related software, and possible issues. Also, he will share his thoughts about GTA01/HXD8/GTA02 production considerations. ||[[Media:Dash_Production_Flow.pdf|Dash_Production_Flow.pdf]]<br />
|-<br />
|3G Feature Phone Case Study || Erin Yuen || Sep 7, 2007 || Take BenQ 3G Feature Phone design and production as case study. || <br />
|-<br />
|Three levels of Fun in Graphics || olv || Sep 14, 2007 || There are three things to do in designing a GUI toolkit: graphics, human interaction, and widgets... || [[Media:graphics_fun.pdf|graphics_fun.pdf]]<br />
|-<br />
|Automatic Approaches for Building, Deployment, and Testing || [[User:John|John Lee]] || Sep 21, 2007 || A brief introduction to the current automatic build/deploy/test method. || [[Media:auto.pdf|auto.pdf]]<br />
|-<br />
|Case Study: Linux-based Skype/GSM dual-mode phone || IFan "Tick" Chen || Sep 28, 2007 || Share the experience of Linux-based Skype/GSM dual-mode phone project inside Compal Communications Inc. as case study. || [[Media:Dual.pdf|dual.pdf]]<br />
|-<br />
|Graphics and stuff (TBD) || Raster || Nov 02, 2007 || Will talk about Graphics and stuff || TBA<br />
|-<br />
|EFL introduction || Jeremy Chang || Nov 16, 2007 || Enlightenment Foundation Libraries overview . || [[Media:EFL_intro.pdf|EFL introduction]] <br />
|-<br />
|Introduction to Boot and Application Launching Time Optimizations for Linux-based products || [[User:Jserv|Jim Huang]] || Nov 23, 2007 || How fast do we need in product expectations? Analyzing boot time and application launching. Optimizations to boot time. Tweaking in user-space. || <br />
|-<br />
|Introduction of the PBE|| [[User:Nod|Nod Huang]] || Nov 30, 2007 || 1. PBE file system 2. how to create a new package in PBE 3. PBE file system 4. how to create a new package in PBE || [[Media:PBE.pdf|PBE.pdf]] <br />
|-<br />
|Power consumption in kernel|| [[User:Willie|Willie Chen]] || Dec 7, 2007 || 1. How to reduce power consumption 2. Utilities 3. GTA01/GTA02 issues || [[Media:power.pdf|Power]]<br />
|-<br />
|ARM Exception System Introduction (HXD8 example)|| [[User:Alec|Alec Tsai]] || Jan 11, 2008 || 1. Exceptions 2. System Memory Map || [[Media:Exception.pdf|Exception]]<br />
|-<br />
| Object files Introduction|| [[User:tick | Tick]] || Feb, 22 2008 || A brief introductions to a.out and ELF || [[Media:elf.pdf| ELF]]<br />
|- <br />
| Kboot || [[User:werner| Werner]] || Feb, 29 2009 || An introduction and discussion about Kboot ||<br />
|- <br />
| Small introduction to Qtopia || [[User: zecke | Zecke]] || Mar, 07 2008 || A small introduction to Qtopia || [[Media: qtopia.pdf | Qtopia]]<br />
|-<br />
| Some daemons in OM-2007.2|| [[User:olv | olv]] || Mar, 14 2008 || A brief introduction to daemons running behind OM-2007.2 || [[Media:om-daemons.pdf| om-daemons.pdf]]<br />
|-<br />
| Introduce to Audio || [[User:graeme | Graeme]] || Mar, 21 2008 || An introduction to the Audio system || [[Media: audio_presentation.pdf | Audio]]<br />
|}<br />
<br />
[[Category:Training| ]]</div>Erinhttp://wiki.openmoko.org/wiki/PrototypesPrototypes2008-03-18T02:52:49Z<p>Erin: /* #60 GTA02 A5 */</p>
<hr />
<div>Prototypes are pieces of hardware such as boards, fully assembled devices, batteries, accessories that OpenMoko uses during the development of new hardware.<br />
<br />
This page tracks such prototypes, in which condition their life started, and what happened to them during their lifetime.<br />
<br />
Prototypes cannot be purchased. They will be loaned out on a case by case basis, and collected back for post mortem analysis.<br />
<br />
If you believe you need a prototype of some upcoming hardware, please mailto:openmoko-kernel@lists.openmoko.org.<br />
<br />
=== #65 GTA02 A5 ===<br />
current holder: Michael Shiloh<br><br />
06 Mar 2008 Ship to Michael Shiloh with coulomb battery<br><br />
05 Mar 2008 Finish CMU-200 test<br><br />
04 Mar 2008 850 Band re-work and add IR resistor for power saving<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #64 GTA02 A5 ===<br />
current holder: Martin/Hardware <br><br />
11 Mar 2008 USB DFU fail<br><br />
05 Mar 2008 Finish CMU-200 test<br><br />
04 Mar 2008 850 Band re-work and add IR resistor for power saving<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #63 GTA02 A5 ===<br />
current holder: Felipe Balbi<br><br />
11 Mar 2008 Sean doing 1800 band stability test<br><br />
05 Mar 2008 Finish CMU-200 test, but once unstable boot into kernel<br><br />
04 Mar 2008 850 Band re-work and add IR resistor for power saving<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #62 GTA02 A5 ===<br />
current holder: Raster<br><br />
07 Mar 2008 Transfer to Raster for another developer about graphics work<br><br />
03 Mar 2008 Tony use for DM/u-boot verification<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #61 GTA02 A5 ===<br />
current holder: Matt<br><br />
29 Feb 2008 Matt for GSM test usage<br><br />
29 Feb 2008 Allen GSM IR resistor rework<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #60 GTA02 A5 ===<br />
current holder: Erin<br><br />
17 Mar 2008 upgrade GSM firmware to moko7 and write IMEI code<br><br />
17 Mar 2008 Use devirginator to load all latest images from buildhost (20080317) <br><br />
17 Mar 2008 Check device status, and then will send it to M. Dietrich <br><br />
10 Mar 2008 GPS antenna is broken <br><br />
29 Feb 2008 Matt for GSM test usage<br><br />
29 Feb 2008 Allen GSM IR resistor rework<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #59 GTA02 A5 ===<br />
current holder: Martin<br><br />
17 Mar 2008 Hardware battery charging test<br><br />
12 Mar 2008 All sound output fail<br><br />
29 Feb 2008 Allen GSM IR resistor rework<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #58 GTA02 A5 ===<br />
current holder: TRIsoft<br><br />
07 Mar 2008 TRIsoft for testing<br><br />
03 Mar 2008 Harry bring to Cebit Show<br><br />
28 Feb 2008 Tony for DM test usage<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #57 Highcell battery 3.6V 1200mAh with Coulomb counter ===<br />
current holder: Allen Chang<br><br />
28 Feb 2008 With correct terminal voltage 3.6 vot 0% setting on bq27000<br />
<br />
=== #56 Highcell battery 3.6V 1200mAh with Coulomb counter ===<br />
current holder: Tony<br><br />
28 Feb 2008 With correct terminal voltage 3.6 vot 0% setting on bq27000<br />
<br />
=== #55 Highcell battery 3.6V 1200mAh with Coulomb counter ===<br />
current holder: Andy<br><br />
28 Feb 2008 With correct terminal voltage 3.6 vot 0% setting on bq27000<br />
<br />
=== #54 Highcell battery 3.6V 1200mAh with Coulomb counter ===<br />
current holder: Miles<br><br />
28 Feb 2008 With correct terminal voltage 3.6 vot 0% setting on bq27000<br />
<br />
=== #53 Highcell battery 3.6V 1200mAh with Coulomb counter ===<br />
current holder: Matt<br><br />
28 Feb 2008 With correct terminal voltage 3.6 vot 0% setting on bq27000<br />
<br />
=== #52 GTA02 A5 ===<br />
current holder: Wolfgang<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br />
<br />
=== #51 GTA02 A5 ===<br />
current holder: Martin<br><br />
17 Mar 2008 Hardware battery charging battery test<br><br />
12 Mar 2008 DFU always fail, USB connection broken all the time<br><br />
05 Mar 2008 Finish u-boot test, and return to tony <br><br />
29 Feb 2008 hardware side fixed 911 key and receiver issue.<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio, 911 key no switch, receiver broken<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #50 GTA02 A5 ===<br />
current holder: Sean<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth working (!)<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #49 GTA02 A5 ===<br />
current holder: OLV<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #48 GTA02 A5 ===<br />
current holder: Hoger<br><br />
05 Mar 2008 Transfer to Hoger<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth radio very weak<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #47 GTA02 A5 ===<br />
current holder: Michael Dietrich<br><br />
27 Feb 2008 Transfered to Will, sent to Michael<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth radio very weak<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #46 GTA02 A5 ===<br />
current holder: Thomas<br><br />
06 Mar 2008 Mail to o-hand Thomas as GTA02v4 replacement, with coulomb battery<br><br />
27 Feb 2008 Add PMU capacitor<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio, 911 key no switch<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #45 GTA02 A5 ===<br />
current holder: Jeremy<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #44 unlucky number ===<br />
<br />
=== #43 GTA02 A5 ===<br />
current holder: Miles<br><br />
21 Feb 2008 to Miles for DM2 partition verification<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #42 GTA02 A5 ===<br />
current holder: Julian<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio, weak vibrator<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #41 GTA02 A5 ===<br />
current holder: Lorn Potter (Trolltech)<br><br />
22 Feb 2008 sent to Lorn Potter, Trolltech<br><br />
22 Feb 2008 Tony: ran DM2 (without wifi), Bluetooth no radio<br><br />
22 Feb 2008 Tony: replaced receiver<br><br />
21 Feb 2008 Earphone broken in the package<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio, receiver broken<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #40 GTA02 A5 ===<br />
current holder: Tick<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #39 GTA02 A5 ===<br />
current holder: Sean Chiang<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #38 GTA02 A5 ===<br />
current holder: Andy<br><br />
21 Feb 2008: run DM2 (without wifi), no issues, Bluetooth working (!)<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #37 GTA02 A5 ===<br />
current holder: Lorn Potter (Trolltech)<br><br />
22 Feb 2008 sent to Lorn Potter, Trolltech<br><br />
21 Feb 2008 run DM2 (without wifi), no issues, Bluetooth working (!)<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #36 GTA02 A5 ===<br />
current holder: Graeme (FOSDEM)<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio, LCM cracked<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #35 GTA02 A5 ===<br />
current holder: Dodji (FOSDEM)<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #34 GTA02 A5 ===<br />
current holder: Martin<br><br />
05 Mar 2008 Return to hardware side for GPS antenna switch second source test<br><br />
20 Feb 2008 run DM2 (without wifi), receiver broken, 911 key broken, Bluetooth scan not working, Tony thinks device may have been drop-tested!<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #33 GTA02 A5 ===<br />
current holder: Erin<br><br />
22 Feb 2008 Erin: load daily build rootfs '0220-fic-gta02.rootfs.jffs2' and kernel 'uImage-2.6.24+svnr4096-r4055-r3-neo1973.bin'. gsmd is running OK, can receive/dial out calls. but no ringtone for incoming calls.<br><br />
20 Feb 2008 run DM2 (without wifi), Bluetooth scan not working, vibrator very weak<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #32 GTA02 A5 ===<br />
current holder: Miles<br><br />
20 Feb 2008 run DM2 (without wifi), Bluetooth scan not working<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #31 GTA02 A5 ===<br />
current holder: Andy<br><br />
20 Feb 2008 run DM2 (without wifi), Bluetoosh Scan only found 1 out of 3 devices<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #30 GTA02 A5 ===<br />
current holder: Mickey<br/><br />
<del>24 Feb 2008 '''issue found''': Headphone Jack GPIO is floating, receiving 500 IRQ's per second, making the system crawl like it has only 50MHz (or less...)<br/></del><br />
<del>24 Feb 2008 '''issue found''': Once sound is initialized, it emits two loud cracks per second<br/></del><br />
24 Feb 2008 '''issue found''': Vibrator is very weak<br/><br />
23 Feb 2008 flash NOR-enabled U-Boot, flash kernel+rootfs<br/><br />
20 Feb 2008 run DM2 (without wifi), no issues found<br/><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br/><br />
<br />
=== #29 Highcell battery 3.7V 1200mAh with Coulomb counter ===<br />
current holder: Andy<br />
<br />
=== #28 Highcell battery 3.7V 1200mAh with Coulomb counter ===<br />
current holder: Tony Tu<br />
<br />
=== #27 GTA02 A5 ===<br />
current holder: Willie<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
18 Feb 2008 Willie: LCD seems be broken. Screen shows three lines.<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #26 GTA02 A5 ===<br />
current holder: Allen Lin<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #25 GTA02 A5 ===<br />
current holder: Raster<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #24 GTA02 A5 ===<br />
current holder: John<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #23 GTA02 A5 ===<br />
current holder: JJ, battery vendor<br><br />
12 Feb 2008 Willie: Install kernel image from lastest svn check out<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #22 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
15 Feb 2008 Tony: Back to hardware team<br><br />
13 Feb 2008 Erin: gsm modem is bad <br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #21 GTA02 A5 ===<br />
current holder: Matt<br><br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad, GPS broken<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #20 GTA02 A5 ===<br />
current holder: Martin<br><br />
05 Mar 2008 GPS antenna switch 2nd source test<br><br />
21 Feb 2008 Miles: factory partition broken<br> <br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad<br><br />
13 Feb 2008 Miles take from Tony for PBE comparsion test<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #19 GTA02 A5 ===<br />
current holder: Brenda<br><br />
27 Feb Add PMU capacitor<br><br />
21 Feb 2008 Tony: Add WiFi FW 2.0.0.89<br><br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #18 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
15 Feb 2008 Willie: Send to hardware side and fix it. <br />
12 Feb 2008 Willie: It will generate big noise, maybe it's a hardware issue. I will check this <br><br />
12 Feb 2008 Erin: after booting to UI, the screen freezes, no any response. Willie is checking it now <br><br />
09 Feb 2008 Erin: load uboot, kernel, rootfs by Sean Chiang, it can auto-camp to the network, can use dialer<br> <br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #17 GTA02 A5 ===<br />
current holder: Vitaly (Atheros)<br><br />
01 Feb 2008 Delivered to Vitaly, Atheros<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #16 GTA02 A5 ===<br />
current holder: Samuel<br><br />
31 Jan 2008 Sent to Samuel<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #15 GTA02 A5 ===<br />
current holder: Tony<br><br />
12 Mar 2008 Wi-fi module still old one, and the DFU fail, USB connection un-steady<br />
31 Jan 2008 Running from battery shuts down 5 seconds after reboot. Running from power source (plugged into battery connectors) is stable<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #14 GTA02 A5 ===<br />
current holder: Willie<br><br />
27 Feb 2008 Willie: Get second phone<br><br />
21 Feb 2008 Tony: switched wifi to FW 2.0.0.89<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #13 GTA02 A5 ===<br />
current holder: Tony<br><br />
29 Jan 2008 Miles: Bluetooth scan doesn't work, Power Key broken<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #12 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
21 Jan 2008 Allen: Added Bluetooth module, reworked for power measurements, broken<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #11 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
21 Jan 2008 Allen: Added Bluetooth module, reworked for power measurements, broken<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #10 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
Die. Because I connect the power supply and usb. Then I shutdown the power supply, and power on the power supply. Quickly, the phone is short.<br />
<br />
=== #9 GTA02 A5 ===<br />
current holder: Matt<br><br />
5 Feb 2008 There are some hardware components broken. The behavior of i2c accessing is strange. And its suspend current is quite high (14~15mA).<br><br />
29 Jan 2008 Matt: Found out jack insert interrupt line is floating<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #8 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
21 Jan 2008 Allen: Added Bluetooth module, reworked for power measurements, broken<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #7 GTA02 A5 ===<br />
current holder: Smedia<br><br />
03 Mar 2008 Transfer to SMedia for flicker test<br />
27 Feb 2008 Add PMU capacitor<br><br />
21 Feb 2008 Tony: added receiver, switched to wifi FW 2.0.0.89<br><br />
05 Feb 2008 Miles: removed receiver<br><br />
29 Jan 2008 Miles: receiver test failed (receiver broken)<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #6 Highcell battery 3.7V 1200mAh with Coulomb counter ===<br />
current holder: Tony<br><br />
29 Jan 2008 Willie: verified<br />
<br />
=== #5 Highcell battery 3.7V 1200mAh with Coulomb counter ===<br />
current holder: Andy<br><br />
29 Jan 2008 sent to Andy<br><br />
29 Jan 2008 Willie: verified<br />
<br />
=== #4 Highcell battery 3.7V 1200mAh with Coulomb counter (Tony) ===<br />
current holder: Tony<br><br />
04 Mar 2008 Returned to Tony who gave me two "end user" batteries instead.<br><br />
08 Feb 2008 Got it. Passes power-on test.<br><br />
30 Jan 2008 sent to Werner<br><br />
29 Jan 2008 Willie: verified<br />
<br />
=== #3 GTA02 A5 ===<br />
current holder: Tony<br><br />
05 Feb 2008 Found solution: added capacitor<br><br />
02 Feb 2008 I see similar behaviour to #15 today on battery + USB. Appears to be related to, eg, starting LCM backlight making power problems resulting in immediate shutdown. Current limit issue somehow?<br><br />
01 Feb 2008 Behaving well.<br><br />
29 Jan 2008 sent to Andy<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #2 GTA02 A5 ===<br />
current holder: Harald<br><br />
29 Jan 2008 sent to Harald<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #1 GTA02 A5 (Werner) ===<br />
current holder: Werner<br><br />
05 Mar 2008 Vibrator seems to be broken or unnoticeably weak<br><br />
04 Mar 2008 SD/MMC seems broken under Linux (same usage works fine on #51; u-boot can read from it)<br><br />
11 Feb 2008 Verified NOR WP (with reworked debug v3)<br><br />
09 Feb 2008 Rework: bypass VB_SYS with 10uF 0603 6V3 cer X5R<br><br />
08 Feb 2008 Got it. Passes power-on test.<br><br />
30 Jan 2008 sent to Werner<br><br />
30 Jan 2008 Miles: verified hardware, same exceptions as below<br><br />
30 Jan 2008 Allen Chang: reworked to add NOR protection (R2505 closed, R2506 opened)<br><br />
29 Jan 2008 Miles: verified hardware, except for<br />
* microSD<br />
* suspend/resume<br />
* Bluetooth audio<br />
* Coulomb counter & motion sensor only low-level verification (no drivers)<br />
* USB host only low-level verification (no device)<br />
* charging (only 500mA verified), running on USB only, switching between charging modes<br />
* full memory verification<br />
* wakeup interrupts (WiFi, USB, GSM, motion sensors, 2 buttons, RTC, headphone jack)<br />
28 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
28 Jan 2008 Tony: Rework wifi FW to 2.0.0.40<br><br />
28 Jan 2008 Batch of 10 from Suzhou, PCBA with all modules, wifi FW 1.3, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
[[Category:GTA02 Hardware]]</div>Erinhttp://wiki.openmoko.org/wiki/GSM_network_registrationGSM network registration2008-03-17T13:44:15Z<p>Erin: </p>
<hr />
<div>We'd like to know the real network registration status by our NEO devices in the world. Please provide some information about your NEO status! The question list as below:<br />
<br />
1. What NEO device you are using? GTA01 or GTA02<br />
<br />
2. Where is your location and what is your network provider? eg. T-Mobile, San Francisco in USA<br />
<br />
3. When you boot the NEO, how long it takes to register the network? eg. in normal case, it should be able to register to a network in 1~2 minutes immediately.<br />
<br />
4. What is your GSM firmware version? you can get this number by an AT command. Using SSH to your NEO, then type this command:<br />
[http://wiki.openmoko.org/wiki/USB_Networking How to use SSH] [http://wiki.openmoko.org/wiki/Gsmd How to use libgsmd-tool]<br />
root@fic-gta02:~# libgsmd-tool -m atcmd<br />
AT+CGMR<br />
STR=`AT+CGMR'<br />
RSTR=`+CGMR: "HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6"'<br />
<br />
5. What is your IMEI code? by this AT command like previous steps.<br />
AT+CGSN<br />
STR=`AT+CGSN' <br />
RSTR=`+CGSN: 000000000000000'<br />
<br />
6. if NEO takes over 3 minutes to register to the network or it just re-register to the network again and again. Please attach your gsm log file ('/tmp/gsm.log') to our bugzilla, we already created a bug for [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1024 this issue].<br />
<br />
<br />
----<br />
<br />
<br />
<br />
{| border="1"<br />
| Owner || Location ||| Network Provider || Device || firmware || IMEI || Status || GSM log<br />
|-<br />
| [mailto:erin_yueh@openmoko.com Erin Yueh] || Taipei, Taiwan || TW mobile || GTA02BV5 || Moko6 || NO || Normal, can register to the network immediately|| no<br />
|-<br />
| [mailto:marcus.bauer@gmail.com Marcus Bauer] || Nice, France || Orange || GTA01Bv4 || Moko4 || YES || Registers immediately and stays registered for ~10 minutes before the re-registering loop starts once per minute|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=554&action=view log]<br />
|}</div>Erinhttp://wiki.openmoko.org/wiki/GSM_network_registrationGSM network registration2008-03-17T13:43:22Z<p>Erin: </p>
<hr />
<div>We'd like to know the real network registration status by our NEO devices in the world. Please provide some information about your NEO status! The question list as below:<br />
<br />
1. What NEO device you are using? GTA01 or GTA02<br />
<br />
2. Where is your location and what is your network provider? eg. T-Mobile, San Francisco in USA<br />
<br />
3. When you boot the NEO, how long it takes to register the network? eg. in normal case, it should be able to register to a network in 1~2 minutes immediately.<br />
<br />
4. What is your GSM firmware version? you can get this number by an AT command. Using SSH to your NEO, then type this command:<br />
<br />
root@fic-gta02:~# libgsmd-tool -m atcmd<br />
AT+CGMR<br />
STR=`AT+CGMR'<br />
RSTR=`+CGMR: "HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6"'<br />
<br />
5. What is your IMEI code? by this AT command like previous steps.<br />
AT+CGSN<br />
STR=`AT+CGSN' <br />
RSTR=`+CGSN: 000000000000000'<br />
<br />
6. if NEO takes over 3 minutes to register to the network or it just re-register to the network again and again. Please attach your gsm log file ('/tmp/gsm.log') to our bugzilla, we already created a bug for [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1024 this issue].<br />
<br />
[http://wiki.openmoko.org/wiki/USB_Networking How to use SSH] [http://wiki.openmoko.org/wiki/Gsmd How to use libgsmd-tool]<br />
<br />
----<br />
<br />
{| border="1"<br />
| Owner || Location ||| Network Provider || Device || firmware || IMEI || Status || GSM log<br />
|-<br />
| [mailto:erin_yueh@openmoko.com Erin Yueh] || Taipei, Taiwan || TW mobile || GTA02BV5 || Moko6 || NO || Normal, can register to the network immediately|| no<br />
|-<br />
| [mailto:marcus.bauer@gmail.com Marcus Bauer] || Nice, France || Orange || GTA01Bv4 || Moko4 || YES || Registers immediately and stays registered for ~10 minutes before the re-registering loop starts once per minute|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=554&action=view log]<br />
|}</div>Erinhttp://wiki.openmoko.org/wiki/GSM_network_registrationGSM network registration2008-03-17T13:40:29Z<p>Erin: </p>
<hr />
<div>We'd like to know the real network registration status by our NEO devices in the world. Please provide some information about your NEO status! The question list as below:<br />
<br />
1. What NEO device you are using? GTA01 or GTA02<br />
<br />
2. Where is your location and what is your network provider? eg. T-Mobile, San Francisco in USA<br />
<br />
3. When you boot the NEO, how long it takes to register the network? eg. in normal case, it should be able to register to a network in 1~2 minutes immediately.<br />
<br />
4. What is your GSM firmware version? you can get this number by an AT command. Using SSH to your NEO, then type this command:<br />
<br />
root@fic-gta02:~# libgsmd-tool -m atcmd<br />
AT+CGMR<br />
STR=`AT+CGMR'<br />
RSTR=`+CGMR: "HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6"'<br />
<br />
5. What is your IMEI code? by this AT command like previous steps.<br />
AT+CGSN<br />
STR=`AT+CGSN' <br />
RSTR=`+CGSN: 000000000000000'<br />
<br />
6. if NEO takes over 3 minutes to register to the network or it just re-register to the network again and again. Please attach your gsm log file ('/tmp/gsm.log') to our bugzilla, we already created a bug for [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1024 this issue].<br />
<br />
[http://wiki.openmoko.org/wiki/USB_Networking How to use SSH] [http://wiki.openmoko.org/wiki/Gsmd How to use libgsmd-tool]<br />
<br />
----<br />
<br />
{| border="1"<br />
| Owner || Location ||| Network Provider || Device || firmware || IMEI || Status || GSM log<br />
|-<br />
| [mailto:erin_yueh@openmoko.com Erin Yueh] || Taipei, Taiwan || TW mobile || GTA02BV5 || Moko6 || NO || Normal, can register to the network immediately|| no<br />
|-<br />
| [mailto:marcus.bauer@gmail.com Marcus Bauer] || Nice, France || Orange || GTA01Bv4 || Moko4 || YES || Registers immediately and stays registered for ~10 minutes before the<br />
re-registering loop starts once per minute || [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=554&action=view log]<br />
|}</div>Erinhttp://wiki.openmoko.org/wiki/GSM_network_registrationGSM network registration2008-03-17T13:39:01Z<p>Erin: </p>
<hr />
<div>We'd like to know the real network registration status by our NEO devices in the world. Please provide some information about your NEO status! The question list as below:<br />
<br />
1. What NEO device you are using? GTA01 or GTA02<br />
<br />
2. Where is your location and what is your network provider? eg. T-Mobile, San Francisco in USA<br />
<br />
3. When you boot the NEO, how long it takes to register the network? eg. in normal case, it should be able to register to a network in 1~2 minutes immediately.<br />
<br />
4. What is your GSM firmware version? you can get this number by an AT command. Using SSH to your NEO, then type this command:<br />
<br />
root@fic-gta02:~# libgsmd-tool -m atcmd<br />
AT+CGMR<br />
STR=`AT+CGMR'<br />
RSTR=`+CGMR: "HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6"'<br />
<br />
5. What is your IMEI code? by this AT command like previous steps.<br />
AT+CGSN<br />
STR=`AT+CGSN' <br />
RSTR=`+CGSN: 000000000000000'<br />
<br />
6. if NEO takes over 3 minutes to register to the network or it just re-register to the network again and again. Please attach your gsm log file ('/tmp/gsm.log') to our bugzilla, we already created a bug for [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1024 this issue].<br />
<br />
[http://wiki.openmoko.org/wiki/USB_Networking How to use SSH] [http://wiki.openmoko.org/wiki/Gsmd How to use libgsmd-tool]<br />
<br />
----<br />
<br />
{| border="1"<br />
| Owner || Location ||| Network Provider || Device || firmware || IMEI || Status || GSM log<br />
|-<br />
| [mailto:erin_yueh@openmoko.com Erin Yueh] || Taipei, Taiwan || TW mobile || GTA02BV5 || Moko6 || NO || Normal, can register to the network immediately|| no<br />
|-<br />
| [mailto:marcus.bauer@gmail.com Marcus Bauer] || Nice, France || Orange || GTA01Bv4 || Moko4 || YES || Registers immediately and stays registered for ~10 minutes before the<br />
re-registering loop starts once per minute || [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=554&action=view log]<br />
|}</div>Erinhttp://wiki.openmoko.org/wiki/GSM_network_registrationGSM network registration2008-03-17T13:38:30Z<p>Erin: </p>
<hr />
<div>We'd like to know the real network registration status by our NEO devices in the world. Please provide some information about your NEO status! The question list as below:<br />
<br />
1. What NEO device you are using? GTA01 or GTA02<br />
<br />
2. Where is your location and what is your network provider? eg. T-Mobile, San Francisco in USA<br />
<br />
3. When you boot the NEO, how long it takes to register the network? eg. in normal case, it should be able to register to a network in 1~2 minutes immediately.<br />
<br />
4. What is your GSM firmware version? you can get this number by an AT command. Using SSH to your NEO, then type this command:<br />
<br />
root@fic-gta02:~# libgsmd-tool -m atcmd<br />
AT+CGMR<br />
STR=`AT+CGMR'<br />
RSTR=`+CGMR: "HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6"'<br />
<br />
5. What is your IMEI code? by this AT command like previous steps.<br />
AT+CGSN<br />
STR=`AT+CGSN' <br />
RSTR=`+CGSN: 000000000000000'<br />
<br />
6. if NEO takes over 3 minutes to register to the network or it just re-register to the network again and again. Please attach your gsm log file ('/tmp/gsm.log') to our bugzilla, we already created a bug for [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1024 this issue].<br />
<br />
[http://wiki.openmoko.org/wiki/USB_Networking How to use SSH] [http://wiki.openmoko.org/wiki/Gsmd How to use libgsmd-tool]<br />
<br />
----<br />
<br />
{| border="1"<br />
| Owner || Location ||| Network Provider || Device || firmware || IMEI || Status || GSM log<br />
|-<br />
| [mailto:erin_yueh@openmoko.com Erin Yueh] || Taipei, Taiwan || TW mobile || GTA02BV5 || Moko6 || NO || Normal, can register to the network immediately|| no<br />
|-<br />
| [mailto:marcus.bauer@gmail.com Marcus Bauer] || Nice, France || Orange || GTA01Bv4 || Moko4 || YES || Registers immediately and stays registered for ~10 minutes before the<br />
re-registering loop starts once per minute || [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=554&action=view log]<br />
|}</div>Erinhttp://wiki.openmoko.org/wiki/GSM_network_registrationGSM network registration2008-03-17T13:37:44Z<p>Erin: </p>
<hr />
<div>We'd like to know the real network registration status by our NEO devices in the world. Please provide some information about your NEO status! The question list as below:<br />
<br />
1. What NEO device you are using? GTA01 or GTA02<br />
<br />
2. Where is your location and what is your network provider? eg. T-Mobile, San Francisco in USA<br />
<br />
3. When you boot the NEO, how long it takes to register the network? eg. in normal case, it should be able to register to a network in 1~2 minutes immediately.<br />
<br />
4. What is your GSM firmware version? you can get this number by an AT command. Using SSH to your NEO, then type this command:<br />
<br />
root@fic-gta02:~# libgsmd-tool -m atcmd<br />
AT+CGMR<br />
STR=`AT+CGMR'<br />
RSTR=`+CGMR: "HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6"'<br />
<br />
5. What is your IMEI code? by this AT command like previous steps.<br />
AT+CGSN<br />
STR=`AT+CGSN' <br />
RSTR=`+CGSN: 000000000000000'<br />
<br />
6. if NEO takes over 3 minutes to register to the network or it just re-register to the network again and again. Please attach your gsm log file ('/tmp/gsm.log') to our bugzilla, we already created a bug for [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1024 this issue].<br />
<br />
[http://wiki.openmoko.org/wiki/USB_Networking How to use SSH] [http://wiki.openmoko.org/wiki/Gsmd How to use libgsmd-tool]<br />
<br />
----<br />
<br />
{| border="1"<br />
| Owner || Location ||| Network Provider || Device || firmware || IMEI || Status || GSM log<br />
|-<br />
| [mailto:erin_yueh@openmoko.com Erin Yueh] || Taipei, Taiwan || TW mobile || GTA02BV5 || Moko6 || NO || Normal, can register to the network immediately|| no<br />
|-<br />
| [mailto:marcus.bauer@gmail.com Marcus Bauer] || Nice, France || Orange || GTA01Bv4 || Moko4 || YES || Registers immediately and stays registered for ~10 minutes before the<br />
re-registering loop starts once per minute || [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=554&action=view log]<br />
|}</div>Erinhttp://wiki.openmoko.org/wiki/GSM_network_registrationGSM network registration2008-03-17T13:33:54Z<p>Erin: </p>
<hr />
<div>We'd like to know the real network registration status by our NEO devices in the world. Please provide some information about your NEO status! The question list as below:<br />
<br />
1. What NEO device you are using? GTA01 or GTA02<br />
<br />
2. Where is your location and what is your network provider? eg. T-Mobile, San Francisco in USA<br />
<br />
3. When you boot the NEO, how long it takes to register the network? eg. in normal case, it should be able to register to a network in 1~2 minutes immediately.<br />
<br />
4. What is your GSM firmware version? you can get this number by an AT command. Using SSH to your NEO, then type this command:<br />
<br />
root@fic-gta02:~# libgsmd-tool -m atcmd<br />
AT+CGMR<br />
STR=`AT+CGMR'<br />
RSTR=`+CGMR: "HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6"'<br />
<br />
5. What is your IMEI code? by this AT command like previous steps.<br />
AT+CGSN<br />
STR=`AT+CGSN' <br />
RSTR=`+CGSN: 000000000000000'<br />
<br />
6. if NEO takes over 3 minutes to register to the network or it just re-register to the network again and again. Please attach your gsm log file ('/tmp/gsm.log') to our bugzilla, we already created a bug for [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1024 this issue].<br />
<br />
[http://wiki.openmoko.org/wiki/USB_Networking How to use SSH] [http://wiki.openmoko.org/wiki/Gsmd How to use libgsmd-tool]<br />
<br />
----<br />
<br />
{| border="1"<br />
| Location || Network Provider || Device || firmware || IMEI || Status || GSM log<br />
|-<br />
| Taipei, Taiwan || TW mobile || GTA02BV5 || Moko6 || NO || Normal, can register to the network immediately|| no<br />
|-<br />
| Nice, France || Orange || GTA01Bv4 || Moko4 || YES || Registers immediately and stays registered for ~10 minutes before the<br />
re-registering loop starts once per minute.|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=554&action=view log]<br />
|}</div>Erinhttp://wiki.openmoko.org/wiki/GSM_network_registrationGSM network registration2008-03-17T13:30:18Z<p>Erin: </p>
<hr />
<div>We'd like to know the real network registration status by our NEO devices in the world. Please provide some information about your NEO status! The question list as below:<br />
<br />
1. What NEO device you are using? GTA01 or GTA02<br />
<br />
2. Where is your location and what is your network provider? eg. T-Mobile, San Francisco in USA<br />
<br />
3. When you boot the NEO, how long it takes to register the network? eg. in normal case, it should be able to register to a network in 1~2 minutes immediately.<br />
<br />
4. What is your GSM firmware version? you can get this number by an AT command. Using SSH to your NEO, then type this command:<br />
<br />
root@fic-gta02:~# libgsmd-tool -m atcmd<br />
AT+CGMR<br />
STR=`AT+CGMR'<br />
RSTR=`+CGMR: "HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6"'<br />
<br />
5. What is your IMEI code? by this AT command like previous steps.<br />
AT+CGSN<br />
STR=`AT+CGSN' <br />
RSTR=`+CGSN: 000000000000000'<br />
<br />
6. if NEO takes over 3 minutes to register to the network or it just re-register to the network again and again. Please attach your gsm log file ('/tmp/gsm.log') to our bugzilla, we already created a bug for [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1024 this issue].<br />
<br />
[http://wiki.openmoko.org/wiki/USB_Networking How to use SSH] [http://wiki.openmoko.org/wiki/Gsmd How to use libgsmd-tool]<br />
<br />
----<br />
<br />
{| border="1"<br />
| Location || Network Provider || Device || firmware || IMEI || GSM log<br />
|-<br />
| Taipei, Taiwan || TW mobile || GTA02 || HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6 || NO || GSM log<br />
|-<br />
| Nice, France || Orange || GTA01 || HW: GTA01Bv4, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko4"'em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko4 || YES || [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=554&action=view log]<br />
|}</div>Erinhttp://wiki.openmoko.org/wiki/GSM_network_registrationGSM network registration2008-03-17T13:26:03Z<p>Erin: </p>
<hr />
<div>We'd like to know the real network registration status by our NEO devices in the world. Please provide some information about your NEO status! The question list as below:<br />
<br />
1. What NEO device you are using? GTA01 or GTA02<br />
<br />
2. Where is your location and what is your network provider? eg. T-Mobile, San Francisco in USA<br />
<br />
3. When you boot the NEO, how long it takes to register the network? eg. in normal case, it should be able to register to a network in 1~2 minutes immediately.<br />
<br />
4. What is your GSM firmware version? you can get this number by an AT command. Using SSH to your NEO, then type this command:<br />
<br />
root@fic-gta02:~# libgsmd-tool -m atcmd<br />
AT+CGMR<br />
STR=`AT+CGMR'<br />
RSTR=`+CGMR: "HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6"'<br />
<br />
5. What is your IMEI code? by this AT command like previous steps.<br />
AT+CGSN<br />
STR=`AT+CGSN' <br />
RSTR=`+CGSN: 000000000000000'<br />
<br />
6. if NEO takes over 3 minutes to register to the network or it just re-register to the network again and again. Please attach your gsm log file ('/tmp/gsm.log') to our bugzilla, we already created a bug for [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1024 this issue].<br />
<br />
[http://wiki.openmoko.org/wiki/USB_Networking How to use SSH] [http://wiki.openmoko.org/wiki/Gsmd How to use libgsmd-tool]<br />
<br />
----<br />
<br />
{| border="1"<br />
| Location || Network Provider || Device || firmware || IMEI || GSM log<br />
|-<br />
| Taiwan || TW mobile || GTA02 || HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6 || 000000000000000 || GSM log<br />
|-<br />
| Taiwan || TW mobile || GTA01 || HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6 || 000000000000000 || GSM log<br />
|}</div>Erinhttp://wiki.openmoko.org/wiki/GSM_network_registrationGSM network registration2008-03-17T13:10:00Z<p>Erin: </p>
<hr />
<div>We'd like to know the real network registration status by our NEO devices in the world. Please provide some information about your NEO status! The question list as below:<br />
<br />
1. What NEO device you are using? GTA01 or GTA02<br />
<br />
2. Where is your location and what is your network provider? eg. T-Mobile, San Francisco in USA<br />
<br />
3. When you boot the NEO, how long it takes to register the network? eg. in normal case, it should be able to register to a network in 1~2 minutes immediately.<br />
<br />
4. What is your GSM firmware version? you can get this number by an AT command. Using SSH to your NEO, then type this command:<br />
<br />
root@fic-gta02:~# libgsmd-tool -m atcmd<br />
AT+CGMR<br />
STR=`AT+CGMR'<br />
RSTR=`+CGMR: "HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6"'<br />
<br />
5. What is your IMEI code? by this AT command like previous steps.<br />
AT+CGSN<br />
STR=`AT+CGSN' <br />
RSTR=`+CGSN: 000000000000000'<br />
<br />
6. if NEO takes over 3 minutes to register to the network or it just re-register to the network again and again. Please attach your gsm log file ('/tmp/gsm.log') to our bugzilla, we already created a bug for [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1024 this issue].<br />
<br />
[http://wiki.openmoko.org/wiki/USB_Networking How to use SSH] [http://wiki.openmoko.org/wiki/Gsmd How to use libgsmd-tool]<br />
<br />
----</div>Erinhttp://wiki.openmoko.org/wiki/GSM_network_registrationGSM network registration2008-03-17T13:09:37Z<p>Erin: /* GSM network registration */</p>
<hr />
<div>We'd like to know the real network registration status by our NEO devices in the world. Please provide some information about your NEO status! The question list as below:<br />
<br />
1. What NEO device you are using? GTA01 or GTA02<br />
<br />
2. Where is your location and what is your network provider? eg. T-Mobile, San Francisco in USA<br />
<br />
3. When you boot the NEO, how long it takes to register the network? eg. in normal case, it should be able to register to a network in 1~2 minutes immediately.<br />
<br />
4. What is your GSM firmware version? you can get this number by an AT command. Using SSH to your NEO, then type this command:<br />
<br />
root@fic-gta02:~# libgsmd-tool -m atcmd<br />
AT+CGMR<br />
STR=`AT+CGMR'<br />
RSTR=`+CGMR: "HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6"'<br />
<br />
5. What is your IMEI code? by this AT command like previous steps.<br />
AT+CGSN<br />
STR=`AT+CGSN' <br />
RSTR=`+CGSN: 000000000000000'<br />
<br />
6. if NEO takes over 3 minutes to register to the network or it just re-register to the network again and again. Please attach your gsm log file ('/tmp/gsm.log') to our bugzilla, we already created a bug for [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1024 this issue].<br />
<br />
[http://wiki.openmoko.org/wiki/USB_Networking How to use SSH] [http://wiki.openmoko.org/wiki/Gsmd How to use libgsmd-tool]</div>Erinhttp://wiki.openmoko.org/wiki/GSM_network_registrationGSM network registration2008-03-17T10:35:08Z<p>Erin: /* GSM network registration */</p>
<hr />
<div>We'd like to know the real network registration status by our NEO devices in the world. Please provide some information about your NEO status! The question list as below:<br />
<br />
1. What NEO device you are using? GTA01 or GTA02<br />
<br />
2. Where is your location and what is your network provider? eg. T-Mobile, San Francisco in USA<br />
<br />
3. When you boot the NEO, how long it takes to register the network? eg. in normal case, it should be able to register to a network in 1~2 minutes immediately.<br />
<br />
4. What is your GSM firmware version? you can get this number by an AT command. Using SSH to your NEO, then type this command:<br />
<br />
root@fic-gta02:~# libgsmd-tool -m atcmd<br />
libgsm-tool - (C) 2006-2007 by Harald Welte and OpenMoko, Inc.<br />
This program is Free Software and has ABSOLUTELY NO WARRANTY<br />
<br />
AT+CGMR<br />
STR=`AT+CGMR'<br />
RSTR=`+CGMR: "HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6"'<br />
<br />
5. What is your IMEI code? by this AT command like previous steps.<br />
AT+CGSN<br />
STR=`AT+CGSN'<br />
RSTR=`+CGSN: 000000000000000'<br />
<br />
6. if NEO takes over 3 minutes to register to the network or it just re-register to the network again and again. Please attach your gsm log file ('/tmp/gsm.log') to our bugzilla, we already created a bug for this issue.<br />
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1024<br />
<br />
<br />
PS. Check our wiki site, if you have problems on these stuff.<br />
<br />
How to use SSH on NEO:<br />
http://wiki.openmoko.org/wiki/USB_Networking<br />
How to use libgsmd-tool:<br />
http://wiki.openmoko.org/wiki/Gsmd</div>Erinhttp://wiki.openmoko.org/wiki/Main_PageMain Page2008-03-17T10:30:53Z<p>Erin: </p>
<hr />
<div>{{Languages|Main_Page}}<br />
__NOTOC__<br />
__NOEDITSECTION__<br />
__NOTOC__<br />
{| cellspacing="5" cellpadding="0" style="padding: 2%; margin:0em 0em 1em 0em; border:1px solid #F9D163; background:#FCE9B4; width:100%" <br />
| <big>'''Welcome to the [[Openmoko]]&trade; public Wiki'''</big><br><br />
|}<br />
<br />
[[Image:GTA02.gif |200px|right|frontside]]<br />
Openmoko&trade; is an [http://en.wikipedia.org/wiki/Open_source Open Source] project under[[License| GPL and LGPL license]]. The aim of Openmoko is to build the world's first free mobile platform which runs a full X server and can therefore run most X applications. You can install any [[OpenMoko]] software over the whole range of [[OpenMoko-supported hardware|supported phones]], and if you upgrade your phone, you won't lose that software. Bugs fixed on any phone are fixed on all. <br />
<br />
The [[Neo1973 | Neo 1973 (GTA01)]] from [[FIC]] is the first of many phones that Openmoko may be used on. You can go to [https://direct.openmoko.com/ Openmoko Online Shop] to get the sales informaiton. [[Neo FreeRunner | Neo FreeRunner (GTA02)]] the new generation Openmoko mobile phone is not yet available - press [[Neo FreeRunner GTA02 Hardware| here]] to get more hardware information. Otherwise, scroll down this page for info on the development status , or you can add your nickname to those interested buying the Neo FreeRunner [[Buying_Interest_List|here]].<br />
<br />
The [[OpenMoko]] project is a community that anyone can join, to help design their ideal phone. Please join us in collaborating on the Openmoko project through any of the [[Development resources | project resources]] including this Openmoko wiki. Please see the [[Help:Contents | wiki editing help]] page for information on making contributions to this wiki. A [[Meet the Core Team | core team]] of developers funded by FIC, Inc. leads the project.<br />
<br />
To the novice, can start by use [[introduction]] page , [[Introduction#Photos|photos]], [[Introduction#Videos|videos]] and [[OPENMOKO WIKI Official Index Page | Openmoko Official Index Page]] , to take the overview of Openmoko and wiki. Moreover, the usual [[FAQ | Frequently Asked Questions]] (FAQ) and [http://lists.openmoko.org/mailman/listinfo/| mailing list] pages might be helpful. Developers may find the [[ChangeLog | change log]] an important resource. <br />
<br />
{{warning|'''The OpenMoko GUI applications are not suitable for end users yet.''' They are still in beta. Do not expect to always and reliably make and receive calls from the OpenMoko GUI. Thanks to the openness of the FIC Neo1973 hardware, there is also an alternative to the OpenMoko GUI: Qtopia 4.3.x is released under GPL and is at the edge of being usable for phone use.}}<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="5" width=100%<br />
! width=100% colspan="2" style="background:#F9D163;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | Latest status<br />
|-<br />
|valign="TOP" width="50%" style="background:#FCE9B4;border-left:5px solid white;border-bottom:5px solid white;" | <br />
* The latest Qtopia snapshot can now be successfully used to make and receive calls, to send and receive SMS and use Contacts for both. However, if you do not enable suspend, one battery will only last 3-5 hours, but in suspend, incoming calls do not wake up Qtopia! See [[Qtopia on Neo 1973]] for instructions.<br />
|valign="TOP" width="50%" style="background:#FCE9B4;border-right:5px solid white;border-bottom:5px solid white;" | <br />
* The [http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/images/neo1973/ latest build] can make and receive calls most of the time. Power management (suspend, standby time) are still experiencing problems. Reports on the new snapshots built daily (will break sometimes) are [[Snapshot_review|here]]<br />
* For the latest status updates, see [[Community_Updates|Community Updates]]<br />
|}<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="5" width=100%<br />
! width=100% colspan="2" style="background:#F9D163;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | What's Your Interest?<br />
|-<br />
|valign="TOP" width="50%" style="background:#FCE9B4;border-left:5px solid white;border-bottom:5px solid white;" | <br />
* [[Basic End-user]] - Information for end users who want basic functionality and no surprises<br />
* [[Advanced End-user]] - Information for advanced end-users who want advanced and experimental functionality but who are not programmers<br />
* [[Business Development]] - Exchange of commercial opportunities for promoting widespread end-user acceptance.<br />
|valign="TOP" width="50%" style="background:#FCE9B4;border-right:5px solid white;border-bottom:5px solid white;" | <br />
* [[Application Developer]] - Information for application developers, including ideas and specifications for applications, and tools to build them<br />
* [[System Developer]] - Information for system developers, including bootloader, kernel, and libraries<br />
* [[Hardware Developer]] - Information for hardware developers, including hardware specs and debug board<br />
|}<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="5" width=100%<br />
! width=100% colspan="2" style="background:#F9D163;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | System Specs<br />
|-<br />
|valign="TOP" width="50%" style="background:#FCE9B4;border-left:5px solid white;border-bottom:5px solid white;" | <br />
* [[Neo1973_hardware|Neo 1973 (GTA01)]] - Specs of original Neo 1973 (GTA01) Hardware<br />
* [[Neo_FreeRunner_GTA02_Hardware|Neo FreeRunner (GTA02)]] - Specs of Neo FreeRunner (GTA02) Hardware<br />
|valign="TOP" width="50%" style="background:#FCE9B4;border-right:5px solid white;border-bottom:5px solid white;" | <br />
* [[OpenMoko Core Applications]] - Applications included in the core build of OpenMoko<br />
* [[OpenMoko Community Applications]] - Featured downloadable applications from the OpenMoko community<br />
|}<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="5" width=100%<br />
! width=33% style="background:#d1d1d1;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | General<br />
! width=33% style="background:#C5FDAF;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | Developer Guides<br />
! width=33% style="background:#FDAFAF;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | Developer Reference Documentation<br />
|-<br />
|valign="TOP" style="background:#ebebeb;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;" |<br />
* [[Development resources | Project Resources]] - Provides a centralized location of all resources such as [[Development resources#Mailing_Lists|mailing lists]], [[Development resources#IRC | IRC]], and other software development oriented resources.<br />
<br />
* [[Current events]] - Information on both past and future events where FIC or OpenMoko had or will have a presence.<br />
* [http://forums.makeopensource.com/ Unofficial OpenMoko Forums] - Everyone is invited to collaborate with OpenMoko users and developers on the forums.<br />
* Most of the documentation and Wiki assumes you are using Linux; here are some notes for users of [[Other OSes]].<br />
* [[MacOS_X|Mac OS X]] - Information specific for those who use Mac OS X<br />
* [[OpenLab]] - A physical area where OpenMoko can interact with FOSS community<br />
<br />
'''Administrative + Organizational'''<br />
* [[Shipping Notes]] - Information to help FIC figure out how to ship products to you, and how much it might cost.<br />
* [[My Account]] - Ideas for what sort of account-based services FIC should provide with the phone.<br />
* [[Hear Me FIC]] - Information to help FIC know what the community wants.<br />
* [[Listen Up Community]] - Community's To-Do-List<br />
* [[Wiki Issues]] - problems/requests regarding this Wiki<br />
<br />
|valign="TOP" style="background:#E8FFDF;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;" | <br />
* [[Getting Started with your Neo1973]]<br />
* [[installation_guide|A guide for flashing and emulating the openmoko software]] (In progress, this should replace the following options)<br />
** [[Flashing_openmoko|Flashing Neo1973 with the kernel, the root filesystem and optionally u-boot.]]<br />
** [[MokoMakefile|Building OpenMoko using the MokoMakefile]]<br />
** [[Application Development Crash Course]] -A very basic how-to for the new people. <br />
** [[OpenMoko2007.2|Building OpenMoko 2007.2]]<br />
** [[Building OpenMoko 2007.1 from scratch]]<br />
*** [[Building a hello world application]]<br />
*** Old [[Building OpenMoko from scratch (pre-BBT)]]<br />
** [[Running OpenMoko on PC]]<br />
*** [[Getting OpenMoko working on host with Xoo]]<br />
*** [[Getting OpenMoko working on host with Xephyr]]<br />
*** [[How to run OpenMoko Apps on PC]]<br />
*** [[OpenMoko under QEMU]]<br />
*** [[Test Openmoko Emulation with chroot image|Test Openmoko Emulation with a Prebuilt chroot Image]]<br />
* [[Migration to bad block tolerant builds]]<br />
* [[Booting from SD]]<br />
* [[DailyBuiltImages|Getting daily built images]]<br />
<br />
|valign="TOP" style="background:#FFDADA;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;"| <br />
'''Hardware Reference Documentation'''<br />
* All [[:Category:Hardware|Hardware]] related documentation and specifications are found on the [[:Category:Hardware|Hardware page]].<br />
* The [[Neo1973 Hardware]] page provides an overview of the hardware components used by the [[:Category:Neo1973 Hardware|Neo1973 hardware platform]]. PCB photographs are also included. A [[Disassembling Neo1973 | photo disassembly story]] may be an interesting starting place.<br />
* [[:Category:Neo1973 Hardware Debugging | Neo1973 Hardware Debugging]] is assisted with the [[Debug Board | Neo1973 debug board]]. A page discussing [[Connecting Neo1973 with Debug Board v2 | debug board and Neo1973 configurations]] is also provided.<br />
<br />
'''Software Reference Documentation'''<br />
* Architectural<br />
** [[OpenMokoFramework]] - The OpenMoko Application Framework<br />
* [[Neo1973 host software]]<br />
* Device Software<br />
** Low-Level<br />
*** [[u-boot]] - The bootloader we use, including documentation for our modifications<br />
*** [[kernel]] - The Linux kernel we use, including documentation for our modifications<br />
** Userspace<br />
*** [[binary compatibility]]<br />
*** [[gsmd]] - the GSM daemon managing the GSM Modem<br />
*** [[gpsd]] - the AGPS (Assisted GPS) daemon<br />
|}<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="5" width=100%<br />
! width=33% style="background:#FCC6FF;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | OpenMoko-specific Development<br />
! width=33% style="background:#B3DDF4;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | OpenMoko Miscellaneous Development<br />
! width=33% style="background:#F5FC7F;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | Miscellaneous<br />
|-<br />
|valign="TOP" style="background:#FEE9FF;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;" | <br />
* [[Roadmap]] - Roadmap for further OpenMoko development<br />
* [[OpenEmbedded]] - The distribution-building framework<br />
* [[Toolchain]] - The toolchain we use for compilation<br />
* [[OpenMoko]] - The OpenMoko distribution<br />
** [[OpenMoko2007]] - The first intended release of it<br />
** [[OpenMoko2007.2]] - An improved release with more formalized style guidelines.<br />
** [[Userspace root image]]<br />
* [[Test Plans]] - How we test our phones<br />
* [[Prototypes]] - Tracking prototypes<br />
* [[GSM network registration]] - Tracking network registration status in the world<br />
<br />
'''User Interface Related'''<br />
* [[GUI Style Guidelines]] -- New for [[OpenMoko2007.2]]<br />
* [[Look & Feel]]<br />
** [[Artwork]]<br />
* [[Applications|Application Roadmap]]<br />
* [[Widgets]]<br />
** [[Widget Inheritance Graph]]<br />
* [[Application UI Design Recommendations]]<br />
<br />
|valign="TOP" style="background:#D4EDFB;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;" |<br />
* [[Thesis work]] <br />
* [[Freshman todo]]<br />
* [[Templates]]<br />
* [[PIM Storage]]<br />
* [[Coding Guidelines]]<br />
* [[OpenMoko#Setting_up_an_OpenMoko_SDK|How to setup the OpenMoko SDK]]<br />
* Alternative distributions for [[Neo1973]] GTA01: [[Angstrom on Neo1973]], [http://pokylinux.org Poky] [http://www.usome.com](instructions needed!)<br />
* [[License]] - How we license our code<br />
* [[Development resources]] - Describes resources for developers (lists, svn, ...)<br />
* [[Neo1973 Phase 0]] - Information for Phase 0 device owners<br />
* [[Wishlist:Neo1973 P0 Review]] - Impressions of the Phase 0 hardware device, also the Phase 0 FAQ<br />
* [[Neo1973 Phase 1]] - Information for Phase 1 device owners<br />
* [[Wishlist:Neo1973 P1 Review]] - Impressions of the Phase 1 hardware device<br />
* [[External Feeds]] - List of feeds from people blogging about OpenMoko<br />
<br />
|valign="TOP" style="background:#FCFFCD;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;" | <br />
* [[WiFi support in OpenMoko]]<br />
* [[Neo1973 and Windows]]<br />
* [[Press Coverage]] - What the press says about the OpenMoko project<br />
* [[mFAQ]] - The OpenMoko Misinformation FAQ ('''mFAQ''') - What the press '''''incorrectly''''' says about the OpenMoko project<br />
* [[OpenMoko Core Applications]] - Applications (GUI based) currently included in the main/core build of OpenMoko <br />
* [[Wish List]]s: [[Wish List - Hardware|Hardware]], [[Wishlist:BuiltInScriptingLanguage|Scripting Languages]], [[Wish List - OpenMoko Ringtones and Sounds|ringtones and sounds]]<br />
* [[Media Content]] - What types of media on the device can we use (that is non-software)?<br />
* [[Testimonials]] - How did you get to OpenMoko?<br />
* [[Buying Interest List]] - (Not official and not a pre-order page) Have you put money aside for Neo1973? Put your nick here.<br />
* Comparison with the [[iPhone]]<br />
* [[Translation]] of OpenMoko<br />
* Project applications for Google's [[Summer of code]]<br />
* Purchase OpenMoko [[SWAG]] T-Shirts!<br />
* The OpenMoko [[Trademark Policy]]<br />
|}<br />
<br />
The members of the OpenMoko community would like to thank FIC Inc. for their continued leadership of the OpenMoko project.<br />
<br />
<span id="bottom"></span><br />
<br />
[[Category:Information| ]]<br />
[[Category:Categories| ]]</div>Erinhttp://wiki.openmoko.org/wiki/PrototypesPrototypes2008-03-17T10:14:35Z<p>Erin: /* #60 GTA02 A5 */</p>
<hr />
<div>Prototypes are pieces of hardware such as boards, fully assembled devices, batteries, accessories that OpenMoko uses during the development of new hardware.<br />
<br />
This page tracks such prototypes, in which condition their life started, and what happened to them during their lifetime.<br />
<br />
Prototypes cannot be purchased. They will be loaned out on a case by case basis, and collected back for post mortem analysis.<br />
<br />
If you believe you need a prototype of some upcoming hardware, please mailto:openmoko-kernel@lists.openmoko.org.<br />
<br />
=== #65 GTA02 A5 ===<br />
current holder: Michael Shiloh<br><br />
06 Mar 2008 Ship to Michael Shiloh with coulomb battery<br><br />
05 Mar 2008 Finish CMU-200 test<br><br />
04 Mar 2008 850 Band re-work and add IR resistor for power saving<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #64 GTA02 A5 ===<br />
current holder: Martin/Hardware <br><br />
11 Mar 2008 USB DFU fail<br><br />
05 Mar 2008 Finish CMU-200 test<br><br />
04 Mar 2008 850 Band re-work and add IR resistor for power saving<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #63 GTA02 A5 ===<br />
current holder: Felipe Balbi<br><br />
11 Mar 2008 Sean doing 1800 band stability test<br><br />
05 Mar 2008 Finish CMU-200 test, but once unstable boot into kernel<br><br />
04 Mar 2008 850 Band re-work and add IR resistor for power saving<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #62 GTA02 A5 ===<br />
current holder: Raster<br><br />
07 Mar 2008 Transfer to Raster for another developer about graphics work<br><br />
03 Mar 2008 Tony use for DM/u-boot verification<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #61 GTA02 A5 ===<br />
current holder: Matt<br><br />
29 Feb 2008 Matt for GSM test usage<br><br />
29 Feb 2008 Allen GSM IR resistor rework<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #60 GTA02 A5 ===<br />
current holder: Erin<br><br />
17 Mar 2008 upgrade GSM firmware to moko7 and write IMEI code '354651019100314'<br><br />
17 Mar 2008 Use devirginator to load all latest images from buildhost (20080317) <br><br />
17 Mar 2008 Check device status, and then will send it to M. Dietrich <br><br />
10 Mar 2008 GPS antenna is broken <br><br />
29 Feb 2008 Matt for GSM test usage<br><br />
29 Feb 2008 Allen GSM IR resistor rework<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #59 GTA02 A5 ===<br />
current holder: Martin<br><br />
17 Mar 2008 Hardware battery charging test<br><br />
12 Mar 2008 All sound output fail<br><br />
29 Feb 2008 Allen GSM IR resistor rework<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #58 GTA02 A5 ===<br />
current holder: TRIsoft<br><br />
07 Mar 2008 TRIsoft for testing<br><br />
03 Mar 2008 Harry bring to Cebit Show<br><br />
28 Feb 2008 Tony for DM test usage<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #57 Highcell battery 3.6V 1200mAh with Coulomb counter ===<br />
current holder: Allen Chang<br><br />
28 Feb 2008 With correct terminal voltage 3.6 vot 0% setting on bq27000<br />
<br />
=== #56 Highcell battery 3.6V 1200mAh with Coulomb counter ===<br />
current holder: Tony<br><br />
28 Feb 2008 With correct terminal voltage 3.6 vot 0% setting on bq27000<br />
<br />
=== #55 Highcell battery 3.6V 1200mAh with Coulomb counter ===<br />
current holder: Andy<br><br />
28 Feb 2008 With correct terminal voltage 3.6 vot 0% setting on bq27000<br />
<br />
=== #54 Highcell battery 3.6V 1200mAh with Coulomb counter ===<br />
current holder: Miles<br><br />
28 Feb 2008 With correct terminal voltage 3.6 vot 0% setting on bq27000<br />
<br />
=== #53 Highcell battery 3.6V 1200mAh with Coulomb counter ===<br />
current holder: Matt<br><br />
28 Feb 2008 With correct terminal voltage 3.6 vot 0% setting on bq27000<br />
<br />
=== #52 GTA02 A5 ===<br />
current holder: Wolfgang<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br />
<br />
=== #51 GTA02 A5 ===<br />
current holder: Martin<br><br />
17 Mar 2008 Hardware battery charging battery test<br><br />
12 Mar 2008 DFU always fail, USB connection broken all the time<br><br />
05 Mar 2008 Finish u-boot test, and return to tony <br><br />
29 Feb 2008 hardware side fixed 911 key and receiver issue.<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio, 911 key no switch, receiver broken<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #50 GTA02 A5 ===<br />
current holder: Sean<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth working (!)<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #49 GTA02 A5 ===<br />
current holder: OLV<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #48 GTA02 A5 ===<br />
current holder: Hoger<br><br />
05 Mar 2008 Transfer to Hoger<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth radio very weak<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #47 GTA02 A5 ===<br />
current holder: Michael Dietrich<br><br />
27 Feb 2008 Transfered to Will, sent to Michael<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth radio very weak<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #46 GTA02 A5 ===<br />
current holder: Thomas<br><br />
06 Mar 2008 Mail to o-hand Thomas as GTA02v4 replacement, with coulomb battery<br><br />
27 Feb 2008 Add PMU capacitor<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio, 911 key no switch<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #45 GTA02 A5 ===<br />
current holder: Jeremy<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #44 unlucky number ===<br />
<br />
=== #43 GTA02 A5 ===<br />
current holder: Miles<br><br />
21 Feb 2008 to Miles for DM2 partition verification<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #42 GTA02 A5 ===<br />
current holder: Julian<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio, weak vibrator<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #41 GTA02 A5 ===<br />
current holder: Lorn Potter (Trolltech)<br><br />
22 Feb 2008 sent to Lorn Potter, Trolltech<br><br />
22 Feb 2008 Tony: ran DM2 (without wifi), Bluetooth no radio<br><br />
22 Feb 2008 Tony: replaced receiver<br><br />
21 Feb 2008 Earphone broken in the package<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio, receiver broken<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #40 GTA02 A5 ===<br />
current holder: Tick<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #39 GTA02 A5 ===<br />
current holder: Sean Chiang<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #38 GTA02 A5 ===<br />
current holder: Andy<br><br />
21 Feb 2008: run DM2 (without wifi), no issues, Bluetooth working (!)<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #37 GTA02 A5 ===<br />
current holder: Lorn Potter (Trolltech)<br><br />
22 Feb 2008 sent to Lorn Potter, Trolltech<br><br />
21 Feb 2008 run DM2 (without wifi), no issues, Bluetooth working (!)<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #36 GTA02 A5 ===<br />
current holder: Graeme (FOSDEM)<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio, LCM cracked<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #35 GTA02 A5 ===<br />
current holder: Dodji (FOSDEM)<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #34 GTA02 A5 ===<br />
current holder: Martin<br><br />
05 Mar 2008 Return to hardware side for GPS antenna switch second source test<br><br />
20 Feb 2008 run DM2 (without wifi), receiver broken, 911 key broken, Bluetooth scan not working, Tony thinks device may have been drop-tested!<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #33 GTA02 A5 ===<br />
current holder: Erin<br><br />
22 Feb 2008 Erin: load daily build rootfs '0220-fic-gta02.rootfs.jffs2' and kernel 'uImage-2.6.24+svnr4096-r4055-r3-neo1973.bin'. gsmd is running OK, can receive/dial out calls. but no ringtone for incoming calls.<br><br />
20 Feb 2008 run DM2 (without wifi), Bluetooth scan not working, vibrator very weak<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #32 GTA02 A5 ===<br />
current holder: Miles<br><br />
20 Feb 2008 run DM2 (without wifi), Bluetooth scan not working<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #31 GTA02 A5 ===<br />
current holder: Andy<br><br />
20 Feb 2008 run DM2 (without wifi), Bluetoosh Scan only found 1 out of 3 devices<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #30 GTA02 A5 ===<br />
current holder: Mickey<br/><br />
<del>24 Feb 2008 '''issue found''': Headphone Jack GPIO is floating, receiving 500 IRQ's per second, making the system crawl like it has only 50MHz (or less...)<br/></del><br />
<del>24 Feb 2008 '''issue found''': Once sound is initialized, it emits two loud cracks per second<br/></del><br />
24 Feb 2008 '''issue found''': Vibrator is very weak<br/><br />
23 Feb 2008 flash NOR-enabled U-Boot, flash kernel+rootfs<br/><br />
20 Feb 2008 run DM2 (without wifi), no issues found<br/><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br/><br />
<br />
=== #29 Highcell battery 3.7V 1200mAh with Coulomb counter ===<br />
current holder: Andy<br />
<br />
=== #28 Highcell battery 3.7V 1200mAh with Coulomb counter ===<br />
current holder: Tony Tu<br />
<br />
=== #27 GTA02 A5 ===<br />
current holder: Willie<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
18 Feb 2008 Willie: LCD seems be broken. Screen shows three lines.<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #26 GTA02 A5 ===<br />
current holder: Allen Lin<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #25 GTA02 A5 ===<br />
current holder: Raster<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #24 GTA02 A5 ===<br />
current holder: John<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #23 GTA02 A5 ===<br />
current holder: JJ, battery vendor<br><br />
12 Feb 2008 Willie: Install kernel image from lastest svn check out<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #22 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
15 Feb 2008 Tony: Back to hardware team<br><br />
13 Feb 2008 Erin: gsm modem is bad <br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #21 GTA02 A5 ===<br />
current holder: Matt<br><br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad, GPS broken<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #20 GTA02 A5 ===<br />
current holder: Martin<br><br />
05 Mar 2008 GPS antenna switch 2nd source test<br><br />
21 Feb 2008 Miles: factory partition broken<br> <br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad<br><br />
13 Feb 2008 Miles take from Tony for PBE comparsion test<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #19 GTA02 A5 ===<br />
current holder: Brenda<br><br />
27 Feb Add PMU capacitor<br><br />
21 Feb 2008 Tony: Add WiFi FW 2.0.0.89<br><br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #18 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
15 Feb 2008 Willie: Send to hardware side and fix it. <br />
12 Feb 2008 Willie: It will generate big noise, maybe it's a hardware issue. I will check this <br><br />
12 Feb 2008 Erin: after booting to UI, the screen freezes, no any response. Willie is checking it now <br><br />
09 Feb 2008 Erin: load uboot, kernel, rootfs by Sean Chiang, it can auto-camp to the network, can use dialer<br> <br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #17 GTA02 A5 ===<br />
current holder: Vitaly (Atheros)<br><br />
01 Feb 2008 Delivered to Vitaly, Atheros<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #16 GTA02 A5 ===<br />
current holder: Samuel<br><br />
31 Jan 2008 Sent to Samuel<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #15 GTA02 A5 ===<br />
current holder: Tony<br><br />
12 Mar 2008 Wi-fi module still old one, and the DFU fail, USB connection un-steady<br />
31 Jan 2008 Running from battery shuts down 5 seconds after reboot. Running from power source (plugged into battery connectors) is stable<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #14 GTA02 A5 ===<br />
current holder: Willie<br><br />
27 Feb 2008 Willie: Get second phone<br><br />
21 Feb 2008 Tony: switched wifi to FW 2.0.0.89<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #13 GTA02 A5 ===<br />
current holder: Tony<br><br />
29 Jan 2008 Miles: Bluetooth scan doesn't work, Power Key broken<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #12 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
21 Jan 2008 Allen: Added Bluetooth module, reworked for power measurements, broken<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #11 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
21 Jan 2008 Allen: Added Bluetooth module, reworked for power measurements, broken<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #10 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
Die. Because I connect the power supply and usb. Then I shutdown the power supply, and power on the power supply. Quickly, the phone is short.<br />
<br />
=== #9 GTA02 A5 ===<br />
current holder: Matt<br><br />
5 Feb 2008 There are some hardware components broken. The behavior of i2c accessing is strange. And its suspend current is quite high (14~15mA).<br><br />
29 Jan 2008 Matt: Found out jack insert interrupt line is floating<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #8 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
21 Jan 2008 Allen: Added Bluetooth module, reworked for power measurements, broken<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #7 GTA02 A5 ===<br />
current holder: Smedia<br><br />
03 Mar 2008 Transfer to SMedia for flicker test<br />
27 Feb 2008 Add PMU capacitor<br><br />
21 Feb 2008 Tony: added receiver, switched to wifi FW 2.0.0.89<br><br />
05 Feb 2008 Miles: removed receiver<br><br />
29 Jan 2008 Miles: receiver test failed (receiver broken)<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #6 Highcell battery 3.7V 1200mAh with Coulomb counter ===<br />
current holder: Tony<br><br />
29 Jan 2008 Willie: verified<br />
<br />
=== #5 Highcell battery 3.7V 1200mAh with Coulomb counter ===<br />
current holder: Andy<br><br />
29 Jan 2008 sent to Andy<br><br />
29 Jan 2008 Willie: verified<br />
<br />
=== #4 Highcell battery 3.7V 1200mAh with Coulomb counter (Tony) ===<br />
current holder: Tony<br><br />
04 Mar 2008 Returned to Tony who gave me two "end user" batteries instead.<br><br />
08 Feb 2008 Got it. Passes power-on test.<br><br />
30 Jan 2008 sent to Werner<br><br />
29 Jan 2008 Willie: verified<br />
<br />
=== #3 GTA02 A5 ===<br />
current holder: Tony<br><br />
05 Feb 2008 Found solution: added capacitor<br><br />
02 Feb 2008 I see similar behaviour to #15 today on battery + USB. Appears to be related to, eg, starting LCM backlight making power problems resulting in immediate shutdown. Current limit issue somehow?<br><br />
01 Feb 2008 Behaving well.<br><br />
29 Jan 2008 sent to Andy<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #2 GTA02 A5 ===<br />
current holder: Harald<br><br />
29 Jan 2008 sent to Harald<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #1 GTA02 A5 (Werner) ===<br />
current holder: Werner<br><br />
05 Mar 2008 Vibrator seems to be broken or unnoticeably weak<br><br />
04 Mar 2008 SD/MMC seems broken under Linux (same usage works fine on #51; u-boot can read from it)<br><br />
11 Feb 2008 Verified NOR WP (with reworked debug v3)<br><br />
09 Feb 2008 Rework: bypass VB_SYS with 10uF 0603 6V3 cer X5R<br><br />
08 Feb 2008 Got it. Passes power-on test.<br><br />
30 Jan 2008 sent to Werner<br><br />
30 Jan 2008 Miles: verified hardware, same exceptions as below<br><br />
30 Jan 2008 Allen Chang: reworked to add NOR protection (R2505 closed, R2506 opened)<br><br />
29 Jan 2008 Miles: verified hardware, except for<br />
* microSD<br />
* suspend/resume<br />
* Bluetooth audio<br />
* Coulomb counter & motion sensor only low-level verification (no drivers)<br />
* USB host only low-level verification (no device)<br />
* charging (only 500mA verified), running on USB only, switching between charging modes<br />
* full memory verification<br />
* wakeup interrupts (WiFi, USB, GSM, motion sensors, 2 buttons, RTC, headphone jack)<br />
28 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
28 Jan 2008 Tony: Rework wifi FW to 2.0.0.40<br><br />
28 Jan 2008 Batch of 10 from Suzhou, PCBA with all modules, wifi FW 1.3, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
[[Category:GTA02 Hardware]]</div>Erinhttp://wiki.openmoko.org/wiki/PrototypesPrototypes2008-03-17T06:19:38Z<p>Erin: /* #60 GTA02 A5 */</p>
<hr />
<div>Prototypes are pieces of hardware such as boards, fully assembled devices, batteries, accessories that OpenMoko uses during the development of new hardware.<br />
<br />
This page tracks such prototypes, in which condition their life started, and what happened to them during their lifetime.<br />
<br />
Prototypes cannot be purchased. They will be loaned out on a case by case basis, and collected back for post mortem analysis.<br />
<br />
If you believe you need a prototype of some upcoming hardware, please mailto:openmoko-kernel@lists.openmoko.org.<br />
<br />
=== #65 GTA02 A5 ===<br />
current holder: Michael Shiloh<br><br />
06 Mar 2008 Ship to Michael Shiloh with coulomb battery<br><br />
05 Mar 2008 Finish CMU-200 test<br><br />
04 Mar 2008 850 Band re-work and add IR resistor for power saving<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #64 GTA02 A5 ===<br />
current holder: Martin/Hardware <br><br />
11 Mar 2008 USB DFU fail<br><br />
05 Mar 2008 Finish CMU-200 test<br><br />
04 Mar 2008 850 Band re-work and add IR resistor for power saving<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #63 GTA02 A5 ===<br />
current holder: Felipe Balbi<br><br />
11 Mar 2008 Sean doing 1800 band stability test<br><br />
05 Mar 2008 Finish CMU-200 test, but once unstable boot into kernel<br><br />
04 Mar 2008 850 Band re-work and add IR resistor for power saving<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #62 GTA02 A5 ===<br />
current holder: Raster<br><br />
07 Mar 2008 Transfer to Raster for another developer about graphics work<br><br />
03 Mar 2008 Tony use for DM/u-boot verification<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #61 GTA02 A5 ===<br />
current holder: Matt<br><br />
29 Feb 2008 Matt for GSM test usage<br><br />
29 Feb 2008 Allen GSM IR resistor rework<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #60 GTA02 A5 ===<br />
current holder: Erin<br><br />
17 Mar 2008 Check device status, and then will send it to M. Dietrich <br><br />
10 Mar 2008 GPS antenna is broken <br><br />
29 Feb 2008 Matt for GSM test usage<br><br />
29 Feb 2008 Allen GSM IR resistor rework<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #59 GTA02 A5 ===<br />
current holder: Martin<br><br />
17 Mar 2008 Hardware battery charging test<br><br />
12 Mar 2008 All sound output fail<br><br />
29 Feb 2008 Allen GSM IR resistor rework<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #58 GTA02 A5 ===<br />
current holder: TRIsoft<br><br />
07 Mar 2008 TRIsoft for testing<br><br />
03 Mar 2008 Harry bring to Cebit Show<br><br />
28 Feb 2008 Tony for DM test usage<br><br />
28 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br><br />
<br />
=== #57 Highcell battery 3.6V 1200mAh with Coulomb counter ===<br />
current holder: Allen Chang<br><br />
28 Feb 2008 With correct terminal voltage 3.6 vot 0% setting on bq27000<br />
<br />
=== #56 Highcell battery 3.6V 1200mAh with Coulomb counter ===<br />
current holder: Tony<br><br />
28 Feb 2008 With correct terminal voltage 3.6 vot 0% setting on bq27000<br />
<br />
=== #55 Highcell battery 3.6V 1200mAh with Coulomb counter ===<br />
current holder: Andy<br><br />
28 Feb 2008 With correct terminal voltage 3.6 vot 0% setting on bq27000<br />
<br />
=== #54 Highcell battery 3.6V 1200mAh with Coulomb counter ===<br />
current holder: Miles<br><br />
28 Feb 2008 With correct terminal voltage 3.6 vot 0% setting on bq27000<br />
<br />
=== #53 Highcell battery 3.6V 1200mAh with Coulomb counter ===<br />
current holder: Matt<br><br />
28 Feb 2008 With correct terminal voltage 3.6 vot 0% setting on bq27000<br />
<br />
=== #52 GTA02 A5 ===<br />
current holder: Wolfgang<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module <br />
<br />
=== #51 GTA02 A5 ===<br />
current holder: Martin<br><br />
17 Mar 2008 Hardware battery charging battery test<br><br />
12 Mar 2008 DFU always fail, USB connection broken all the time<br><br />
05 Mar 2008 Finish u-boot test, and return to tony <br><br />
29 Feb 2008 hardware side fixed 911 key and receiver issue.<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio, 911 key no switch, receiver broken<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #50 GTA02 A5 ===<br />
current holder: Sean<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth working (!)<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #49 GTA02 A5 ===<br />
current holder: OLV<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #48 GTA02 A5 ===<br />
current holder: Hoger<br><br />
05 Mar 2008 Transfer to Hoger<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth radio very weak<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #47 GTA02 A5 ===<br />
current holder: Michael Dietrich<br><br />
27 Feb 2008 Transfered to Will, sent to Michael<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth radio very weak<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #46 GTA02 A5 ===<br />
current holder: Thomas<br><br />
06 Mar 2008 Mail to o-hand Thomas as GTA02v4 replacement, with coulomb battery<br><br />
27 Feb 2008 Add PMU capacitor<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio, 911 key no switch<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #45 GTA02 A5 ===<br />
current holder: Jeremy<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #44 unlucky number ===<br />
<br />
=== #43 GTA02 A5 ===<br />
current holder: Miles<br><br />
21 Feb 2008 to Miles for DM2 partition verification<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #42 GTA02 A5 ===<br />
current holder: Julian<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio, weak vibrator<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #41 GTA02 A5 ===<br />
current holder: Lorn Potter (Trolltech)<br><br />
22 Feb 2008 sent to Lorn Potter, Trolltech<br><br />
22 Feb 2008 Tony: ran DM2 (without wifi), Bluetooth no radio<br><br />
22 Feb 2008 Tony: replaced receiver<br><br />
21 Feb 2008 Earphone broken in the package<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio, receiver broken<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #40 GTA02 A5 ===<br />
current holder: Tick<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #39 GTA02 A5 ===<br />
current holder: Sean Chiang<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #38 GTA02 A5 ===<br />
current holder: Andy<br><br />
21 Feb 2008: run DM2 (without wifi), no issues, Bluetooth working (!)<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #37 GTA02 A5 ===<br />
current holder: Lorn Potter (Trolltech)<br><br />
22 Feb 2008 sent to Lorn Potter, Trolltech<br><br />
21 Feb 2008 run DM2 (without wifi), no issues, Bluetooth working (!)<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #36 GTA02 A5 ===<br />
current holder: Graeme (FOSDEM)<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio, LCM cracked<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #35 GTA02 A5 ===<br />
current holder: Dodji (FOSDEM)<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #34 GTA02 A5 ===<br />
current holder: Martin<br><br />
05 Mar 2008 Return to hardware side for GPS antenna switch second source test<br><br />
20 Feb 2008 run DM2 (without wifi), receiver broken, 911 key broken, Bluetooth scan not working, Tony thinks device may have been drop-tested!<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #33 GTA02 A5 ===<br />
current holder: Erin<br><br />
22 Feb 2008 Erin: load daily build rootfs '0220-fic-gta02.rootfs.jffs2' and kernel 'uImage-2.6.24+svnr4096-r4055-r3-neo1973.bin'. gsmd is running OK, can receive/dial out calls. but no ringtone for incoming calls.<br><br />
20 Feb 2008 run DM2 (without wifi), Bluetooth scan not working, vibrator very weak<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #32 GTA02 A5 ===<br />
current holder: Miles<br><br />
20 Feb 2008 run DM2 (without wifi), Bluetooth scan not working<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #31 GTA02 A5 ===<br />
current holder: Andy<br><br />
20 Feb 2008 run DM2 (without wifi), Bluetoosh Scan only found 1 out of 3 devices<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #30 GTA02 A5 ===<br />
current holder: Mickey<br/><br />
<del>24 Feb 2008 '''issue found''': Headphone Jack GPIO is floating, receiving 500 IRQ's per second, making the system crawl like it has only 50MHz (or less...)<br/></del><br />
<del>24 Feb 2008 '''issue found''': Once sound is initialized, it emits two loud cracks per second<br/></del><br />
24 Feb 2008 '''issue found''': Vibrator is very weak<br/><br />
23 Feb 2008 flash NOR-enabled U-Boot, flash kernel+rootfs<br/><br />
20 Feb 2008 run DM2 (without wifi), no issues found<br/><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br/><br />
<br />
=== #29 Highcell battery 3.7V 1200mAh with Coulomb counter ===<br />
current holder: Andy<br />
<br />
=== #28 Highcell battery 3.7V 1200mAh with Coulomb counter ===<br />
current holder: Tony Tu<br />
<br />
=== #27 GTA02 A5 ===<br />
current holder: Willie<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
18 Feb 2008 Willie: LCD seems be broken. Screen shows three lines.<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #26 GTA02 A5 ===<br />
current holder: Allen Lin<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #25 GTA02 A5 ===<br />
current holder: Raster<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #24 GTA02 A5 ===<br />
current holder: John<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #23 GTA02 A5 ===<br />
current holder: JJ, battery vendor<br><br />
12 Feb 2008 Willie: Install kernel image from lastest svn check out<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #22 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
15 Feb 2008 Tony: Back to hardware team<br><br />
13 Feb 2008 Erin: gsm modem is bad <br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #21 GTA02 A5 ===<br />
current holder: Matt<br><br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad, GPS broken<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #20 GTA02 A5 ===<br />
current holder: Martin<br><br />
05 Mar 2008 GPS antenna switch 2nd source test<br><br />
21 Feb 2008 Miles: factory partition broken<br> <br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad<br><br />
13 Feb 2008 Miles take from Tony for PBE comparsion test<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #19 GTA02 A5 ===<br />
current holder: Brenda<br><br />
27 Feb Add PMU capacitor<br><br />
21 Feb 2008 Tony: Add WiFi FW 2.0.0.89<br><br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #18 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
15 Feb 2008 Willie: Send to hardware side and fix it. <br />
12 Feb 2008 Willie: It will generate big noise, maybe it's a hardware issue. I will check this <br><br />
12 Feb 2008 Erin: after booting to UI, the screen freezes, no any response. Willie is checking it now <br><br />
09 Feb 2008 Erin: load uboot, kernel, rootfs by Sean Chiang, it can auto-camp to the network, can use dialer<br> <br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #17 GTA02 A5 ===<br />
current holder: Vitaly (Atheros)<br><br />
01 Feb 2008 Delivered to Vitaly, Atheros<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #16 GTA02 A5 ===<br />
current holder: Samuel<br><br />
31 Jan 2008 Sent to Samuel<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #15 GTA02 A5 ===<br />
current holder: Tony<br><br />
12 Mar 2008 Wi-fi module still old one, and the DFU fail, USB connection un-steady<br />
31 Jan 2008 Running from battery shuts down 5 seconds after reboot. Running from power source (plugged into battery connectors) is stable<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #14 GTA02 A5 ===<br />
current holder: Willie<br><br />
27 Feb 2008 Willie: Get second phone<br><br />
21 Feb 2008 Tony: switched wifi to FW 2.0.0.89<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #13 GTA02 A5 ===<br />
current holder: Tony<br><br />
29 Jan 2008 Miles: Bluetooth scan doesn't work, Power Key broken<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #12 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
21 Jan 2008 Allen: Added Bluetooth module, reworked for power measurements, broken<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #11 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
21 Jan 2008 Allen: Added Bluetooth module, reworked for power measurements, broken<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #10 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
Die. Because I connect the power supply and usb. Then I shutdown the power supply, and power on the power supply. Quickly, the phone is short.<br />
<br />
=== #9 GTA02 A5 ===<br />
current holder: Matt<br><br />
5 Feb 2008 There are some hardware components broken. The behavior of i2c accessing is strange. And its suspend current is quite high (14~15mA).<br><br />
29 Jan 2008 Matt: Found out jack insert interrupt line is floating<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #8 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
21 Jan 2008 Allen: Added Bluetooth module, reworked for power measurements, broken<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #7 GTA02 A5 ===<br />
current holder: Smedia<br><br />
03 Mar 2008 Transfer to SMedia for flicker test<br />
27 Feb 2008 Add PMU capacitor<br><br />
21 Feb 2008 Tony: added receiver, switched to wifi FW 2.0.0.89<br><br />
05 Feb 2008 Miles: removed receiver<br><br />
29 Jan 2008 Miles: receiver test failed (receiver broken)<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #6 Highcell battery 3.7V 1200mAh with Coulomb counter ===<br />
current holder: Tony<br><br />
29 Jan 2008 Willie: verified<br />
<br />
=== #5 Highcell battery 3.7V 1200mAh with Coulomb counter ===<br />
current holder: Andy<br><br />
29 Jan 2008 sent to Andy<br><br />
29 Jan 2008 Willie: verified<br />
<br />
=== #4 Highcell battery 3.7V 1200mAh with Coulomb counter (Tony) ===<br />
current holder: Tony<br><br />
04 Mar 2008 Returned to Tony who gave me two "end user" batteries instead.<br><br />
08 Feb 2008 Got it. Passes power-on test.<br><br />
30 Jan 2008 sent to Werner<br><br />
29 Jan 2008 Willie: verified<br />
<br />
=== #3 GTA02 A5 ===<br />
current holder: Tony<br><br />
05 Feb 2008 Found solution: added capacitor<br><br />
02 Feb 2008 I see similar behaviour to #15 today on battery + USB. Appears to be related to, eg, starting LCM backlight making power problems resulting in immediate shutdown. Current limit issue somehow?<br><br />
01 Feb 2008 Behaving well.<br><br />
29 Jan 2008 sent to Andy<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #2 GTA02 A5 ===<br />
current holder: Harald<br><br />
29 Jan 2008 sent to Harald<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #1 GTA02 A5 (Werner) ===<br />
current holder: Werner<br><br />
05 Mar 2008 Vibrator seems to be broken or unnoticeably weak<br><br />
04 Mar 2008 SD/MMC seems broken under Linux (same usage works fine on #51; u-boot can read from it)<br><br />
11 Feb 2008 Verified NOR WP (with reworked debug v3)<br><br />
09 Feb 2008 Rework: bypass VB_SYS with 10uF 0603 6V3 cer X5R<br><br />
08 Feb 2008 Got it. Passes power-on test.<br><br />
30 Jan 2008 sent to Werner<br><br />
30 Jan 2008 Miles: verified hardware, same exceptions as below<br><br />
30 Jan 2008 Allen Chang: reworked to add NOR protection (R2505 closed, R2506 opened)<br><br />
29 Jan 2008 Miles: verified hardware, except for<br />
* microSD<br />
* suspend/resume<br />
* Bluetooth audio<br />
* Coulomb counter & motion sensor only low-level verification (no drivers)<br />
* USB host only low-level verification (no device)<br />
* charging (only 500mA verified), running on USB only, switching between charging modes<br />
* full memory verification<br />
* wakeup interrupts (WiFi, USB, GSM, motion sensors, 2 buttons, RTC, headphone jack)<br />
28 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
28 Jan 2008 Tony: Rework wifi FW to 2.0.0.40<br><br />
28 Jan 2008 Batch of 10 from Suzhou, PCBA with all modules, wifi FW 1.3, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
[[Category:GTA02 Hardware]]</div>Erinhttp://wiki.openmoko.org/wiki/PrototypesPrototypes2008-02-22T06:03:40Z<p>Erin: /* #33 GTA02 A5 */</p>
<hr />
<div>Prototypes are pieces of hardware such as boards, fully assembled devices, batteries, accessories that OpenMoko uses during the development of new hardware.<br />
<br />
This page tracks such prototypes, in which condition their life started, and what happened to them during their lifetime.<br />
<br />
Prototypes cannot be purchased. They will be loaned out on a case by case basis, and collected back for post mortem analysis.<br />
<br />
If you believe you need a prototype of some upcoming hardware, please mailto:openmoko-kernel@lists.openmoko.org.<br />
<br />
=== #52 GTA02 A5 ===<br />
current holder: Tony<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #51 GTA02 A5 ===<br />
current holder: Tony<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio, 911 key no switch, receiver broken<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #50 GTA02 A5 ===<br />
current holder: Tony<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth working (!)<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #49 GTA02 A5 ===<br />
current holder: Tony<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #48 GTA02 A5 ===<br />
current holder: Tony<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth radio very weak<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #47 GTA02 A5 ===<br />
current holder: Tony<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth radio very weak<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #46 GTA02 A5 ===<br />
current holder: Tony<br><br />
22 Feb 2008 run DM2 (without wifi), Bluetooth no radio, 911 key no switch<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #45 GTA02 A5 ===<br />
current holder: Jeremy<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #44 unlucky number ===<br />
<br />
=== #43 GTA02 A5 ===<br />
current holder: Miles<br><br />
21 Feb 2008 to Miles for DM2 partition verification<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #42 GTA02 A5 ===<br />
current holder: Julian<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio, weak vibrator<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #41 GTA02 A5 ===<br />
current holder: Tony<br><br />
22 Feb 2008 Tony: ran DM2 (without wifi), Bluetooth no radio<br><br />
22 Feb 2008 Tony: replaced receiver<br><br />
21 Feb 2008 Earphone broken in the package<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio, receiver broken<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #40 GTA02 A5 ===<br />
current holder: Tick<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #39 GTA02 A5 ===<br />
current holder: Sean Chiang<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #38 GTA02 A5 ===<br />
current holder: Tony<br><br />
21 Feb 2008: run DM2 (without wifi), no issues, Bluetooth working (!)<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #37 GTA02 A5 ===<br />
current holder: Tony<br><br />
21 Feb 2008: run DM2 (without wifi), no issues, Bluetooth working (!)<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #36 GTA02 A5 ===<br />
current holder: John (FOSDEM)<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio, LCM cracked<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #35 GTA02 A5 ===<br />
current holder: John (FOSDEM)<br><br />
21 Feb 2008 run DM2 (without wifi), Bluetooth no radio<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #34 GTA02 A5 ===<br />
current holder: Tony<br><br />
20 Feb 2008 run DM2 (without wifi), receiver broken, 911 key broken, Bluetooth scan not working, Tony thinks device may have been drop-tested!<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #33 GTA02 A5 ===<br />
current holder: Erin<br><br />
22 Feb 2008 Erin: load daily build rootfs '0220-fic-gta02.rootfs.jffs2' and kernel 'uImage-2.6.24+svnr4096-r4055-r3-neo1973.bin'. gsmd is running OK, can receive/dial out calls. but no ringtone for incoming calls. <br />
20 Feb 2008 run DM2 (without wifi), Bluetooth scan not working, vibrator very weak<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #32 GTA02 A5 ===<br />
current holder: Miles<br><br />
20 Feb 2008 run DM2 (without wifi), Bluetooth scan not working<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #31 GTA02 A5 ===<br />
current holder: Andy<br><br />
20 Feb 2008 run DM2 (without wifi), Bluetoosh Scan only found 1 out of 3 devices<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #30 GTA02 A5 ===<br />
current holder: John (FOSDEM)<br><br />
20 Feb 2008 run DM2 (without wifi), no issues found<br><br />
18 Feb 2008 Hardware add capacitor and FW2.0.0.89 module<br />
<br />
=== #29 Highcell battery 3.7V 1250mAh with Coulomb counter ===<br />
current holder: Andy<br />
<br />
=== #28 Highcell battery 3.7V 1250mAh with Coulomb counter ===<br />
current holder: Raster<br />
<br />
=== #27 GTA02 A5 ===<br />
current holder: Willie<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
18 Feb 2008 Willie: LCD seems be broken. Screen shows three lines.<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #26 GTA02 A5 ===<br />
current holder: Allen Lin<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #25 GTA02 A5 ===<br />
current holder: Raster<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #24 GTA02 A5 ===<br />
current holder: John<br><br />
18 Feb 2008 Tony: Add Wi-Fi Module FW2.0.0.89<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #23 GTA02 A5 ===<br />
current holder: JJ, battery vendor<br><br />
12 Feb 2008 Willie: Install kernel image from lastest svn check out<br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #22 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
15 Feb 2008 Tony: Back to hardware team<br><br />
13 Feb 2008 Erin: gsm modem is bad <br><br />
12 Feb 2008 Tony: removed wifi module<br><br />
12 Feb 2008 DKay: capacitor added<br><br />
05 Feb 2008 batch of 30, PCBA fully assembled, wifi FW 1.3<br />
<br />
=== #21 GTA02 A5 ===<br />
current holder: Matt<br><br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad, GPS broken<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #20 GTA02 A5 ===<br />
current holder: Tony<br><br />
21 Feb 2008 Miles: factory partition broken<br> <br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad<br><br />
13 Feb 2008 Miles take from Tony for PBE comparsion test<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #19 GTA02 A5 ===<br />
current holder: Tony<br><br />
21 Feb 2008 Tony: Add WiFi FW 2.0.0.89<br><br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #18 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
15 Feb 2008 Willie: Send to hardware side and fix it. <br />
12 Feb 2008 Willie: It will generate big noise, maybe it's a hardware issue. I will check this <br><br />
12 Feb 2008 Erin: after booting to UI, the screen freezes, no any response. Willie is checking it now <br><br />
09 Feb 2008 Erin: load uboot, kernel, rootfs by Sean Chiang, it can auto-camp to the network, can use dialer<br> <br />
01 Feb 2008 Miles: verified hardware, same exceptions as #1, Bluetooth sensitivity very bad<br><br />
31 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
31 Jan 2008 Batch of 4 from Suzhou, PCBA with all modules, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
=== #17 GTA02 A5 ===<br />
current holder: Vitaly (Atheros)<br><br />
01 Feb 2008 Delivered to Vitaly, Atheros<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #16 GTA02 A5 ===<br />
current holder: Samuel<br><br />
31 Jan 2008 Sent to Samuel<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #15 GTA02 A5 ===<br />
current holder: Tony<br><br />
31 Jan 2008 Running from battery shuts down 5 seconds after reboot. Running from power source (plugged into battery connectors) is stable<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #14 GTA02 A5 ===<br />
current holder: Tony<br><br />
21 Feb 2008 Tony: switched wifi to FW 2.0.0.89<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #13 GTA02 A5 ===<br />
current holder: Tony<br><br />
29 Jan 2008 Miles: Bluetooth scan doesn't work, Power Key broken<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #12 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
21 Jan 2008 Allen: Added Bluetooth module, reworked for power measurements, broken<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #11 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
21 Jan 2008 Allen: Added Bluetooth module, reworked for power measurements, broken<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #10 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
Die. Because I connect the power supply and usb. Then I shutdown the power supply, and power on the power supply. Quickly, the phone is short.<br />
<br />
=== #9 GTA02 A5 ===<br />
current holder: Matt<br><br />
5 Feb 2008 There are some hardware components broken. The behavior of i2c accessing is strange. And its suspend current is quite high (14~15mA).<br><br />
29 Jan 2008 Matt: Found out jack insert interrupt line is floating<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #8 GTA02 A5 ===<br />
current holder: Tim Lee<br><br />
21 Jan 2008 Allen: Added Bluetooth module, reworked for power measurements, broken<br><br />
18 Jan 2008 Arrived from Suzhou (batch of 4) as PCBA without modules<br />
<br />
=== #7 GTA02 A5 ===<br />
current holder: Tony<br><br />
21 Feb 2008 Tony: added receiver, switched to wifi FW 2.0.0.89<br><br />
05 Feb 2008 Miles: removed receiver<br><br />
29 Jan 2008 Miles: receiver test failed (receiver broken)<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #6 Highcell battery 3.7V 1250mAh with Coulomb counter ===<br />
current holder: Tony<br><br />
29 Jan 2008 Willie: verified<br />
<br />
=== #5 Highcell battery 3.7V 1250mAh with Coulomb counter ===<br />
current holder: Andy<br><br />
29 Jan 2008 sent to Andy<br><br />
29 Jan 2008 Willie: verified<br />
<br />
=== #4 Highcell battery 3.7V 1200mAh with Coulomb counter (Werner) ===<br />
current holder: Werner<br><br />
08 Feb 2008 Got it. Passes power-on test.<br><br />
30 Jan 2008 sent to Werner<br><br />
29 Jan 2008 Willie: verified<br />
<br />
=== #3 GTA02 A5 ===<br />
current holder: Andy<br><br />
05 Feb 2008 Found solution: added capacitor<br><br />
02 Feb 2008 I see similar behaviour to #15 today on battery + USB. Appears to be related to, eg, starting LCM backlight making power problems resulting in immediate shutdown. Current limit issue somehow?<br><br />
01 Feb 2008 Behaving well.<br><br />
29 Jan 2008 sent to Andy<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #2 GTA02 A5 ===<br />
current holder: Harald<br><br />
29 Jan 2008 sent to Harald<br><br />
29 Jan 2008 Same as #1 until 29 Jan 2008<br />
<br />
=== #1 GTA02 A5 (Werner) ===<br />
current holder: Werner<br><br />
11 Feb 2008 Verified NOR WP (with reworked debug v3)<br><br />
09 Feb 2008 Rework: bypass VB_SYS with 10uF 0603 6V3 cer X5R<br><br />
08 Feb 2008 Got it. Passes power-on test.<br><br />
30 Jan 2008 sent to Werner<br><br />
30 Jan 2008 Miles: verified hardware, same exceptions as below<br><br />
30 Jan 2008 Allen Chang: reworked to add NOR protection (R2505 closed, R2506 opened)<br><br />
29 Jan 2008 Miles: verified hardware, except for<br />
* microSD<br />
* suspend/resume<br />
* Bluetooth audio<br />
* Coulomb counter & motion sensor only low-level verification (no drivers)<br />
* USB host only low-level verification (no device)<br />
* charging (only 500mA verified), running on USB only, switching between charging modes<br />
* full memory verification<br />
* wakeup interrupts (WiFi, USB, GSM, motion sensors, 2 buttons, RTC, headphone jack)<br />
28 Jan 2008 Tony: Put inside GTA01 case, speaker, antennas<br><br />
28 Jan 2008 Tony: Rework wifi FW to 2.0.0.40<br><br />
28 Jan 2008 Batch of 10 from Suzhou, PCBA with all modules, wifi FW 1.3, NOR protection disabled, full DM1 (v009) and DM2 (v012)<br />
<br />
[[Category:Neo1973 Phase 2 related]]</div>Erinhttp://wiki.openmoko.org/wiki/GSM_unit_testGSM unit test2008-02-20T06:57:30Z<p>Erin: /* How to use this python script */</p>
<hr />
<div>GSM unit test is for testing the interactions between [http://wiki.openmoko.org/wiki/Gsmd#libgsmd-tool libgsmd-tool] and [http://wiki.openmoko.org/wiki/Gsmd gsmd]. Here is a [[Python]] script to execute commands via libgsmd-tool. We can write our own test cases to let GSM modem execute AT commands automatically. It allows us to verify [[GSM]] basic functions, such like making phone calls, sending SMS, or registering to the network.<br />
<br />
This python script is based on [http://wiki.openmoko.org/wiki/Pexpect Python Expect]. Pexpect is a pure Python module for spawning child applications; controlling them; and responding to expected patterns in their output. We use this module to spawn [libgsmd-tool] and then can send commands to GSM modem via gsmd.<br />
<br />
== How to use this python script ==<br />
<br />
* python script [[http://people.openmoko.org/erin_yueh/UnitTestv2.py 1]]<br />
* sample test case [[http://people.openmoko.org/erin_yueh/casev1 2]]<br />
* register the network test case [[http://cs.nyu.edu/~wcy203/RegistertoNetwork 3]]<br />
* dial out test case [[http://people.openmoko.org/erin_yueh//DialOut 4]]<br />
* send/receive SMS test case [[http://people.openmoko.org/erin_yueh/SendReceiveSMS 5]]<br />
<br />
usage: python UnivTestv1.py -t casename -c libgsmd-tool -m shell<br />
-t : testcase file<br />
-c : libgsmd-tool<br />
-m : atcmd or shell<br />
<br />
=== How to write a test case file ===<br />
<br />
==== text format ==== <br />
it should be written as below: <br />
<br />
C:r <br />
E:Register,error <br />
E:Netreg registered(home network),OK,error<br />
From above case, it sends 'r' command to libgsmd-tool and it tries to register the network.<br />
<br />
==== real output from libgsmd-tool ====<br />
below texts are copied from libgsmd-tool shell mode <br />
<br />
r<br />
# Register<br />
EVENT: Netreg searching for network <br />
EVENT: Signal Quality: 22<br />
EVENT: Netreg registered (home network) LocationAreaCode = 0x2C27 CellID = 0x498C<br />
<br />
==== how to write expect list to match the result ====<br />
From above real output from libgsmd-tool, it's very easy to detect the expect behavior. The first expect, it prints the command descriptions. The second expect, we can use some keywords like 'Netreg registered' for this case.<br />
<br />
* use ',' for the delimiter <br />
<br />
* always put the most matched one on the first element: There can be a lot of matched elements in an expect list. Put this list before using 'error'<br />
<br />
* append .EOF and .TIMEOUT elements to the expect list: When it reads the second expect line, it appends these two more elements to the list. <br />
<br />
* how to know it's failed or passed: there are 4 cases<br />
# correct: passed<br />
# error: failed<br />
# EOF: failed<br />
# timeout: failed<br />
<br />
* script log: It also stores the session log from 'libgsmd-tool', and the default file name is 'script.log'.</div>Erinhttp://wiki.openmoko.org/wiki/Today/2007.2Today/2007.22008-02-19T10:58:14Z<p>Erin: /* Adjust UI components at runtime */</p>
<hr />
<div>== Overview ==<br />
This article defines the second revision of the Today Application, an application designed for the OpenMoko platform.<br />
<br />
The Today application is the entry point for the user. It therefore resides on the 'desktop' of the phone, and is used for the following:<br />
1) Quickly finding out the status of phone & calender related items.<br />
2) Launch a new application.<br />
3) Manage running applications i.e. Switch to or close a running application.<br />
<br />
== Use Cases ==<br />
Here are some possible use cases:<br />
* I want to be able to view at a glance today's Calendar Events and To Do Items.<br />
* I want to launch an application.<br />
* I want to switch to a running application.<br />
<br />
== Core Functionality ==<br />
<br />
(Italics = Done, Bold = In progress)<br />
<br />
* '''View network provider'''<br />
* ''Overview of missed calls and unread messages''<br />
* ''Overview of future events, tasks and alarms''<br />
* '''Lock the phone to prevent accidental touch-screen press'''<br />
* ''Launch core applications''<br />
* ''Launch dialer to view missed calls''<br />
* ''Launch messages application to view unread messages''<br />
<br />
* ''View all applications, with descriptions''<br />
* ''Launch a selected application''<br />
* ''Filter all applications by category''<br />
* ''Filter all applications on name and description by custom search string''<br />
<br />
* ''View running applications''<br />
* ''Switch to running application''<br />
* ''Close running application''<br />
* ''Close all running applications''<br />
<br />
== Layout Components ==<br />
<br />
=== Application Area ===<br />
==== Today Page ====<br />
<br />
[[Image:today-main-arrows.png]]<br />
<br />
*'''1) Title''' -- This is a global panel applet which automatically sets the title to the currently on screen application. It also provides a quick way to switch between running applications.<br />
*'''2) Phone Group''' -- Has the network operator as the title, and shows the number of missed calls and unread SMS's.<br />
*'''3) Calender Group''' -- Shows the time and date as the title, and has a list of calender items, todo's and reminders.<br />
*'''4) Main Page''' -- Current page.<br />
*'''5) Launch Task Page''' -- Switches to the Launch Task page, where the user can browse and launch applications.<br />
*'''6) Running Tasks Page''' -- Switches to the Running Tasks page, where the user can switch to or close running applications.<br />
*'''7) Quick Launch''' -- A tool-bar housing the most used applications.<br />
<br />
==== Launch Task Page ====<br />
<br />
[[Image:today-new-arrows.png]]<br />
<br />
*'''1) Title''' <br />
*'''2) Application List''' -- A list of available applications.<br />
*'''3) Today Page''' -- Switches to the Today page.<br />
*'''4) Launch Task Page''' -- Current Page.<br />
*'''5) Running Tasks Page''' -- Switches to the Running Tasks page, where the user can switch to or close running applications.<br />
*'''6) Search/Filter Menu''' -- This is used to filter the applications, either by clicking the search icon and typing in a string, or by clicking on the filter menu and choosing an application group.<br />
<br />
==== Running Tasks Page ====<br />
<br />
[[Image:today-running-arrows.png]]<br />
<br />
*'''1) Title''' <br />
*'''2) Switch To''' -- Switches to the highlighted application.<br />
*'''3) Close''' -- Closes the highlighted application.<br />
*'''4) Close All''' -- Closes all the running applications.<br />
*'''5) Today Page''' -- Switches to the Today page.<br />
*'''6) Launch Task Page''' -- Switches to the Launch Task page.<br />
*'''7) Running Tasks Page''' -- Current Page.<br />
*'''8) List Of Running Applications'''<br />
<br />
== Adjust UI components at runtime ==<br />
<br />
*'''default''': this is from daily build default image<br />
[[Image:Todaypage_reduced_false.png|200px|]]<br />
# gconftool-2 --type bool --set /desktop/poky/interface/reduced false<br />
<br />
*'''reduced''': remove the upper application icons, no clock, and no date<br />
[[Image:Todaypage_reduced_true.png|200px|]]<br />
# gconftool-2 --type bool --set /desktop/poky/interface/reduced true<br />
<br />
*'''digital/analog clock''' : change the digital clock to analog clock<br />
[[Image:Todaypage_digitalclock_false.png|200px|]]<br />
# gconftool-2 --type bool --set /desktop/poky/interface/digital_clock false<br />
<br />
*'''remove clock entirely''' <br />
[[Image:Todaypage_noclock.png|200px|]]<br />
# gconftool-2 --type bool --set /desktop/poky/interface/small_clock true<br />
<br />
*'''change wallpaper image''' <br />
[[Image:Todaypage_changewallpaper.png|200px|]]<br />
# gconftool-2 --type string --set /desktop/poky/interface/wallpaper /usr/share/pixmaps/wallpaper.png'''<br />
<br />
* '''gconf problem'''<br />
(gconftool-2:1366): GConf-WARNING **: Client failed to connect to the D-BUS daemon:<br />
Failed to execute dbus-launch to autolaunch D-Bus session<br />
Error setting value: No D-BUS daemon running<br />
<br />
root@fic-gta02:/$ ps aux | grep today<br />
root 1320 3.7 11.5 33556 14100 ? S 23:00 0:09 openmoko-today<br />
root 1369 0.0 0.4 2860 592 pts/0 S+ 23:04 0:00 grep today<br />
<br />
root@fic-gta02:/$ cat /proc/1320/environ <br />
<br />
root@fic-gta02:/$ export DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-80gSL9Q6F4,<br />
guid=6efed88183a7f6b9210cf40047ba0dfe<br />
<br />
<br />
{{Languages|Today/2007.2}}<br />
[[Category:OpenMoko2007.2]]<br />
[[Category:Finger based]]<br />
[[Category:Implemented]]</div>Erinhttp://wiki.openmoko.org/wiki/Today/2007.2Today/2007.22008-02-19T10:47:22Z<p>Erin: </p>
<hr />
<div>== Overview ==<br />
This article defines the second revision of the Today Application, an application designed for the OpenMoko platform.<br />
<br />
The Today application is the entry point for the user. It therefore resides on the 'desktop' of the phone, and is used for the following:<br />
1) Quickly finding out the status of phone & calender related items.<br />
2) Launch a new application.<br />
3) Manage running applications i.e. Switch to or close a running application.<br />
<br />
== Use Cases ==<br />
Here are some possible use cases:<br />
* I want to be able to view at a glance today's Calendar Events and To Do Items.<br />
* I want to launch an application.<br />
* I want to switch to a running application.<br />
<br />
== Core Functionality ==<br />
<br />
(Italics = Done, Bold = In progress)<br />
<br />
* '''View network provider'''<br />
* ''Overview of missed calls and unread messages''<br />
* ''Overview of future events, tasks and alarms''<br />
* '''Lock the phone to prevent accidental touch-screen press'''<br />
* ''Launch core applications''<br />
* ''Launch dialer to view missed calls''<br />
* ''Launch messages application to view unread messages''<br />
<br />
* ''View all applications, with descriptions''<br />
* ''Launch a selected application''<br />
* ''Filter all applications by category''<br />
* ''Filter all applications on name and description by custom search string''<br />
<br />
* ''View running applications''<br />
* ''Switch to running application''<br />
* ''Close running application''<br />
* ''Close all running applications''<br />
<br />
== Layout Components ==<br />
<br />
=== Application Area ===<br />
==== Today Page ====<br />
<br />
[[Image:today-main-arrows.png]]<br />
<br />
*'''1) Title''' -- This is a global panel applet which automatically sets the title to the currently on screen application. It also provides a quick way to switch between running applications.<br />
*'''2) Phone Group''' -- Has the network operator as the title, and shows the number of missed calls and unread SMS's.<br />
*'''3) Calender Group''' -- Shows the time and date as the title, and has a list of calender items, todo's and reminders.<br />
*'''4) Main Page''' -- Current page.<br />
*'''5) Launch Task Page''' -- Switches to the Launch Task page, where the user can browse and launch applications.<br />
*'''6) Running Tasks Page''' -- Switches to the Running Tasks page, where the user can switch to or close running applications.<br />
*'''7) Quick Launch''' -- A tool-bar housing the most used applications.<br />
<br />
==== Launch Task Page ====<br />
<br />
[[Image:today-new-arrows.png]]<br />
<br />
*'''1) Title''' <br />
*'''2) Application List''' -- A list of available applications.<br />
*'''3) Today Page''' -- Switches to the Today page.<br />
*'''4) Launch Task Page''' -- Current Page.<br />
*'''5) Running Tasks Page''' -- Switches to the Running Tasks page, where the user can switch to or close running applications.<br />
*'''6) Search/Filter Menu''' -- This is used to filter the applications, either by clicking the search icon and typing in a string, or by clicking on the filter menu and choosing an application group.<br />
<br />
==== Running Tasks Page ====<br />
<br />
[[Image:today-running-arrows.png]]<br />
<br />
*'''1) Title''' <br />
*'''2) Switch To''' -- Switches to the highlighted application.<br />
*'''3) Close''' -- Closes the highlighted application.<br />
*'''4) Close All''' -- Closes all the running applications.<br />
*'''5) Today Page''' -- Switches to the Today page.<br />
*'''6) Launch Task Page''' -- Switches to the Launch Task page.<br />
*'''7) Running Tasks Page''' -- Current Page.<br />
*'''8) List Of Running Applications'''<br />
<br />
== Adjust UI components at runtime ==<br />
<br />
*'''default''': this is from daily build default image<br />
[[Image:Todaypage_reduced_false.png|200px|]]<br />
# gconftool-2 --type bool --set /desktop/poky/interface/reduced false<br />
<br />
*'''reduced''': remove the upper application icons, no clock, and no date<br />
[[Image:Todaypage_reduced_true.png|200px|]]<br />
# gconftool-2 --type bool --set /desktop/poky/interface/reduced true<br />
<br />
*'''digital/analog clock''' : change the digital clock to analog clock<br />
[[Image:Todaypage_digitalclock_false.png|200px|]]<br />
# gconftool-2 --type bool --set /desktop/poky/interface/digital_clock false<br />
<br />
*'''remove clock entirely''' <br />
[[Image:Todaypage_noclock.png|200px|]]<br />
# gconftool-2 --type bool --set /desktop/poky/interface/small_clock true<br />
<br />
*'''change wallpaper image''' <br />
[[Image:Todaypage_changewallpaper.png|200px|]]<br />
#gconftool-2 --type string --set /desktop/poky/interface/wallpaper /usr/share/pixmaps/wallpaper.png'''<br />
<br />
<br />
{{Languages|Today/2007.2}}<br />
[[Category:OpenMoko2007.2]]<br />
[[Category:Finger based]]<br />
[[Category:Implemented]]</div>Erinhttp://wiki.openmoko.org/wiki/Today/2007.2Today/2007.22008-02-19T10:46:08Z<p>Erin: /* Adjust UI components at runtime */</p>
<hr />
<div>== Overview ==<br />
This article defines the second revision of the Today Application, an application designed for the OpenMoko platform.<br />
<br />
The Today application is the entry point for the user. It therefore resides on the 'desktop' of the phone, and is used for the following:<br />
1) Quickly finding out the status of phone & calender related items.<br />
2) Launch a new application.<br />
3) Manage running applications i.e. Switch to or close a running application.<br />
<br />
== Use Cases ==<br />
Here are some possible use cases:<br />
* I want to be able to view at a glance today's Calendar Events and To Do Items.<br />
* I want to launch an application.<br />
* I want to switch to a running application.<br />
<br />
== Core Functionality ==<br />
<br />
(Italics = Done, Bold = In progress)<br />
<br />
* '''View network provider'''<br />
* ''Overview of missed calls and unread messages''<br />
* ''Overview of future events, tasks and alarms''<br />
* '''Lock the phone to prevent accidental touch-screen press'''<br />
* ''Launch core applications''<br />
* ''Launch dialer to view missed calls''<br />
* ''Launch messages application to view unread messages''<br />
<br />
* ''View all applications, with descriptions''<br />
* ''Launch a selected application''<br />
* ''Filter all applications by category''<br />
* ''Filter all applications on name and description by custom search string''<br />
<br />
* ''View running applications''<br />
* ''Switch to running application''<br />
* ''Close running application''<br />
* ''Close all running applications''<br />
<br />
== Layout Components ==<br />
<br />
=== Application Area ===<br />
==== Today Page ====<br />
<br />
[[Image:today-main-arrows.png]]<br />
<br />
*'''1) Title''' -- This is a global panel applet which automatically sets the title to the currently on screen application. It also provides a quick way to switch between running applications.<br />
*'''2) Phone Group''' -- Has the network operator as the title, and shows the number of missed calls and unread SMS's.<br />
*'''3) Calender Group''' -- Shows the time and date as the title, and has a list of calender items, todo's and reminders.<br />
*'''4) Main Page''' -- Current page.<br />
*'''5) Launch Task Page''' -- Switches to the Launch Task page, where the user can browse and launch applications.<br />
*'''6) Running Tasks Page''' -- Switches to the Running Tasks page, where the user can switch to or close running applications.<br />
*'''7) Quick Launch''' -- A tool-bar housing the most used applications.<br />
<br />
==== Launch Task Page ====<br />
<br />
[[Image:today-new-arrows.png]]<br />
<br />
*'''1) Title''' <br />
*'''2) Application List''' -- A list of available applications.<br />
*'''3) Today Page''' -- Switches to the Today page.<br />
*'''4) Launch Task Page''' -- Current Page.<br />
*'''5) Running Tasks Page''' -- Switches to the Running Tasks page, where the user can switch to or close running applications.<br />
*'''6) Search/Filter Menu''' -- This is used to filter the applications, either by clicking the search icon and typing in a string, or by clicking on the filter menu and choosing an application group.<br />
<br />
==== Running Tasks Page ====<br />
<br />
[[Image:today-running-arrows.png]]<br />
<br />
*'''1) Title''' <br />
*'''2) Switch To''' -- Switches to the highlighted application.<br />
*'''3) Close''' -- Closes the highlighted application.<br />
*'''4) Close All''' -- Closes all the running applications.<br />
*'''5) Today Page''' -- Switches to the Today page.<br />
*'''6) Launch Task Page''' -- Switches to the Launch Task page.<br />
*'''7) Running Tasks Page''' -- Current Page.<br />
*'''8) List Of Running Applications'''<br />
<br />
{{Languages|Today/2007.2}}<br />
[[Category:OpenMoko2007.2]]<br />
[[Category:Finger based]]<br />
[[Category:Implemented]]<br />
<br />
== Adjust UI components at runtime ==<br />
<br />
*'''default''': this is from daily build default image<br />
[[Image:Todaypage_reduced_false.png|200px|]]<br />
# gconftool-2 --type bool --set /desktop/poky/interface/reduced false<br />
<br />
*'''reduced''': remove the upper application icons, no clock, and no date<br />
[[Image:Todaypage_reduced_true.png|200px|]]<br />
# gconftool-2 --type bool --set /desktop/poky/interface/reduced true<br />
<br />
*'''digital/analog clock''' : change the digital clock to analog clock<br />
[[Image:Todaypage_digitalclock_false.png|200px|]]<br />
# gconftool-2 --type bool --set /desktop/poky/interface/digital_clock false<br />
<br />
*'''remove clock entirely''' <br />
[[Image:Todaypage_noclock.png|200px|]]<br />
# gconftool-2 --type bool --set /desktop/poky/interface/small_clock true<br />
<br />
*'''change wallpaper image''' <br />
[[Image:Todaypage_changewallpaper.png|200px|]]<br />
#gconftool-2 --type string --set /desktop/poky/interface/wallpaper /usr/share/pixmaps/wallpaper.png'''</div>Erinhttp://wiki.openmoko.org/wiki/File:Todaypage_changewallpaper.pngFile:Todaypage changewallpaper.png2008-02-19T10:13:53Z<p>Erin: today page with different wallpaper</p>
<hr />
<div>today page with different wallpaper</div>Erinhttp://wiki.openmoko.org/wiki/File:Todaypage_noclock.pngFile:Todaypage noclock.png2008-02-19T10:12:31Z<p>Erin: today page without clock</p>
<hr />
<div>today page without clock</div>Erinhttp://wiki.openmoko.org/wiki/File:Todaypage_digitalclock_false.pngFile:Todaypage digitalclock false.png2008-02-19T09:53:10Z<p>Erin: today page with analog clock</p>
<hr />
<div>today page with analog clock</div>Erin