Openmoko - User contributions [en]

User:Mariusno

2009-03-03T22:46:11Z

Mariusno: /* program */

===Device: ===
GTA02v6

===Running: ===
OM2008.12

===Ascessories: ===
512MB uSD-card
Headphones
External-antenna

== Programming: ==

===program===
GPS position update tool, with picture upload and a google maps api intergration.

===language===
python, java, php, javascript

=Update soon=
Code will be uploaded when program is working

User:Mariusno

2009-03-03T22:45:40Z

Mariusno: /* Update soon */

===Device: ===
GTA02v6

===Running: ===
OM2008.12

===Ascessories: ===
512MB uSD-card
Headphones
External-antenna

== Programming: ==

===program===
GPS position update tool, width picture upload and a google maps api
===language===
python, java, php, javascript

=Update soon=
Code will be uploaded when program is working

User:Mariusno

2009-03-03T12:37:23Z

Mariusno:

===Device: ===
GTA02v6

===Running: ===
OM2008.12

===Ascessories: ===
512MB uSD-card
Headphones
External-antenna

== Programming: ==

===program===
GPS position update tool, width picture upload and a google maps api
===language===
python, java, php, javascript

=Update soon=

User:Mariusno

2009-03-03T12:32:00Z

Mariusno:

Device: GTA02v6

Running: OM2008.12

Programming: GPS position update tool, width picture upload and a google maps api

User:Mariusno

2009-03-03T12:31:20Z

Mariusno: New page: Running: OM2008.12 Programming: GPS position update tool, width picture upload and a google maps api

Running: OM2008.12

Programming: GPS position update tool, width picture upload and a google maps api

Openmoko Local Groups: Oslo

2009-03-03T12:30:17Z

Mariusno: /* People */

Welcome to the Openmoko group for people near Oslo, [[Openmoko_Local_Groups:_Norway|Norway]]!

This page is supposed to function as a means for Openmoko interested people near Oslo to find each other and get organized. Since the community is still quite small, please remember to add yourself to the list.

The list also shows who you can contact to ask for help if you have bricked your device and need to borrow a [[Debug board|debug board]] to unbrick it.

== Resources ==
We have a Google Group http://groups.google.com/group/gta0x with a mailing list for discussions in Norwegian.

== People ==
{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
!Has Device
!Has Debug Board
|-
|[[User:aevin|Eivind S]]
|Linux, (embedded) programming
|User and developer
|Oslo
|GTA02v5-r owner, DBv3 keeper
![[Image: Moko.jpg|center]]
![[Image: MokoBox.jpg|center]]
|-
|[[User:deadcyclo|Brendan Johan Lee]]
|Linux, programming
|User and developer. Will now be using the Freerunner on my mastersproject.
|Oslo
|GTA02 owner
![[Image: Moko.jpg|center]]
!
|-
|[[User:torito|Jose G]]
|Linux, PyS60
|User and developer
|Oslo
|Awaits [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]
!
!
|-
|[[User:terje|Terje Sannum]]
|Linux, programming, electronics
|User, developer
|Oslo
|GTA01Bv4 owner
|[[Image: Moko.jpg|center]]
![[Image: MokoBox.jpg|center]]
|-
|[[User:Holone|Harald Holone]]
|Linux, OpenStreetMap
|User, developer
|Halden
|GTA01BV4 owner
|[[Image: Moko.jpg|center]]
|
|-
|[[User:Tingo|Torfinn Ingolfsen]]
|electronics,Linux, FreeBSD, bug-finding
|User, bug-finder
|Oslo
|GTA01BV4 + GTA02 owner
|[[Image: Moko.jpg|center]]
!
|-
|[[User:Goxboxlive | Goxboxlive]]
|User, bug-finder
|Make Linux run on HTC devices
|Oslo
|Maintaining [http://www.linuxtogo.org/~htcpxa htcpxa] and make various Linux images for HTC devices. GTA01Bv4, Neo Advanced (Owner)]
|[[Image: Moko.jpg|center]]
|[[Image: MokoBox.jpg|center]]
|-
|[[User:Alexey Feldgendler|Alexey Feldgendler]]
|Linux, programming
|User, developer
|Oslo
|[[GTA02]] owner
![[Image: Moko.jpg|center]]
|-
|[[User:quatrox|quatrox]]
|Electronics, Linux, Embedded, Gentoo
|User, bug-finder
|Kongsberg
|GTA02v5-r + DBv3 owner
|[[Image: Moko.jpg|center]]
|[[Image: MokoBox.jpg|center]]
|-
|[[User:mariusno|Marius Næss Olsen]]
|GNU/Linux, programming
|User, developer
|Oslo
|[[GTA02]] owner
![[Image: Moko.jpg|center]]
!
|}

See also [[Talk:Openmoko_Local_Groups:_Norway]] for national matters.

[[Category:Openmoko Local Groups]]

Openmoko Local Groups: Oslo

2009-03-03T12:29:43Z

Mariusno: /* People */

Welcome to the Openmoko group for people near Oslo, [[Openmoko_Local_Groups:_Norway|Norway]]!

This page is supposed to function as a means for Openmoko interested people near Oslo to find each other and get organized. Since the community is still quite small, please remember to add yourself to the list.

The list also shows who you can contact to ask for help if you have bricked your device and need to borrow a [[Debug board|debug board]] to unbrick it.

== Resources ==
We have a Google Group http://groups.google.com/group/gta0x with a mailing list for discussions in Norwegian.

== People ==
{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
!Has Device
!Has Debug Board
|-
|[[User:aevin|Eivind S]]
|Linux, (embedded) programming
|User and developer
|Oslo
|GTA02v5-r owner, DBv3 keeper
![[Image: Moko.jpg|center]]
![[Image: MokoBox.jpg|center]]
|-
|[[User:deadcyclo|Brendan Johan Lee]]
|Linux, programming
|User and developer. Will now be using the Freerunner on my mastersproject.
|Oslo
|GTA02 owner
![[Image: Moko.jpg|center]]
!
|-
|[[User:torito|Jose G]]
|Linux, PyS60
|User and developer
|Oslo
|Awaits [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]
!
!
|-
|[[User:terje|Terje Sannum]]
|Linux, programming, electronics
|User, developer
|Oslo
|GTA01Bv4 owner
|[[Image: Moko.jpg|center]]
![[Image: MokoBox.jpg|center]]
|-
|[[User:Holone|Harald Holone]]
|Linux, OpenStreetMap
|User, developer
|Halden
|GTA01BV4 owner
|[[Image: Moko.jpg|center]]
|
|-
|[[User:Tingo|Torfinn Ingolfsen]]
|electronics,Linux, FreeBSD, bug-finding
|User, bug-finder
|Oslo
|GTA01BV4 + GTA02 owner
|[[Image: Moko.jpg|center]]
!
|-
|[[User:Goxboxlive | Goxboxlive]]
|User, bug-finder
|Make Linux run on HTC devices
|Oslo
|Maintaining [http://www.linuxtogo.org/~htcpxa htcpxa] and make various Linux images for HTC devices. GTA01Bv4, Neo Advanced (Owner)]
|[[Image: Moko.jpg|center]]
|[[Image: MokoBox.jpg|center]]
|-
|[[User:Alexey Feldgendler|Alexey Feldgendler]]
|Linux, programming
|User, developer
|Oslo
|[[GTA02]] owner
![[Image: Moko.jpg|center]]
|-
|[[User:quatrox|quatrox]]
|Electronics, Linux, Embedded, Gentoo
|User, bug-finder
|Kongsberg
|GTA02v5-r + DBv3 owner
|[[Image: Moko.jpg|center]]
|[[Image: MokoBox.jpg|center]]
|-
|[[User:Marius Næss Olsen|mariusno]]
|GNU/Linux, programming
|User, developer
|Oslo
|[[GTA02]] owner
![[Image: Moko.jpg|center]]
!
|}

See also [[Talk:Openmoko_Local_Groups:_Norway]] for national matters.

[[Category:Openmoko Local Groups]]

Openmoko Local Groups: Oslo

2009-03-03T12:29:12Z

Mariusno: /* People */

Welcome to the Openmoko group for people near Oslo, [[Openmoko_Local_Groups:_Norway|Norway]]!

This page is supposed to function as a means for Openmoko interested people near Oslo to find each other and get organized. Since the community is still quite small, please remember to add yourself to the list.

The list also shows who you can contact to ask for help if you have bricked your device and need to borrow a [[Debug board|debug board]] to unbrick it.

== Resources ==
We have a Google Group http://groups.google.com/group/gta0x with a mailing list for discussions in Norwegian.

== People ==
{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
!Has Device
!Has Debug Board
|-
|[[User:aevin|Eivind S]]
|Linux, (embedded) programming
|User and developer
|Oslo
|GTA02v5-r owner, DBv3 keeper
![[Image: Moko.jpg|center]]
![[Image: MokoBox.jpg|center]]
|-
|[[User:deadcyclo|Brendan Johan Lee]]
|Linux, programming
|User and developer. Will now be using the Freerunner on my mastersproject.
|Oslo
|GTA02 owner
![[Image: Moko.jpg|center]]
!
|-
|[[User:torito|Jose G]]
|Linux, PyS60
|User and developer
|Oslo
|Awaits [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]
!
!
|-
|[[User:terje|Terje Sannum]]
|Linux, programming, electronics
|User, developer
|Oslo
|GTA01Bv4 owner
|[[Image: Moko.jpg|center]]
![[Image: MokoBox.jpg|center]]
|-
|[[User:Holone|Harald Holone]]
|Linux, OpenStreetMap
|User, developer
|Halden
|GTA01BV4 owner
|[[Image: Moko.jpg|center]]
|
|-
|[[User:Tingo|Torfinn Ingolfsen]]
|electronics,Linux, FreeBSD, bug-finding
|User, bug-finder
|Oslo
|GTA01BV4 + GTA02 owner
|[[Image: Moko.jpg|center]]
!
|-
|[[User:Goxboxlive | Goxboxlive]]
|User, bug-finder
|Make Linux run on HTC devices
|Oslo
|Maintaining [http://www.linuxtogo.org/~htcpxa htcpxa] and make various Linux images for HTC devices. GTA01Bv4, Neo Advanced (Owner)]
|[[Image: Moko.jpg|center]]
|[[Image: MokoBox.jpg|center]]
|-
|[[User:Alexey Feldgendler|Alexey Feldgendler]]
|Linux, programming
|User, developer
|Oslo
|[[GTA02]] owner
![[Image: Moko.jpg|center]]
|-
|[[User:quatrox|quatrox]]
|Electronics, Linux, Embedded, Gentoo
|User, bug-finder
|Kongsberg
|GTA02v5-r + DBv3 owner
|[[Image: Moko.jpg|center]]
|[[Image: MokoBox.jpg|center]]
|-
|[[User:Marius Næss Olsen|Marius Næss Olsen]]
|GNU/Linux, programming
|User, developer
|Oslo
|[[GTA02]] owner
![[Image: Moko.jpg|center]]
!
|}

See also [[Talk:Openmoko_Local_Groups:_Norway]] for national matters.

[[Category:Openmoko Local Groups]]

Manually using Bluetooth

2009-03-02T11:42:33Z

Mariusno: /* OBEX */

{{InProgress}}
Bluetooth is one of the core functions of the Neo1973, however it is basically unimplemented on the software side at the moment.
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.

This page details how to use bluetooth from the command line.
We have quite a lot of plans about what exactly Bluetooth should be used for.

== Power it up ==

Power up the adapter by clicking on the bluetooth icon in the top bar and selecting power on.

The old way to do it is a shell command (for kernels before 2.6.24):

root@fic-gta01:~# echo 1 > /sys/bus/platform/devices/gta01-pm-bt.0/power_on

For kernel 2.6.24 (or later) use

root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on

and on the GTA02 *only* (i.e. not on the GTA01) also use

root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset

But nowadays[http://permalink.gmane.org/gmane.comp.hardware.smartphones.userland/165], one should use [[Dbus device API]]s!

At the shell, "hciconfig" should print information about the adapter if it powered up properly:

hciconfig

The devices should show as UP. If not you can use

hciconfig <device> up

== Bluetooth Functions ==

===Configuring Bluetooth on Openmoko 2007.2 (August 27 snapshot with kernel 2.6.21.6-moko11) ===

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

=== Scanning for bluetooth devices ===

hcitool scan

This will list the addresses of any discoverable bluetooth devices in the vicinity

=== passkey agent example ===

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.

passkey-agent --default 0000 &

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

In debian there is no passkey-agent binary but the package bluez-utils has its source code at /usr/share/doc/bluez-utils/examples/passkey-agent.c.gz.

=== HID (Human Input Device) ===

==== Being able to use HID devices ====

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

We want to be able to use a bluetooth keyboard to type into the various applications of our Neo1973.
To use a Bluetooth Keyboard type: (11:22:33:44:55:66 is the Address of your BT-Keyboard)

hidd --connect 11:22:33:44:55:66

and press "Connect" on your BT-KB. Alternately, if you know that only one BT-Keyboard is within range, you can just:

hidd --search

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.

Tested on:
* [http://www.logitech.com/index.cfm/keyboards/keyboard/devices/3848&cl=us,en Logitech diNovo Mini] Works well, very portable and the touchpad also works just fine. Also has no problems with double letters.
* [http://www.logitech.com/index.cfm/products/details/US/EN,CRID=2166,CONTENTID=10717 Logitech Dinovo Edge]
* [http://www.logitech.com/index.cfm/keyboards/keyboard_mice_combos/devices/164&cl=us,en Logitech Dinovo Media Desktop (keyboard)]
* [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.
* [http://blog.russnelson.com/chordite Chordite]. This keyboard uses the Broadcom BCM2042 BT keyboard controller along with a custom driver.
* [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)
* [http://www.apple.com/support/keyboard/ Apple's white "Wireless Keyboard (original)"] - details may be the same as above. (tested some time ago)
* [http://www.frogpad.com/ FrogPad] - as above
* [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.
** Freeedom Universal Keyboard Model G912 does not work (see Discussion Page)
* [http://www.nextag.com/Playstation-3-Logitech-Cordless-564345667/prices-html?nxtg=f8320a24052a-7789F8FE732FF6E3 Logitech Playstation 3 Keyboard] Works well, Mouse pad works.
* [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...)
* [http://www.vkb-support.com/ I-Tech Virtual Laser Keyboard] works. Cursor keys not recognized as such, but produce keycodes than can be mapped.

This is a script that I've ([[User:ChristW]]) been using with varying results. YMMV:
<pre>
echo Power on
echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on
sleep 1
echo Reset on
echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset
sleep 1
echo Reset off
echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset
sleep 1
echo hciconfig down
hciconfig hci0 down
sleep 1
echo hciconfig up
hciconfig hci0 up
sleep 1
echo Connect
hidd --connect XX:XX:XX:XX:XX:XX
</pre>

==== Acting as HID device ====

We want to be able to use the Neo as a HID device, being able to use it as controller for presentations. See [[ReMoko]]

=== RFCOMM ===

Here's how to connect to an external Bluetooth GPS and read NMEA data (Tested with a Holux GPSSlim236 and a Nokia LD-3W ).

First, switch on the GPS and identify the BT address:

hcitool scan

Then, edit /etc/bluetooth/rfcomm.conf, which by default has all settings commented out, to something like this:

rfcomm0 {
# Automatically bind the device at startup
bind no;
# Bluetooth address of the device
device 00:11:22:33:44:55;
# RFCOMM channel for the connection (check your GPS docs for details)
channel 1;
# Description of the connection
comment "Bluetooth GPS";
}

Restart the BT services:

root@neo:~$ /etc/init.d/bluetooth stop
root@neo:~$ /etc/init.d/bluetooth start

You should now be able to bind the GPS to /dev/rfcomm0, like this:

root@neo:~$ rfcomm bind 0

Confirm the connect:

root@neo:~$ rfcomm
rfcomm0: 00:11:22:33:44:55 channel 1 clean

... and watch the NMEA strings coming from your GPS:

root@neo:~$ cat /dev/rfcomm0
$GPGGA,111748.000,5907.6964,N,01121.1787,E,1,06,1.2,57.7,M,40.1,M,,0000*6F
$GPRMC,111748.000,A,5907.6964,N,01121.1787,E,0.00,94.94,160807,,,A*50
$GPVTG,94.94,T,,M,0.00,N,0.0,K,A*3D

If you have nothing better to do, you can now pinpoint my office :-).

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

power on bluetooth:
if you use FSO image
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
else: (GTA02 only)
root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset

[http://linux.die.net/man/5/hcid.conf hcid.conf]
modify /etc/bluetooth/hcid.conf

<pre>
#
# HCI daemon configuration file.
#

# HCId options
options {
# Automatically initialize new devices
autoinit yes;

# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;

# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;

# Default PIN code for incoming connections
passkey "1234";
}

# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "%h-%d";

# Local device class
class 0x000100;

# Default packet type
pkt_type DH1,DM1,HV1;

# Inquiry and Page scan
iscan enable; pscan enable;

# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;

# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
}
</pre>

[http://linux.die.net/man/8/hcid hcid] - Bluetooth Host Controller Interface Daemon

All paired devices information are stored in /var/lib/bluetooth/BT HW addr folder
eg.
<pre>
root@om-gta02:/var/lib/bluetooth/00:06:6E:16:EB:C7# ls
classes features lastused names panu
config gn manufacturers nap
</pre>

Display local devices
root@om-gta02:/# hcitool dev

Scan all nearby bluetooth devices
root@om-gta02:~# hcitool scan

Browse what kind of services in this device
root@om-gta02:~# sdptool browse 00:18:C5:42:18:78

<pre>
Browsing 00:18:C5:42:18:78 ...

Service Name: OBEX File Transfer
Service RecHandle: 0x1005b
Service Class ID List:
"OBEX File Transfer" (0x1106)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 11
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"OBEX File Transfer" (0x1106)
Version: 0x0100

Service Name: OBEX Object Push
Service RecHandle: 0x1005e
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 9
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100

</pre>

Use obexpush and obexftp tools

install obexpush, obexftp packages
opkg install obexpush [http://www.go2linux.org/linux-command-line-obexftp-man-page obexftp]

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.

<pre>
root@om-gta02:~# ps aux | grep opd
root 1322 0.0 0.4 1972 604 ? Ss 16:21 0:00 opd: waiting for incomming OBEX connections on channel 10...
</pre>

How to pair with a bluetooth device, check [http://wiki.bluez.org/wiki/Security bluez wiki]

=== Networking ===

==== Using PC's connection from Neo ====

===== Bluetooth networking with a Linux system =====

Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.

'''On the laptop'''

* Start bluetooth
/etc/init.d/bluetooth start

* Start pand as server
pand -s

* As soon as pand is started on the phone configure your IP address
ip a add 10.0.0.1/24 dev bnep0
ip l set bnep0 up

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

'''On the Neo'''

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

* Power on bluetooth (see above)

* Scan for the laptop
root@fic-gta01:~$ hcitool scan
Scanning ...
00:0E:6D:C0:0l:6A Sho
00:20:E0:5A:FE:C8 BlueZ (0)

* Connect to the laptop pand
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8

* Configure your IP address
ip a add 10.0.0.2/24 dev bnep0
ip r add default via 10.0.0.1

* Sometimes you may need to bring up the bnep0 on the phone as well:
ip l set bnep0 up
* Enjoy

*--[[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).
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.

Should see log line like
''pand[17965]: New connection from 00:06:6E:XX:XX:XX at bnep0''

if connection is successful in server's /var/log/messages.

===== Bluetooth networking with a MacOS X system =====

Please refer to [[MacOS_X#Bluetooth_2]]

For using the Neo as a dialup Bluetooth server and the Mac as the client, please see below at [[Manually_using_Bluetooth#PPP_Networking]]

===== Bluetooth networking with a Windows XP system =====

This was tested with a Windows XP SP2 on a IBM Thinkpad T41 with the Widcomm BT stack

* Start bluetooth on Windows XP

* Enable "Network Access" in the Bluetooth configuration

* Scan for the Neo and pair with the Neo (right click, select pair)

On the Neo

* Enable PAN support on the Neo by changing Autostart from false to true in /etc/bluetooth/network.service

* Power on bluetooth (see above)

* Scan for the laptop
root@fic-gta01:~$ hcitool scan
Scanning ...
<laptop_bt_address> Thinkpad
...

* Connect to the laptop pand
pand -c <laptop_bt_address> -r PANU -d NAP -e bnep0 -A -E -S
(add '-n' to see the pand status messages until you get it right)

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:
pand -l -r PANU -d NAP -e bnep0 -A -E -S
(add '-n' to see the pand status messages until you get it right)

* Configure your IP address. It should work like when connecting to Linux:
ip a add 10.0.0.2/24 dev bnep0
ip r add default via 10.0.0.1
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.

* You should now be able to ssh/putty from Windows to your Neo. Enjoy!
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.

===== PPP Networking =====

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:

* Edit the /etc/default/bluetooth file and set the following options:
RFCOMM_ENABLE=true
DUND_ENABLE=true
DUND_OPTIONS="--listen --persist call dun"

* Create an /etc/ppp/peers/dun file with options like the following:
115200
192.168.2.202:192.168.2.200
passive
local
noipdefault
noauth
nodefaultroute

* Restart bluetooth (/etc/init.d/bluetooth stop ; /etc/init.d/bluetooth start)

To connect from a MacOS 10.3 client:

* Open "Applications/Utilities/Bluetooth Serial Utility"

* Click on "New"

* Choose a name, then click "Choose Device"

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

* Select "Port type: RS-232" and "Show in Network Preferences". Click OK.

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

* Choose "Show: <your-device-name>", then click "Modem"

* 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".

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

===== Bluetooth networking with a Linux system - More secure way =====

''Check this, probably needs some corrections''

Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.

On the laptop

* check these options in /etc/bluetooth/hcid.conf
security auto;
passkey "your pin";
lm master;

* Start bluetooth
# /etc/init.d/bluetooth start

* Start pand as server
pand --listen --role NAP --encrypt

* Add in /etc/network/interfaces (see [[USB_Networking]])
auto bnep0
iface bnep0 inet static
address 192.168.1.1
netmask 255.255.255.0
network 192.168.1.0
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.1.0/24
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT

On the Neo

* Power on bluetooth (see above)

* Scan for the laptop
root@fic-gta01:~$ hcitool scan
Scanning ...
00:20:E0:5A:FE:C8 laptop

* Set pin
root@fic-gta01:~$ passkey-agent 'your pin' 00:20:E0:5A:FE:C8 &

* Connect to the laptop pand
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8

* Configure your IP address
root@fic-gta01:~$ ifconfig bnep0 192.168.1.2
root@fic-gta01:~$ route add default gateway 192.168.1.1

* Enjoy

==== Using Neo's connection from PC ====

===== Calling Neo's GPRS modem via Bluetooth =====

In this mode, Neo would behave like any other phone which can be used from a PC to get a network connection.

This section not written yet. Has someone set it up?

===== Sharing existing Neo's connection =====

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.

On the PC
# Check with hciconfig you have working Bluetooth
On the Neo
(if on Debian etc., remember modprobe ohci_hcd hci_usb)
# Initialize Bluetooth as told before:
## echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on
## echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset
# install iptables: opkg install http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/iptables_1.3.8-r4.1_armv4t.ipk
# modprobe bnep
# Check that hcid is running both on Neo and PC (Bluetooth 4.x: install bluez-compat)
# Use default passkey "1234" in /etc/bluetooth/hcid.conf
# 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
# ifconfig bnep0 10.0.5.2 up
# echo 1 > /proc/sys/net/ipv4/ip_forward
# iptables -t nat -A POSTROUTING -j MASQUERADE -o ppp0
On the PC:
# sudo pand --connect <your bluetooth mac address> --service NAP --autozap
# ifconfig bnep0 10.0.5.1 up
# You can test the connection with ping 10.0.5.2
# sudo ip route add default via 10.0.5.2 dev bnep0
# [not automated yet] add GPRS connection's nameservers to /etc/resolv.conf

== Advanced Audio Distribution Profile (A2DP) ==

See [[A2DP]].

== Headset Audio ==

[[Neo1973_Audio_Subsystem]] has detail about alsa settings and a proposal for audio scenario management.

To try this out, follow the instructions on the [[A2DP]] page to install software and run the passkey agent.

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.

Put the headset in pairing mode. Replace the bluetooth address below with your headset's and run the python script:

#!/usr/bin/python
import dbus
bus = dbus.SystemBus()
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')
conn = manager.ActivateService('audio')
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')
path = audio.CreateHeadset('00:0B:2E:39:33:22')
audio.ChangeDefaultHeadset(path)
headset = dbus.Interface (bus.get_object(conn, path), 'org.bluez.audio.Headset')
headset.Connect()
headset.Play()

Now place a call and try to route it to bluetooth (after it's in progress):

alsactl -f /etc/gsmbluetooth.state restore

You may also be able to listen to system audio given the right state file:

alsactl -f /etc/systembluetooth.state restore
madplay song.mp3

==Bluetooth Headset on Freerunner ==

[http://lists.openmoko.org/pipermail/support/2008-September/thread.html#2627 This thread] suggests the following:

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

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

:http://handheldshell.com/BtConfigure.py
:Put the headset in pairing mode ( this only needs to be done once for each new headset ) and run
BtConfigure.py

:Download the the following python scripts to set up the audio service and set the headset as the default device:

:http://handheldshell.com/BtHeadset.py
:http://handheldshell.com/passkey.py
:http://handheldshell.com/BtHeadsetDisconnect.py
:http://handheldshell.com/python-pyalsaaudio_0.3-ml0_armv4t.ipk - can someone add python-pyalsa to the feeds ?

:Download the the following python scripts if you prefer not to mess around with alsactl:

:http://handheldshell.com/pymixer.py
:http://handheldshell.com/volume.desktop

:put pymixer in /usr/bin

chmod u+x /usr/bin/pymixer.py

:put volume.desktop in /usr/share/applications

:Get the [[http://handheldshell.com/gsm_headset.txt alsa state file]] - this state file _WORKS_, mic and earphones are properly routed

cp gsm_headset.txt /usr/share/openmoko/scenarios/btheadset.state

:from the home screen run Volume

:from the terminal run

BtHeadset.py

:Wait until it says waiting for call to end, you should hear static in the headset. If you don't something has gone wrong.

:Now start the call

:In the volume control switch to the btheadset tab. press restore

:You should now hear the call in your headset.

:End the call

BtHeadsetDisconnect.py

:This was all done with the 2008-updates image from sept 4.

:The new scripts rely on a specific format for the .asoundrc . A stanza like this is required :

pcm.headset {
type bluetooth
device <headset mac>
profile "voice"
}

== Debugging ==

If anything goes wrong, capture the bluetooth traffic with
sudo hcidump -l 4096 -w bt.dump
and attach bt.dump to your bug reports etc.

== Further reading ==

http://www.holtmann.org/papers/bluetooth/ols2006_slides.pdf
http://wiki.bluez.org/wiki/Audio#org.bluez.Audio
http://www.gentoo.org/doc/en/bluetooth-guide.xml

{{Languages|Manually_using_Bluetooth}}

[[Category:Bluetooth| ]]
[[Category:Networking]]
[[Category:Application Developer]]