Bluetooth puzzle

AmigaOne X1000 platform specific issues related to Linux only.
Post Reply
User avatar
kilaueabart
Posts: 1070
Joined: Mon Mar 05, 2012 2:36 am

Bluetooth puzzle

Post by kilaueabart »

Everything puzzles me nowadays.

I ordered a bluetooth USB adapter, on the chance that it might work, and hooray! Doesn't work with vmlinux-4.1 but 4.8(.8) does the trick. I can send files from Ubuntu to my phone or tablet.

However, if it try to read my cell phone or tablet from Ubuntu, I get
Failed to launch default file browser
The specified location is not supported
You can enter an alternate browser in service settings
No idea what "service settings" means, but not too important. I am able to send files from phone or tablet to Ubuntu, which is what I would normally do anyway, and I think I may have googled a fix for the failure to launch problem.
One of the devices I have paired with Ubuntu bluetooth is a bluetooth speaker. It gets listed as
BLKBOX POP360
Microphone
00:11:...
Why "Microphone"? And why when I have it paired and play a music file in Ubuntu does the sound only come from my desktop speakers and not from my bluetooth speaker? Again, not a very important matter, because the desktop speakers are the sensible way to play audio from the desktop, but it is a puzzle. I really only want to use it with phone or tablet, where it works fine.


One more puzzle. I keep getting one or two devices listed when I search that are complete mysteries. I thought devices have to be close to connect, but I live in a 5th floor apartment. Would something upstairs or downstairs be close enough?
User avatar
xeno74
Posts: 9348
Joined: Fri Mar 23, 2012 7:58 am

Re: Bluetooth puzzle

Post by xeno74 »

Hi Kilaueabart,

Please post the output of sdptool browse. With sdptool browse you can see which services are available on your cell phone and tablet.

Sometimes you have to activate the Bluetooth profile "ftp" on your cell phone and tablet as well.

Cheers,
Christian
http://www.amigalinux.org
http://www.supertuxkart-amiga.de

Running Linux on AmigaONEs can require some tinkering.
User avatar
kilaueabart
Posts: 1070
Joined: Mon Mar 05, 2012 2:36 am

Re: Bluetooth puzzle

Post by kilaueabart »

xeno74 wrote:Please post the output of sdptool browse. With sdptool browse[/] you can see which services are available on your cell phone and tablet.
Here is the output. It's awfully long, probably more than needed, but I don't understand it, so no idea what to leave out.

Edit, Monday: It seems this is all from my cell phone. I get it with cell phone bluetooth on and tablet bluetooth off. When I reverse that, cell phone off, and tablet on, sdptool browse finds nothing! Nonetheless, today I can both send and receive files between the desktop and the tablet, so no more problem! (Minor puzzle: Why does Bluetooth Devices > Setup > Connect want to treat both the phone and the tablet as "Audio source?")

Code: Select all

Inquiring ...
Browsing F8:95:C7:46:86:E7 ...
Service RecHandle: 0x10000
Service Class ID List:
  "Generic Attribute" (0x1801)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 31
  "ATT" (0x0007)
    uint16: 0x0001
    uint16: 0x0005

Service RecHandle: 0x10001
Service Class ID List:
  "Generic Access" (0x1800)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 31
  "ATT" (0x0007)
    uint16: 0x0014
    uint16: 0x001e

Service Name: Headset Gateway
Service RecHandle: 0x10002
Service Class ID List:
  "Headset Audio Gateway" (0x1112)
  "Generic Audio" (0x1203)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 2
Profile Descriptor List:
  "Headset" (0x1108)
    Version: 0x0102

Service Name: Handsfree Gateway
Service RecHandle: 0x10003
Service Class ID List:
  "Handsfree Audio Gateway" (0x111f)
  "Generic Audio" (0x1203)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 3
Profile Descriptor List:
  "Handsfree" (0x111e)
    Version: 0x0106

Service Name: AV Remote Control Target
Service RecHandle: 0x10004
Service Class ID List:
  "AV Remote Target" (0x110c)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 23
  "AVCTP" (0x0017)
    uint16: 0x0104
Profile Descriptor List:
  "AV Remote" (0x110e)
    Version: 0x0105

Service Name: Advanced Audio
Service RecHandle: 0x10005
Service Class ID List:
  "Audio Source" (0x110a)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 25
  "AVDTP" (0x0019)
    uint16: 0x0102
Profile Descriptor List:
  "Advanced Audio" (0x110d)
    Version: 0x0102

Service RecHandle: 0x10006
Service Class ID List:
  "AV Remote" (0x110e)
  "AV Remote Controller" (0x110f)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 23
  "AVCTP" (0x0017)
    uint16: 0x0104
Profile Descriptor List:
  "AV Remote" (0x110e)
    Version: 0x0105

Service Name: MAP SMS/MMS
Service RecHandle: 0x10008
Service Class ID List:
  "Message Access - MAS" (0x1132)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 4
  "OBEX" (0x0008)
Profile Descriptor List:
  "Message Access" (0x1134)
    Version: 0x0101

Service Name: OBEX Phonebook Access Server
Service RecHandle: 0x10009
Service Class ID List:
  "Phonebook Access - PSE" (0x112f)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 19
  "OBEX" (0x0008)
Profile Descriptor List:
  "Phonebook Access" (0x1130)
    Version: 0x0101

Service Name: OBEX Object Push
Service RecHandle: 0x1000a
Service Class ID List:
  "OBEX Object Push" (0x1105)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 12
  "OBEX" (0x0008)
Profile Descriptor List:
  "OBEX Object Push" (0x1105)
    Version: 0x0100
By the way, one of the mysterious devices that come up when I search is just this step-counting thing I have started wearing on my wrist.
Post Reply