RPi 3: Bluetooth: unable to send file to Windows 10 laptop

[xiphocoleon]

Hello --

I have been having lots of Bluetooth issues with my RPi. However, I'd like to keep this troubleshooting narrative focused on today's experiment: sending a file from my RPi 3 to an Asus Windows 10 laptop.

Here is my setup:

RPi OS: Raspian/Linux 8 Jessie
Running: Bluez 5.23 and Blueman 1.99~alpha1-1+deb8u1 (results from a grep search)

Asus Laptop: Windows 10, using a CSR 4.0 bluetooth dongle, as the computer doesn't have bluetooth built into it. I have successfully sent a file to this computer from a Mac desktop that has bluetooth.

If I click on the Blueman icon at the bottom of the RPi GUI and click "devices" I see my laptop with a magnifying glass/search glass icon over it. Also, in the bluetooth menu of my laptop's settings, I see my RPi's name, and it says "connected." However, for other devices, like my Mac desktop, my laptop's bluetooth devices list says "paired."

Back to my RPi. If I go to Blueman's menu, and click "Send Files to Device" and then choose a text file to send to my laptop, I will get an error box that says:

Service not supported by remote device

I suspect this is an issue with the Asus laptop, but I have not been able to solve this. Also, since the laptop says it is connected and not "paired" to the RPi, I suspect that there could be an issue also.

Can anyone make a suggestion about how to send this file via Bluetooth to my laptop?

Thank you.

[Douglas6]

First, find out what profiles your laptop provides. On the Pi's command line, enter bluetoothctl and type 'info <bdaddr>'. What does it say?

[xiphocoleon]

I have typed: info <laptop's bluetooth address> in the bluetoothctl menu in the terminal, and I received:

[bluetooth]# info 00:1A:7D:DA:71:13
Device 00:1A:7D:DA:71:13
Name: LASTCHANCEPC
Alias: LASTCHANCEPC
Class: 0x02010c
Icon: computer
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Dialup Networking (00001103-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: SIM Access (0000112d-0000-1000-8000-00805f9b34fb)


Also, on its own, in the Windows 10 Bluetooth preferences pane, the RPi, "mirror-pi", toggles every so often between "connected" and "paired." I tried sending a file when the RPi was paired. I received no notification on the laptop. On the Pi I received the same message as at the beginning of this thread, that "Service not supported by remote device" and while I initiate the transfer, in bluetoothctl in the terminal window, I see:

[CHG] Device 00:1A:7D:DA:71:13 Connected: yes
[CHG] Device 00:1A:7D:DA:71:13 Connected: no

as the laptop seems connected for a moment, but then as the file transfer fails, the laptop becomes disconnected.

Let me know if you have any thoughts about this. Thanks.

[Douglas6]

The bluetoothctl results look good: the laptop is paired and trusted, and is offering both OBEX object push and FTP services.
I don't have much experience with blueman. Could you try using ussp-push from the command line? See this post, but ignore the steps for pairing and trusting, which are old: viewtopic.php?p=675983#p675983

[xiphocoleon]

I downloaded and installed ussp-push to my Pi. I then followed through the post link you sent in the above post. This was very helpful! Thank you!

I was able to sdptool browse my Mac Pro 2009, found the Obex channel, and then I used ussp-push to successfully send a file via bluetooth from RPi to Mac Pro.

However, when I did the sdptool command targeting my Windows 10 laptop I received the messages below, and no Obex messages were given. I am not sure why this is.

Below is my command to browse my Windows 10 laptop, which uses a CSR 4.0 dongle to have bluetooth. Also, previously, above this device printed these lines, which made it seem like it had Obex ability:

UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)


pi@raspberrypi:~ $ sdptool browse 00:1A:7D:DA:71:13
Browsing 00:1A:7D:DA:71:13 ...
Service Name: Service Discovery
Service Description: Publishes services to remote devices
Service Provider: Microsoft
Service RecHandle: 0x0
Service Class ID List:
"SDP Server" (0x1000)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 1
"SDP" (0x0001)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100

Browsing 00:1A:7D:DA:71:13 ...
Service Search failed: Invalid argument
Service Name: Device ID Service Record
Service Description: Device ID Service Record
Service RecHandle: 0x10000
Service Class ID List:
"PnP Information" (0x1200)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 1
"SDP" (0x0001)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100

Browsing 00:1A:7D:DA:71:13 ...
Service Search failed: Invalid argument
Service Name: Device ID Service Record
Service Description: Device ID Service Record
Service RecHandle: 0x10002
Service Class ID List:
"PnP Information" (0x1200)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 1
"SDP" (0x0001)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100

Browsing 00:1A:7D:DA:71:13 ...
Service Search failed: Invalid argument
Service Name: Device ID Service Record
Service Description: Device ID Service Record
Service RecHandle: 0x10005
Service Class ID List:
"PnP Information" (0x1200)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 1
"SDP" (0x0001)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100

Browsing 00:1A:7D:DA:71:13 ...
Service Search failed: Invalid argument
Service RecHandle: 0x10007
Service Class ID List:
"AV Remote Target" (0x110c)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x0102
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0103

Service Name: Personal Ad Hoc User Service
Service Description: Personal Ad Hoc User Service
Service RecHandle: 0x10008
Service Class ID List:
"PAN User" (0x1115)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 15
"BNEP" (0x000f)
Version: 0x0100
SEQ8: 0 dd 6
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"PAN User" (0x1115)
Version: 0x0100

Service Name: Device ID Service Record
Service Description: Device ID Service Record
Service RecHandle: 0x10009
Service Class ID List:
"PnP Information" (0x1200)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 1
"SDP" (0x0001)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100

Browsing 00:1A:7D:DA:71:13 ...
Service Search failed: Invalid argument
Service RecHandle: 0x1000a
Service Class ID List:
"AV Remote Target" (0x110c)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x0102
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0103

Service Name: Personal Ad Hoc User Service
Service Description: Personal Ad Hoc User Service
Service RecHandle: 0x1000b
Service Class ID List:
"PAN User" (0x1115)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 15
"BNEP" (0x000f)
Version: 0x0100
SEQ8: 0 dd 6
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"PAN User" (0x1115)
Version: 0x0100

Service Name: Device ID Service Record
Service Description: Device ID Service Record
Service RecHandle: 0x1000c
Service Class ID List:
"PnP Information" (0x1200)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 1
"SDP" (0x0001)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100

Browsing 00:1A:7D:DA:71:13 ...
Service Search failed: Invalid argument
Service RecHandle: 0x1000d
Service Class ID List:
"AV Remote Target" (0x110c)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x0102
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0103

Service Name: Personal Ad Hoc User Service
Service Description: Personal Ad Hoc User Service
Service RecHandle: 0x1000e
Service Class ID List:
"PAN User" (0x1115)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 15
"BNEP" (0x000f)
Version: 0x0100
SEQ8: 0 dd 6
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"PAN User" (0x1115)
Version: 0x0100


All of the lines that say
Browsing 00:1A:7D:DA:71:13 ...
Service Search failed: Invalid argument
Make me think somehow Obex is not being discovered by this browse tool, but that is just a guess.

Any ideas?

Thank you.

[Douglas6]

I'm afraid I don't have an answer. I would have thought 'sdptool browse' would find the OBEX services, but I generally use bluetoothctl for service discovery, or 'sdptool browse local' for local services. I'm curious, what do you get with

Code: Select all

sdptool search --bdaddr 00:1A:7D:DA:71:13 OPUSH

or

Code: Select all

sdptool search --bdaddr 00:1A:7D:DA:71:13 FTP

[EDIT: Ah, I misunderstood. Works on the Mac, not on Windows 10. Dunno, I still use XP. Is there a Win 10 setting to permit Bluetooth file transfer?]

[xiphocoleon]

SOLVED:

In the bottom right-hand system tray of my Windows 10 machine, I just opened the Bluetooth icon, and clicked Receive File, and then the laptop just waits to receive the file.

Then, in my Blueman GUI window, I click the laptop which is already paired and connected, and I select to send file.

The file successfully sends.

Thank you.