bluetooth and obexftp problems

**cw9000** · 12-Aug-2014, 15:13

Hi. I just bought a usb bluetooth dongle for opensuse 13.1 64 bit machine. Running gnome, have all kde packages installed. When I plugged it in "lsusb" reported it as plugged in and in HCI mode. I didn't know how to use it so I searched and found bluez and bluedevel. Well bluedevil was the only thing that showed up under my apps so I used that, even though its kde. So I connected my samsung s3 and it seemed to be working fine, but I tried to browse it in dolphin and all it would do was show the folders. Then I right clicked the bluedevil icon and found my device and clicked on "browse device". This opened up Konqueror and I successfully copy and pasted files back and forth to the phone. I wanted to use Gnome however, so I logged out and back in and Gnome recognized bluetooth devices. However, obexftp is now completely not working. I even tried restarting computer, starting a kde session. I installed obexfs and obexftp. When I run the command

Code:

obexftp -b <address> -l

I get unable to connect ( not very informative). I've used blueman. done everything I can think of. I went into gnome settings -> Sharing and turned it on for bluetooth. Nothing gets obexftp working. When I try to "Browse Device" in Bluedevil, it opens up Konqueror but it says "The process for obexftp://<ad:dr:e:ss> protocol died unexpectedly". Same thing in Dolphin.

The thing is...I HAD this working. My bluetooth keyboard and mouse work fine. any thoughts on how to get obexftp working?

**deano_ferrari** · 12-Aug-2014, 17:39

I don't have a lot of experience with BT connectivity and I don't have any definitive answers, but I currently have two devices to play with: an iPhone and an Android OS phone. Using 'bluetoothctl' CLI, I note that my iPhone reports the following

Code:

# info 50:EA:D6:67:38:93
Device 50:EA:D6:67:38:93
        Name: Dean’s iPhone
        Alias: Dean’s iPhone
        Class: 0x7a020c
        Icon: phone
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: yes
        UUID: Vendor specific           (00000000-deca-fade-deca-deafdecacafe)
        UUID: Service Discovery Serve.. (00001000-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: NAP                       (00001116-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
        UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
        UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v05ACp1297d0710

* Note that it provides no OBEX protocol support, so sharing files this way is not possible with this particular device.

Next the Android phone...

Code:

# info E4:2D:02:91:5C:86
Device E4:2D:02:91:5C:86
        Name: Vodafone 875
        Alias: Vodafone 875
        Class: 0x5a0204
        Icon: phone
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: no
        LegacyPairing: yes
        UUID: Dialup Networking         (00001103-0000-1000-8000-00805f9b34fb)
        UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
        UUID: NAP                       (00001116-0000-1000-8000-00805f9b34fb)
        UUID: GN                        (00001117-0000-1000-8000-00805f9b34fb)
        UUID: Imaging Responder         (0000111b-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
        UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        Modalias: bluetooth:v0046p0802d0903

I can use Dolphin to push files to the phone using the 'bluetooth://' KIO like this

Code:

bluetooth://e4-2d-02-91-5c-86/

but that is all.

FWIW, the 'obexftp://' protocol fails with the same message that you report.

**cw9000** · 12-Aug-2014, 17:57

thanks for that. yeah my device shows the following

Code:

Name: SGH-T999L
        Alias: SGH-T999L
        Class: 0x5a020c
        Icon: phone
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
        UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
        UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
        UUID: PANU                      (00001115-0000-1000-8000-00805f9b34fb)
        UUID: NAP                       (00001116-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
        UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
        UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (fbe4be12-374a-486b-a473-24e39408a24d)
        Modalias: bluetooth:v0075p0100d0200

I have no problems sending a file to the phone, but I wish obexftp was working.

**deano_ferrari** · 12-Aug-2014, 18:52

I have no problems sending a file to the phone, but I wish obexftp was working.

It may also depend on the specific hardware concerned. You may want to consider submitting a bug report.

If you are in a wireless networking environment, I would consider investigating alternative network-based connectivity instead.

**cw9000** · 14-Aug-2014, 09:40

A bug report....wouldn't know where to start. As far as other options for connectivity...I have plenty. Just wanted to get the bluetooth working. I can plug the phone into my computer, ssh into my phone. If I want to transfer files some other way I can use otg cable and memory stick. I can ftp into my computer using ES File Explorer and transfer files to and from the phone. Anyway, thanks for your help.

**deano_ferrari** · 14-Aug-2014, 13:59

Originally Posted by cw9000

A bug report....wouldn't know where to start.

It's actually not that difficult, and it's the only way to bring it to the attention of the developers so that any issues can be fixed. Here's a guide...

http://en.opensuse.org/openSUSE:Submitting_bug_reports