1

I've got a brand new bluetooth headphone Philips SHB7150 with a brand new Belkin bluetooth adapter V4.

The pairing is fine but after i cannot get the newly discovered headset in my pulseradio.

Instead I get the following image enter image description here with erratic behavior when trying to use the bluetooh headset.

LiveWireBT
  • 28,763
Laurent06000
  • 736
  • 2
  • 13
  • 28
  • I don't speak french, but I do have a Bluetooth headset and I don't see anything wrong in the screenshot. Please describe the erratic behaviour. – LiveWireBT May 25 '14 at 05:54
  • The erratic behaviour happens as following : when I select the headphone set, I'm not always able to use it as the sound output. It sometimes switch to internal speakers without any further message. I tried pactl load-module module-bluetooth-discover but this will only run once. – Laurent06000 May 25 '14 at 08:56
  • That sounds to me like an issue with the Bluetooth adpater (maintaining or establishing a connection). You should try another adapter. (http://www.amazon.de/dp/B003ZDW78C/ works fine with my Fidelio M1BT, it has the same ID on amazon.fr but worse rating. Also branding doesn't seem to matter as most if not all of these apdapters chips are made by CSR, which also owns aptX.) – LiveWireBT May 25 '14 at 09:49
  • The result is the same with two different adapters : One Trust V3.0 adapter and a brand new Belkin V4.0 adapter. To my opinion 10.04 is not mature enough to handle bluetooth properly – Laurent06000 May 26 '14 at 19:28
  • Moreover I do not see the headset in the list until I issue the command "pactl load-module module-bluetooth-discover". I really do not know what this command is meant for. – Laurent06000 May 26 '14 at 19:44
  • Does anyone have an idea about it ? I cannot imagine nobody has faced the same problem – Laurent06000 May 27 '14 at 12:45
  • Does not for me in the same configuration. problem re-occurs ... – Laurent06000 Sep 22 '15 at 00:42

2 Answers2

1

It is a bug that is already repored.

Gramic
  • 178
0

This was a bug reported in Gramic message.

It seems to be fixed after Bluetooth updates.

Works fine with a Belkin V4.0 USB Bluetooth adapter.

Laurent06000
  • 736
  • 2
  • 13
  • 28