I have a question about bluetooth on the A500.
I'm trying to get a headset to work, but I understand it lacks the profile to use the microphone portion. What I'm not able to determine is if this is permanent. Is this a hardware or software limitation? Is it possible for Acer to add this functionality in future updates?
Thanks,
-PW
From the Acer User's Guide:
Connecting a Bluetooth device
Only A2DP stereo headsets (without microphone) are supported. Please check for updates to the tablet's software which may add support for additional Bluetooth devices.
For Bluetooth settings, tap Apps > Settings > Wireless & networks > Bluetooth settings.
Tap Find nearby devices to scan for available devices.
I've been trying to get a BT headset working with my a500 as well - wanting to use a headset for Skype, Talk, and Tribair calls.
Tried editing etc/bluetooth/audio.conf; added "headset" to the "enable" line, removed the comment from the "HFP=true" line, and upped MaxConnections to 3. Also added "ro.bt.profiles=4270403" and "service.brcm.bt.ag_supported=1" to build.prop, as someone did to get BT handsfree profile working on the HTC Flyer.
I did manage, after doing all this, to get the headset to show up in the devices list with the profile "Headset - use for phone audio" rather than the one it was originally showing up with (can't remember what that one was exactly, but it was different and definitely not right). Unfortunately, though, it still shows in the list as "Paired but not connected", and will not connect no matter what I do.
Surely this should be a pretty easy fix - as I understand it the lack of HFP support is a software block, not a hardware deficiency. I'm getting out of my depth trying anything further than I already have...anyone have any more ideas for enabling this?
tardis.42 said:
I've been trying to get a BT headset working with my a500 as well - wanting to use a headset for Skype, Talk, and Tribair calls.
Tried editing etc/bluetooth/audio.conf; added "headset" to the "enable" line, removed the comment from the "HFP=true" line, and upped MaxConnections to 3. Also added "ro.bt.profiles=4270403" and "service.brcm.bt.ag_supported=1" to build.prop, as someone did to get BT handsfree profile working on the HTC Flyer.
I did manage, after doing all this, to get the headset to show up in the devices list with the profile "Headset - use for phone audio" rather than the one it was originally showing up with (can't remember what that one was exactly, but it was different and definitely not right). Unfortunately, though, it still shows in the list as "Paired but not connected", and will not connect no matter what I do.
Surely this should be a pretty easy fix - as I understand it the lack of HFP support is a software block, not a hardware deficiency. I'm getting out of my depth trying anything further than I already have...anyone have any more ideas for enabling this?
Click to expand...
Click to collapse
Just got the Acer A100 to play with and i noticed the same thing.
I was the one who posted the hack for Flyer but it wont work here.
I also modified what you have in the audio.conf file and got the same result.
I am thinking that it is either disabled in the Kernel or the radio does not support it. It pairs as headset but will never connect.
Both my Galaxy tab 10.1 and the previous xoom had no problems with headset profiles.
Anyone has any clue?
pacificwing said:
I have a question about bluetooth on the A500.
I'm trying to get a headset to work, but I understand it lacks the profile to use the microphone portion. What I'm not able to determine is if this is permanent. Is this a hardware or software limitation? Is it possible for Acer to add this functionality in future updates?
Thanks,
-PW
Click to expand...
Click to collapse
Hi, have u got the resolve about it？ I met this trouble as well...
how stupid. I hope 3.2 resolves this.in the meantime will a wired headset work for voice, Skype etc?
dweebken said:
From the Acer User's Guide:
Connecting a Bluetooth device
Only A2DP stereo headsets (without microphone) are supported. Please check for updates to the tablet's software which may add support for additional Bluetooth devices.
For Bluetooth settings, tap Apps > Settings > Wireless & networks > Bluetooth settings.
Tap Find nearby devices to scan for available devices.
Click to expand...
Click to collapse
now the devices DONT HAVE TO BE MIC-LESS lol. I own a RF-MAB2 aka Bluetooth Stereo Headset and mic for calls. The tablet will automatically set up the [email protected] with out the mic. So it will work even if you have a mic built in
I just realized this problem on my A100 which is running 3.2. How stupid of Acer to not support handsfree. It could be just a lack of software, but it could also be hardware. The chipset will support it, but if they failed to link the audio out from the bluetooth to the audio in at the chips level, its totally screwed.
DigitalMD said:
I just realized this problem on my A100 which is running 3.2. How stupid of Acer to not support handsfree. It could be just a lack of software, but it could also be hardware. The chipset will support it, but if they failed to link the audio out from the bluetooth to the audio in at the chips level, its totally screwed.
Click to expand...
Click to collapse
I can't speak for the hardware, but I know the software functionality is not there. The HSP protocol is NOT supported with this tablet, period.
Ugh - this is so frustrating. I just picked up a A501 to use with Skype and Dell Voice, and now I find out you can't pair a Bluetooth headset with it. That's about 75% of the reason I bought the darned thing!
im goin over this "alike" as i want my headset to able to capably work google now, hope i can find an answer im on day 2 already lol
I don't think bt headsets are going to work anytime soon on acer roms... They eventually might with CM once it fully works. As for acer, they (as well as most other tablet manufacturers) don't seem to think this is an important feature to have as tabs aren't meant to be used as a phone anyway. If you want something that works, use a cable headset.
Ever heard of skype? What about voip? Both work fine on the tabs, so of course peeps wanna use headsets with that. Preferably Bluetooth.
Sent from my A500 using xda premium
Hi all.
Here's what I'm seeing and what I'm trying to figure out.
On my new Nexus 4, which in other respects seems just fine, voice over Bluetooth is basically unusable. I first tried testing out voice commands for dialing etc., which consistently failed. A friend happened to call while I was doing this, and could barely make out what I was saying (reported it as choppy, digitized etc.).
This is using a Plantronics Discovery 975. Which works fine with my Nexus One, so isn't a faulty headset (I even had my wife's same model headset and tried it also). I don't have any other headsets handy.
This N4 *has* been upgraded to 4.2.1. After searching a bit, I found numerous reports and a couple articles re many BT features, including voice over BT, being broken to a great extent on many devices with 4.2.1 (or earlier, and getting still worse in 4.2.1). Those reports, however, mostly seemed to reference devices other than the N4 (though perhaps only due to its newness & relative scarcity, hard to know).
I then tried the headsets with my wife's Galaxy Nexus, which also had been upgraded to 4.2.1. On that, however, the voice over BT apparently worked fine, or at least much better -- sounded ok, and VR could recognize contacts to be called.
Thus I could at least conclude it isn't just voice over BT simply broken in 4.2.1 everywhere (which would have made things simple.. ), and it isn't simply voice over BT in 4.2.1 with the Discovery 975 either. So add in the Nexus 4.
I've seen many reports of BT streaming audio issues on the N4 with 4.2.1, but little at all about voice, and certainly some successful reports for voice.
So I'm trying to figure out: What is the likelihood that with all of the 4.2.1 Bluetooth troubles, there is a consequent BT software issue on my Nexus 4 when used with this Discovery 975 headset? Vs., what is the likelihood that my specific N4 has some kind of hardware issue with BT?
- How many folks are using voice over BT successfully? Anyone else having issues?
- What version does your N4 have -- 4.2.1, or earlier?
- If you used it *before* an upgrade to 4.2.1, did it work both before and after the upgrade, or did the upgrade introduce issues?
- Anyone specifically using the Plantronics Discovery 975, or another Plantronics?
Basically, I'd really like to avoid the crap shoot of exchanging the phone (BT voice is a critical feature for me), since it seems fine in all other respects, and with all of the manifest BT issues that appear to have been introduced with 4.2.1, that seems like at least a reasonable culprit.
However, if there aren't widespread issues with voice over BT on the N4 with 4.2.1, then it would seem the only way it would be a software issue, would be if it's the combination with my particular Plantronics headset model. Otherwise, I think I'd have to face the possibility of a hw issue. (Bad timing for me with 4.2.1's buggy BT issues, it really obscures the situation. )
Another useful test for me to try might be to revert back to the prior OS version and test with that, but I gather I have to root to do that, not sure if that also voids the warranty.. (hence preventing me from exchanging it if I did ultimately need to).
TIA
Bump.. help a brother out -- no one using voice over Bluetooth on their N4, or have some perspective on the above?
Seems like a lot more people talking about audio streaming over BT than voice.. not sure if that's because audio streaming is much more widely used, or if people are having issues with audio streaming with their N4 but not voice.
gilgamesh0 said:
Bump.. help a brother out -- no one using voice over Bluetooth on their N4, or have some perspective on the above?
Seems like a lot more people talking about audio streaming over BT than voice.. not sure if that's because audio streaming is much more widely used, or if people are having issues with audio streaming with their N4 but not voice.
Click to expand...
Click to collapse
Yes I've noticed BT broken when trying to use voice commands on a headset. But what's more troubling is BT sometimes just doesn't work at all. Tap to turn on and it immediately turns off. A reboot fixes the issue but I have to do this every other day it seems. Hoping for either a 4.2.2 or 4.3 patch.
SUTHRNFRIED said:
Yes I've noticed BT broken when trying to use voice commands on a headset. But what's more troubling is BT sometimes just doesn't work at all. Tap to turn on and it immediately turns off. A reboot fixes the issue but I have to do this every other day it seems. Hoping for either a 4.2.2 or 4.3 patch.
Click to expand...
Click to collapse
Thanks Suthrn.. sounds also as though, like me, you never tried voice BT prior to 4.2.1. When you say a reboot fixes the issue, you mean just a simple long-press power off and restart? Or some kind of hard reset?
gilgamesh0 said:
Thanks Suthrn.. sounds also as though, like me, you never tried voice BT prior to 4.2.1. When you say a reboot fixes the issue, you mean just a simple long-press power off and restart? Or some kind of hard reset?
Click to expand...
Click to collapse
Oops, just realized, sounds like you mean the reset resolves this other issue you mention with the BT just immediately turning off again after turning it on.
I haven't seen that problem as yet, but of course there's still time.
Bluetooth works great for me... Syncs 2x faster than my galaxy nexus. Using Motorola s11 HD flex stereo Bluetooth headset. I think these things are at least BT 3.0 but everything about them has been alright. The only problem i have is that music over BT is blown out crackling depending on the app (Pandora for instance) This is supposedly a 4.2 issue and not a hardware one.
Sent from my Nexus 4 using xda premium
Jayrod1980 said:
Bluetooth works great for me... Syncs 2x faster than my galaxy nexus. Using Motorola s11 HD flex stereo Bluetooth headset. I think these things are at least BT 3.0 but everything about them has been alright. The only problem i have is that music over BT is blown out crackling depending on the app (Pandora for instance) This is supposedly a 4.2 issue and not a hardware one.
Click to expand...
Click to collapse
Thanks. But it sounds like yours is another case of just audio streaming to your Bluetooth stereo headphones, not using voice over a Bluetooth voice headset (actually just took a look for the headset model you described, and indeed it appears to be just for streaming output, not for voice input). The problem I'm talking about is specifically with voice input to the phone. In fact, with my Plantronics headset, I've been able to hear the VR prompts coming over from the phone without any obvious problems, it's just my voice input to the phone that appears to be getting munged.
I use plantronics back beat 903+ and have less issues than with my iPhone. I stream audio books and make calls. Voice commands are interpreted way better than on Siri. I had a 1 in 5 shot of it picking up "Call Lissa Lu" the first time. I cannot say it is perfect but I haven't had people complaining of not understanding me on a call.
Sent from my Nexus 4 using xda app-developers app
gilgamesh0 said:
Hi all.
Here's what I'm seeing and what I'm trying to figure out.
On my new Nexus 4, which in other respects seems just fine, voice over Bluetooth is basically unusable. I first tried testing out voice commands for dialing etc., which consistently failed. A friend happened to call while I was doing this, and could barely make out what I was saying (reported it as choppy, digitized etc.).
This is using a Plantronics Discovery 975. Which works fine with my Nexus One, so isn't a faulty headset (I even had my wife's same model headset and tried it also). I don't have any other headsets handy.
This N4 *has* been upgraded to 4.2.1. After searching a bit, I found numerous reports and a couple articles re many BT features, including voice over BT, being broken to a great extent on many devices with 4.2.1 (or earlier, and getting still worse in 4.2.1). Those reports, however, mostly seemed to reference devices other than the N4 (though perhaps only due to its newness & relative scarcity, hard to know).
I then tried the headsets with my wife's Galaxy Nexus, which also had been upgraded to 4.2.1. On that, however, the voice over BT apparently worked fine, or at least much better -- sounded ok, and VR could recognize contacts to be called.
Thus I could at least conclude it isn't just voice over BT simply broken in 4.2.1 everywhere (which would have made things simple.. ), and it isn't simply voice over BT in 4.2.1 with the Discovery 975 either. So add in the Nexus 4.
I've seen many reports of BT streaming audio issues on the N4 with 4.2.1, but little at all about voice, and certainly some successful reports for voice.
So I'm trying to figure out: What is the likelihood that with all of the 4.2.1 Bluetooth troubles, there is a consequent BT software issue on my Nexus 4 when used with this Discovery 975 headset? Vs., what is the likelihood that my specific N4 has some kind of hardware issue with BT?
- How many folks are using voice over BT successfully? Anyone else having issues?
- What version does your N4 have -- 4.2.1, or earlier?
- If you used it *before* an upgrade to 4.2.1, did it work both before and after the upgrade, or did the upgrade introduce issues?
- Anyone specifically using the Plantronics Discovery 975, or another Plantronics?
Basically, I'd really like to avoid the crap shoot of exchanging the phone (BT voice is a critical feature for me), since it seems fine in all other respects, and with all of the manifest BT issues that appear to have been introduced with 4.2.1, that seems like at least a reasonable culprit.
However, if there aren't widespread issues with voice over BT on the N4 with 4.2.1, then it would seem the only way it would be a software issue, would be if it's the combination with my particular Plantronics headset model. Otherwise, I think I'd have to face the possibility of a hw issue. (Bad timing for me with 4.2.1's buggy BT issues, it really obscures the situation. )
Another useful test for me to try might be to revert back to the prior OS version and test with that, but I gather I have to root to do that, not sure if that also voids the warranty.. (hence preventing me from exchanging it if I did ultimately need to).
TIA
Click to expand...
Click to collapse
It might be your phone after all. I've been using BlueAnt Q2 and built-in system in my car - have not noticed any issues before or after 4.2.1 upgrade.
I also have a Plantronics Discovery 975 and have experienced the same choppiness/digitized sound you describe.
This has happened on my N4 with my 975, and my wife's N4 with her 975. We both had Nexus Ones before and the 975s worked perfectly.
I have not had a chance to try the N4 with another bluetooth device, and I did not get a chance to use the 975 with the N4 before upgrading to 4.2.1.
Anyway, you are not alone in your frustration with the sound through the 975...
gilgamesh0 said:
Hi all.
Here's what I'm seeing and what I'm trying to figure out.
On my new Nexus 4, which in other respects seems just fine, voice over Bluetooth is basically unusable. I first tried testing out voice commands for dialing etc., which consistently failed. A friend happened to call while I was doing this, and could barely make out what I was saying (reported it as choppy, digitized etc.).
This is using a Plantronics Discovery 975. Which works fine with my Nexus One, so isn't a faulty headset (I even had my wife's same model headset and tried it also). I don't have any other headsets handy.
This N4 *has* been upgraded to 4.2.1. After searching a bit, I found numerous reports and a couple articles re many BT features, including voice over BT, being broken to a great extent on many devices with 4.2.1 (or earlier, and getting still worse in 4.2.1). Those reports, however, mostly seemed to reference devices other than the N4 (though perhaps only due to its newness & relative scarcity, hard to know).
I then tried the headsets with my wife's Galaxy Nexus, which also had been upgraded to 4.2.1. On that, however, the voice over BT apparently worked fine, or at least much better -- sounded ok, and VR could recognize contacts to be called.
Thus I could at least conclude it isn't just voice over BT simply broken in 4.2.1 everywhere (which would have made things simple.. ), and it isn't simply voice over BT in 4.2.1 with the Discovery 975 either. So add in the Nexus 4.
I've seen many reports of BT streaming audio issues on the N4 with 4.2.1, but little at all about voice, and certainly some successful reports for voice.
So I'm trying to figure out: What is the likelihood that with all of the 4.2.1 Bluetooth troubles, there is a consequent BT software issue on my Nexus 4 when used with this Discovery 975 headset? Vs., what is the likelihood that my specific N4 has some kind of hardware issue with BT?
- How many folks are using voice over BT successfully? Anyone else having issues?
- What version does your N4 have -- 4.2.1, or earlier?
- If you used it *before* an upgrade to 4.2.1, did it work both before and after the upgrade, or did the upgrade introduce issues?
- Anyone specifically using the Plantronics Discovery 975, or another Plantronics?
Basically, I'd really like to avoid the crap shoot of exchanging the phone (BT voice is a critical feature for me), since it seems fine in all other respects, and with all of the manifest BT issues that appear to have been introduced with 4.2.1, that seems like at least a reasonable culprit.
However, if there aren't widespread issues with voice over BT on the N4 with 4.2.1, then it would seem the only way it would be a software issue, would be if it's the combination with my particular Plantronics headset model. Otherwise, I think I'd have to face the possibility of a hw issue. (Bad timing for me with 4.2.1's buggy BT issues, it really obscures the situation. )
Another useful test for me to try might be to revert back to the prior OS version and test with that, but I gather I have to root to do that, not sure if that also voids the warranty.. (hence preventing me from exchanging it if I did ultimately need to).
TIA
Click to expand...
Click to collapse
Parrot MKI 9200 here. Works fine for voice calls... in fact, generally people tell me that it's better than my old GNex. Voice recognition on the parrot works as reliably as on the GNex... If the quality was bad, it certainly wouldn't work.
I read a lot of complaints about the new BT stack in 4.2.x so perhaps this is related to the A2DP issues... audio streaming is definitely poor on the nexus 4. Or perhaps it just doesn't like your headset. Have you tried another?
Daern
Sent from my Nexus 4 using Tapatalk 2
I have noticed that compared to my old Galaxy nexus, the quality of the connection to my Camaro is much much worse. Its a 2012 and a I had the dealership do a software update just to make sure it wasn't the car. Any other phone its crystal clear by my N4 is just horrible.
I just noticed this yesterday in my Mazda 3. Music streams perfectly fine, but I was on a call, and the other party could not understand what I was saying. I tried listening from the other side, and it's really distorted and difficult to hear.
fooznugget said:
I just noticed this yesterday in my Mazda 3. Music streams perfectly fine, but I was on a call, and the other party could not understand what I was saying. I tried listening from the other side, and it's really distorted and difficult to hear.
Click to expand...
Click to collapse
Same. Streaming music is fine. But sound is distorted on calls.
I'm using a Plantronics Voyager Pro and also have the phone connected via Bluetooth to my BMW. I've had calls come in where I was unable to hardly hear what they were saying (horrible sounding audio) and they said the same thing about me. This has happened on both my Plantronics headset (I have two, and it's happened to both) and in my BMW. Just now I got a pair of VIZIO VXTHB100 Stereo Headphones and when I first tried to pair them up the phone only showed the MAC address of the headset and came up with an error when trying to connect it... It's worth noting that I did do a reboot on my phone earlier in the day already to.
I turned bluetooth off and back on (without touching my headset) and POOF it found the headset (showing by name this time) and connected right away.
I really, REALLY, hope this is a software issue that will get patched soon. Coming from my Samsung Galaxy Nexus which was PERFECT and now I'm dealing with this... I feel like it's my Nexus ONE all over again.... I'm honestly concerned with the quality of this phone compared to the Samsung Galaxy Nexus (internals wise). I'd go back to my Samsung GNexus if my woman wasn't using it as an upgrade from her old Nexus S... Another thing I've noticed is that 90% of the time I can't get Google Chat/Google + Video chats to use my bluetooth headset OR Skype to use it either... SOOOO damn annoying.
BTW, the sound quality on the VIZIO Stereo Bluetooth headset is okay. Not as good as my gaming headset, but hey, they will do the job well and I can answer a call with them on if need be to.
-Kaz
Thanks for all the replies so far (especially the guy with the also-failing Discovery 975). I had already started to lean toward deeming it a likely software issue, given a) all the apparent general BT issues introduced with 4.2/4.2.1 and, b) I finally was able to try streaming Bluetooth audio, and that worked with no obvious issues. I would think that there wouldn't be anything physically about the BT radio or the way it is situated that would lead it to fail for just voice input but not output, no? I don't really know anything about the hw.
It seems more likely at this point that with the current BT software there are compatibility issues with various devices, but there is also a platform dependency as well (hence the Discovery 975 working ok on my wife's Galaxy Nexus with 4.2.1, but not my N4).
Or else, if it is a hw issue, it sounds like one present on a number of Nexus 4s, given the responses so far.
Of course, if Google would say something about it, we'd not be in the dark. This is a pretty critical feature for a lot of folks. Unfortunately, I've come to be surprised when they announce anything at all. Bugs happen, even severe ones, but it would help a lot to just know what is going on.
I've used seinhessier vmx 100 which worked surprisingly well, as on my old phone I almost threw it out as no one understood me and I could hardly hear them. Now they don't even notice! I'm using stock, not rooted 4.2.1.
Sent from my Nexus 4 using xda premium
jholt1 said:
I've used seinhessier vmx 100 which worked surprisingly well, as on my old phone I almost threw it out as no one understood me and I could hardly hear them. Now they don't even notice! I'm using stock, not rooted 4.2.1.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I am using a Plantronics Voyager and i too have some issues. The problem is hearing what other are saying as most sound distorted and to loud. I dont know what to do and the headset worked perfect with my old Galaxy S2.
Similar poor audio when using LG Bluetooth headset which worked great with iPhone 4s and macbook pro for calls.
Has anyone tried a custom rom, say cyanogen 10 based or aokp?
Wondering if the stacks in the custom roms are any different than stock.
tr2ride said:
Similar poor audio when using LG Bluetooth headset which worked great with iPhone 4s and macbook pro for calls.
Has anyone tried a custom rom, say cyanogen 10 based or aokp?
Wondering if the stacks in the custom roms are any different than stock.
Click to expand...
Click to collapse
I would like to know that as well. Or any other fixes/tricks for that matter...
Is there any way to fix the bluetooth audio quality other than switching to a CM-based ROM?
My old phone over bluetooth sounds fine. My S4 via a wired connection sounds fine. My S4 over bluetooth sounds like everything was sampled at 32 kHz. All other equipment is the same, so I'm relatively sure it's a bluetooth-specific issue. My girlfriend's S4 does the same thing.
So, any fixes? I'd really like to avoid switching to an aftermarket ROM right now.
Edit: L337 on AT&T
Tourney3p0 said:
Is there any way to fix the bluetooth audio quality other than switching to a CM-based ROM?
My old phone over bluetooth sounds fine. My S4 via a wired connection sounds fine. My S4 over bluetooth sounds like everything was sampled at 32 kHz. All other equipment is the same, so I'm relatively sure it's a bluetooth-specific issue. My girlfriend's S4 does the same thing.
So, any fixes? I'd really like to avoid switching to an aftermarket ROM right now.
Click to expand...
Click to collapse
Random guess: Could this issue be caused by the adaptive sound feature? I'm not a true audiophile, but I haven't noticed a problem through my receiver in the car or at home.
Try playing something with cymbals and a lot of treble. Turn the volume up a bit higher than normal while still maintaining a reasonable level. The cymbals sound like someone is smacking a plastic grocery bag with a stick instead of being crisp and clean like they should be. I can then disconnect the S4, connect my old phone, and play the same mp3 without any sound distortion. Or I can play the same mp3 from the S4 via aux and it sounds fine.
Try it on both bluetooth and aux. If you truly don't notice a difference, I guess it must just be my phone. If it does do it however, you definitely don't need to be an audiophile to hear it.
My old phone had the exact same problem until I moved to JB on a CM build. The problem there is well-documented as existing on the S3 (try looking up bitpool settings), but I kind of figured they would have fixed it by now. I'm coming from the world of HTC, so I was hoping there is a fix for Samsung.
Sorry to revive this thread, but I have an update.
My car has built-in bluetooth for phone only, so no a2dp. I have a third-party bluetooth adapter that I'm using for music.
I've found that when both of these are connected, the audio quality (especially on trebles and guitars with distortion) is absolutely terrible. That was the point of my original post. Since then, I've determined that this happens ONLY when I am paired with both my car and my third-party bluetooth. I can actually pair and unpair from my car in real time and hear the audio quality immediately get better/worse. The quality gets worse immediately when it pairs, even if the car bluetooth is not in use (but still connected).
I've verified this is the case with both my phone and my girlfriend's S4. Can anyone with such a setup verify this does or does not happen for them? I'm thinking this is a bug with the bluetooth stack, and it'd be nice if it could be fixed. If anyone can try pairing to two different devices and confirm my problem, I'll start a bug report with Samsung. Otherwise I'll try another bluetooth adapter for a2dp.