[Pkg-bluetooth-discuss] User experience pairing Samsung Omnia (Windows Mobile 6.1) with wheezy

Thu Jan 23 13:53:33 UTC 2014

Package: bluez
Version: 4.99-2

Package: gnome-bluetooth
Version: 3.4.2-1

$ uname -a
3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
$ cat /etc/debian_version
7.3

I spent some time searching how to configure bluetooth to use my
Samsung Omnia as a bluetooth modem, as it does not work out of the box.
In the mailing lists archive I could not find useful related cased, only
spam or uninformative bug reports as #735544.

From #595373: Unable to use DUN with my phone
"Well, either all software is similarly broken or the problem is in
bluez itself. gnome-bluetooth, kdebluetooth and bluedeveil all show
their pairing wizards without any options for DUN."

1)

#debian-bluetooth was quite empty so I started with the debian wiki:

< https://wiki.debian.org/BluetoothUser
"in Nautilus in the ~/public folder: When opening this folder, you find
a notification bar to define the sharing of data. This includes the
sharing via WebDAV, but also via Bluetooth. Furthermore, one can enable
receiving files via Bluetooth. These files are stored in ~/downloads."

I neither found that folder nor appeared a bar after creating it with
Nautilus 3.4.2.

https://wiki.debian.org/Bluetooth pointed to
http://anonscm.debian.org/viewvc/pkg-bluetooth/TODO?view=co&revision=0
which raised an exception:

An Exception Has Occurred
Python Traceback

Traceback (most recent call last):
  File "/usr/lib/viewvc/lib/viewvc.py", line 4322, in main
    request.run_viewvc()
  File "/usr/lib/viewvc/lib/viewvc.py", line 397, in run_viewvc
    self.view_func(self)
  File "/usr/lib/viewvc/lib/viewvc.py", line 2577, in view_checkout
    path, rev = _orig_path(request)
  File "/usr/lib/viewvc/lib/viewvc.py", line 792, in _orig_path
    return _path_parts(request.repos.get_location(path, pathrev, rev)),
rev
  File "/usr/lib/viewvc/lib/vclib/svn/svn_repos.py", line 763, in
get_location
    raise vclib.ItemNotFound(path)
ItemNotFound: TODO

4) I am new to the matter but some of the linked howtos definitively
are outdated and could be dicouraging or at least distracting for new
users:

https://wiki.debian.org/BluetoothPalmOSConnection
https://wiki.debian.org/UseYourCellPhoneAsModem
https://wiki.debian.org/Modem/3G
http://bluez.sourceforge.net/contrib/HOWTO-PAN
http://www.stolk.org/debian/bluetooth.html
http://wiki.maemo.org/Bluetooth_DUN
https://web.archive.org/web/20110912145857/http://ornellas.apanela.com/dokuwiki/pub:linux_bluetooth_gprs
https://web.archive.org/web/20080128210840/http://www.holtmann.org/linux/bluetooth/

The TODO in the linked svn pkg-bluetooth repo at least is from 2007. :)

2) This is what I tried to so far:

$ hcitool dev
Devices:
        hci0    00:1A:6B:BE:C2:EA

# bluez-test-device trusted 00:23:D6:98:A5:96
1

I added to /etc/bluetooth/hcid.conf

lm accept, master
device 00:1A:6B:BE:C2:EA {
    name "Samsung Omnia";
    auth enable;
    encrypt enable;}

In System config > bluetooth the device is listed, but the option to
activate it (On/Off switch) is greyed out. It shows:

Paired: Yes
Type: Phone
Address: 00:23:D6:98:A5:96

* If I activate on "Use phone as PAN/NAP" it says "Your phone is now
ready to use!", but nothing happens/is shown in the log and the network
connection is not available.
* Send files to the device: The selected file is shown on the device
  asking if I want to save it. Choosing yes, the file is stored in "My
  documents". +1
* Clicking on "Browse files" nothing seems to happen.

On the device under allowed services my laptop as activated for
"DFÜ-Netzwerk" (file transfer).

I removed the device from the list and paired it again:

Jan 23 14:18:28 6715s NetworkManager[2626]: <info> BT device 00:23:D6:98:A5:96 removed
Jan 23 14:18:28 6715s NetworkManager[2626]: <info> (00:23:D6:98:A5:96): now unmanaged
Jan 23 14:18:28 6715s NetworkManager[2626]: <info> (00:23:D6:98:A5:96): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
Jan 23 14:18:28 6715s NetworkManager[2626]: <info> (00:23:D6:98:A5:96): cleaning up...
Jan 23 14:18:28 6715s NetworkManager[2626]: <info> (00:23:D6:98:A5:96): taking down device.
Jan 23 14:18:30 6715s NetworkManager[2626]:    keyfile: removed /etc/NetworkManager/system-connections/abc Network-ab0c30a6-c94a-4120-940b-e10e217f7523.
Jan 23 14:18:39 6715s bluetoothd[26455]: Discovery session 0x7fe9dc54eb10 with :1.4198 activated
Jan 23 14:18:51 6715s bluetoothd[26455]: Stopping discovery
Jan 23 14:19:09 6715s bluetoothd[26455]: input-headset driver probe failed for device 00:23:D6:98:A5:96
Jan 23 14:19:09 6715s NetworkManager[2626]: <warn> (00:23:D6:98:A5:96): failed to look up interface index
Jan 23 14:19:09 6715s NetworkManager[2626]: <info> BT device abc (00:23:D6:98:A5:96) added (NAP)
Jan 23 14:19:09 6715s NetworkManager[2626]: <info> (00:23:D6:98:A5:96): new Bluetooth device (driver: 'bluez' ifindex: 0)
Jan 23 14:19:09 6715s NetworkManager[2626]: <info> (00:23:D6:98:A5:96): exported as /org/freedesktop/NetworkManager/Devices/46
Jan 23 14:19:09 6715s NetworkManager[2626]: <info> (00:23:D6:98:A5:96): now managed
Jan 23 14:19:09 6715s NetworkManager[2626]: <info> (00:23:D6:98:A5:96): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jan 23 14:19:09 6715s NetworkManager[2626]: <info> (00:23:D6:98:A5:96): deactivating device (reason 'managed') [2]
Jan 23 14:19:09 6715s NetworkManager[2626]: nm_system_iface_flush_routes: assertion `ifindex > 0' failed
Jan 23 14:19:09 6715s NetworkManager[2626]: nm_system_iface_flush_addresses: assertion `ifindex > 0' failed
Jan 23 14:19:09 6715s NetworkManager[2626]: <info> (00:23:D6:98:A5:96): device state change: unavailable -> disconnected (reason 'none') [20 30 0]

How can I change the displayed name of the device and the (outdated)
hostname of my computer in the bluetooth dialogue?

3) In the daemon.log I also found

Jan 23 13:13:41 6715s bluetoothd[25664]: Bluetooth daemon 4.99
Jan 23 13:13:41 6715s bluetoothd[25664]: Starting SDP server
Jan 23 13:13:41 6715s bluetoothd[25664]: Failed to init alert plugin
Jan 23 13:13:41 6715s bluetoothd[25664]: Failed to init time plugin
Jan 23 13:13:41 6715s bluetoothd[25664]: Failed to init gatt_example
plugin Jan 23 13:13:41 6715s bluetoothd[25664]: Listening for HCI
events on hci0 Jan 23 13:13:41 6715s bluetoothd[25664]: HCI dev 0 up
Jan 23 13:13:41 6715s bluetoothd[25664]: Proximity GATT Reporter
Driver: Operation not permitted (1) Jan 23 13:13:41 6715s
bluetoothd[25664]: input-headset driver probe failed for device
00:23:D6:98:A5:96 Jan 23 13:13:41 6715s bluetoothd[25664]: Unable to
load keys to adapter_ops: Function not implemented (38) Jan 23 13:13:41
6715s bluetoothd[25664]: Adapter /org/bluez/25664/hci0 has been enabled

which seems related to
https://lists.debian.org/debian-kernel/2012/10/msg00527.html
What does this mean?

I would like to test the experimental bluez (5.10) drivers, but wheezy
(4.9) hesitates to install them due to libc6.
Please tell if you need more detailed hardware specifications.

Thanks for your time and all hints,
kardan