Bug 787405

About the same results for the Rocketfish Mobile head phones. Very broken audio from Banshee player to head phone. Also on Fedora 16 with bluez-4.96-3.fc16.x86_64. Here is information from pacmd:

 index: 5
	name: <bluez_sink.00_18_16_06_43_05.monitor>
	driver: <module-bluetooth-device.c>
	flags: DECIBEL_VOLUME LATENCY 
	state: IDLE
	suspend cause: 
	priority: 1030
	volume: 0: 100% 1: 100%
	        0: 0.00 dB 1: 0.00 dB
	        balance 0.00
	base volume: 100%
	             0.00 dB
	volume steps: 65537
	muted: no
	current latency: 0.00 ms
	max rewind: 0 KiB
	sample spec: s16le 2ch 44100Hz
	channel map: front-left,front-right
	             Stereo
	used by: 0
	linked by: 0
	fixed latency: 51.12 ms
	monitor_of: 3
	card: 2 <bluez_card.00_18_16_06_43_05>
	module: 20
	properties:
		device.description = "Monitor of RF-MAB2"
		device.class = "monitor"
		device.string = "00:18:16:06:43:05"
		device.api = "bluez"
		device.bus = "bluetooth"
		device.form_factor = "headset"
		bluez.path = "/org/bluez/1082/hci0/dev_00_18_16_06_43_05"
		bluez.class = "0x240404"
		bluez.name = "RF-MAB2"
		device.icon_name = "audio-headset-bluetooth"
		device.intended_roles = "phone"

*** Bug 830626 has been marked as a duplicate of this bug. ***

Are you still have this problem in updated Fedora 16?

And please, could you try reproduce this bug in Fedora 18 Beta RC1?
http://dl.fedoraproject.org/pub/alt/stage/18-Beta-RC1/

I just did some more testing on this. Since bluetooth is so problematic and we're always wondering if it is hardware or software I bought the Iogear GBU521 USB Bluetooth 4.0 adapter to test with instead of the Intel motherboard SOC chip. I also install blueman and ran tests on Fedora 16 and Fedora 17, I do not have the Fedora 18 Beta yet.

Still does not work in Fedora 16. It seems to have degraded to where I'm not able to pair devices on that system now.

I did have success with Fedora 17 in pairing and playing music through the same Rocketfish head phones. I had to turn the volume way down to keep the static down. Found that I was only able to select telephoney device under the sound settings for hardware, would not work at all if I tried the A2DP option. I used Google Music and Rythmbox. Audio quality was not nearly as good as with my Galaxy Nexus phone.

I did manage to totaly crash the system once. Also manage by disabling blueman and then restarting blueman to get it in a mode where there was no sound hardware.
I'm running the latest released updates on both systems.

Rex, do you have idea why A2DP is not working in phonon?

i do not, sorry (else, I would've said something by now).  if i'd have to venture guesses, it'd be something lower level at issue here, like pulseaudio/bluetooth interaction or even possibly kernel (bluetooth) drivers.

I have now tested with Fedora 18 Beta. Works about like Fedora 17. I ran the Live 64 bit image off a stick. I did more fidling with sound and turning the head phones on and off and never had the system crash. Wonder if Blueman cuased that issue. I was able to select A2DP for a sound option but then could hear no audio. Quality might have been slightly better but hard to tell for sure. Still not close to what I get the the cellphone.

Noticed lots of dmesg entries of:
Bluetooth: hci SCO packet for unknown connection handle 0

At the end of this string of log entries the handle changed from 0 so this maybe during the pairing process.

If you need more testing or have specific things to try let me know. Thanks for the support.

You have to use BlueDevil to have working Bluetooth in KDE Plasma sessions, Blueman is not supported in KDE Plasma sessions.

I'm not using KDE, not even installed.

So, the systemsettings stuff you mentioned in comment #1 essentially only work for kde/phonon-based applications.

If that's not what you're using, then we'll have to back up a step or 2

Ah, just noticed original reporter != you.

I'd recommend you file a new bug then (against pulseaudio probably).  This bug is about something different essentially... though it's possible there's some common lower component at work as I alluded-to in comment #6

Given all this data, and from what I can gather from duped bug #830626, since pulseaudio/bluetooth apparently worked at some point and then stopped, this likely appears to be a bluetooth kernel/driver bug/regression.  reassigning

hrm, on second thought the original report was about phonon, let's keep this one, and dedup bug #830626 instead (folks not on phonon/kde should follow that one or file a new bug).

If this bug does not get moved soon to Fedora 17 or 18 it will get dropped when Fedora 16 goes end of life and we will loose all the history.

David, your bug is something different than the oringal reporter here.  I'll reiterate my suggestion from comment #11 that you file a new one.

> If this bug does not get moved soon to Fedora 17 or 18 it will get dropped when
> Fedora 16 goes end of life and we will loose all the history.

Nonsense. Bug history does not get lost when a bug gets closed, and any Fedora packager (e.g. me) or triager can reopen bugs.

Plus, as Rex says, your bug is not the same anyway, plase file a new one against pulseaudio.

Sorry for the bad phrasing, but ment to say that bugs sometimes do not get resolved by the end of support and are still an issue with the follow on releases.

Already opened a new report, 882594, against pulseaudio.

 Hi,

 I tried to install fedora 18 beta to see if the error is reproducible there but I couldn install F18 on the same laptop.
 I will report back as soon as I am able to install F18.

 Regards and sorry for the late reply.

 Enrique

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.