Database Develop

Bluetooth Headset Audio

Hello all
I recently put 4.2.11.1 on my G1. Now when I pair my headset with the phone. The audio is still transfered though my phone. Is this a known issue? is there a fix?
Tech Specs
Handset: G1 w/Cyanogen 4.2.11.1
Headset: Samsung WEP470
The headset worked fine with stock 1.6
The headset appears to pair fine, even verified the bluetooth 'button' is selected while in a call. Still audio goes through the handset and not the headset.
This really is my only issue I love cyanogen so far and hope that the Nexus One is cracked fairly soon after release.

I have the exact same issue with a parrot ck2100-bluetooth hansfree, also running latest cyanogen

I've had this issue and other Bluetooth audio problems under the last several CM releases (See http://code.google.com/p/cyanogenmod/issues/detail?id=819). When audio fails to go through the headset as you describe, turning the headset off and then on again often fixes it. If that doesn't help, then turning the headset off, toggling Bluetooth off and then on, and then turning on the headset usually works.

hrmm, hope this can get fixed I may have to abandon Cyanogen. I have to field call via bluetooth when I work from home.

usually this happens once a week for my bluetooth if i keep toggling BT on and off several times (usually do it if i forget my BT headset). easy fix. not a serious problem with me.
like the person above said: just turn toggle BT off then on, it should connect fine. if not, what i do is go through the settings and unpair them and pair, it should connect to the phone's audio. rinse and repeat.
not a serious bug that should keep anyone away from a certain rom... especially Cyans

Yall in the wrong forum ppl
If its an issue concerning Cy's rom go in his thread n follow the link to submite the issue.
If u trying to solve the problem go in Q&A and ask there or CY's thread.
This has nothing to do with development.

moved to Q&A

I am also having this issue.
I am having a parot c3100 and it pairs fine. But the sound is send to my phone instead of over my car audio system.
I tried bluetooth+headphone fix, but that doesn't help either.
It looks like every cyanogen (based) rom does have this issue ....
Does anybody have other ideas to get it fixed ?

Bluetooth sounds bad

Hey all,
I have Froyo 2.2 on my N1...anyone know why my bluetooth headset crackles and is really fuzzy sounding? Sounds like they are underwater sometime...I even tried a new bluetooth headset with same problem...any ideas? Thanks.

rayman121985 said:
Hey all,
I have Froyo 2.2 on my N1...anyone know why my bluetooth headset crackles and is really fuzzy sounding? Sounds like they are underwater sometime...I even tried a new bluetooth headset with same problem...any ideas? Thanks.
Click to expand...
Click to collapse
which FroYo ROM, and which kernel.

mine does the exact same, its not just you its probably a froyo issue.

ok so i was bored and did some tests, it seems it only happens to me when trying to send audio via bluetooth when playing a flash video, reg music and videos are no problem.

I also have same problem, but on CM 5.0.X (Android 2.1). I tried Motorola S9-HD (stereo) and Nokia HS-56W (mono). Every time connect the headset and the phone is very close (20-30 cm), the sound is fine, but as soon as the phone is to push further, the sound is choppy and stutters. And this happens on any headset.

is WiFi on or off?
WiFi and bluetooth operate on same frequency band and can cause issues.

i have wi-fi on and bluetooth on.

switch WiFi off and try.

arkavat said:
switch WiFi off and try.
Click to expand...
Click to collapse
I switched off Wi-Fi and connect Motorola S9-HD and it really workes. A will try today use more and write late about it.

Same problem here with Froyo.
I turned Wifi off and the sound problems went away.
I think is a hardware problem or design problem because I used to use the same headset (Motorola H-710) with an iPhone and never had this problem even with Wifi switched on.
Would be any way to get rid of this problem?, it really bothers me to turn off the Wifi every time I get a phone call.
Thanks

its a problem with flash, not bluetooth, adobe should fix it soon

Thank you for the suggestion I will be sure to try that tomorrow!
I have kernal 2.6.32.9-27220-g328f560 android build apa26 #1
Build number is frf50
I hear this is a test version of Froyo anyway...I don't think the real Froyo has been released yet? So maybe it will be fixed...thank you.

After two days of tests, with switched off Wi-Fi, it turned out that the problem does not disappear completely. Correctly identify the reason for failed. Since stuttering occurred on different songs (that is, perhaps, that stuttering is dependent on the bitrate), I sometimes felt that the problem with lowering the frequency of the processor in sleep mode, and it is not enough to encode mp3 and transfer data via Bluetooth.

Still bad with OTA
I got the froyo OTA for my stock N1 yesterday morning.
I can confirm that the distorted sound is present on the phone application only when wifi is turned on and you are using bluetooth. At first I thought it was only when wifi was on but not connected but it appears that you can get the distortion on a phone call whenever wifi is turned on.
All entertainment application seem to work fine with my A2DP bluetooth. Again it only seems to be bluetooth phone calls and wifi turned on. Believe me this is bad enough. This didn't happen on 2.1 and if it weren't so much hassle I'd probably go back.
Hopefully someone will come up with a workaround that will allow bluetooth calls and wifi turned on at the same time. Gees, if it weren't so basic

This just drives me nuts that Google makes major changes to parts of the OS, then doesn't think to actually TEST everything they changed. This would easily been detected if they actually tried it out. Duh.

I have the FRF91 update and all the blutooth distortions are GONE.

Blueman101 said:
I have the FRF91 update and all the blutooth distortions are GONE.
Click to expand...
Click to collapse
I updated from stock via the OTA to FRF91 and thats actually when the distortions showed up on mine? Well its good to know that there is hope but now I am wondering what possibly may be different between mine and yours?
Can anyone else tell us how their bluetooth is doing on FRF91?

Does anyone think a froyo factory data reset is worth trying?

Issue linking LG Thrill to my car Bluetooth

I Drive BMW 328XI and for some reason when i pair the car with my LG Thrill, i lose the phone signal and the bluetooth disconnects for about 10 seconds then the ATT signal comes back on the phone then about 10 seconds later the phone pairs again for about 10 seconds and then the whole cycle all over again, and it will stay on for hours ..
no luck looking up anything online, i did find few ppl have issues on BMW and Audi cars with bluetooth, but nothing like my case tho!
any ideas or hints other than pair and un-pair the phone and deleting the phone profile from the car .. cuz i did that over 10 times and still no go!
Thank You!

!!!
anyone !!! ?? !!!

Sounds like an incompatibility issue between your car and the phone. I've seen issues with some of the phones and vehicles at my dealership (not BMW) that are almost exactly what you are describing. There won't be a fix unless the dealer (BMW) or the phone manufacturer comes up with an update. Hopefully Gingerbread will help you out.

Tried Thriller? I had bt issues with my headset dropping and reconnecting on its own on the stock rom. Haven't had an issue since I flashed Thriller.
Sent from my LG Thrill Faux G

Gr8Danes said:
Sounds like an incompatibility issue between your car and the phone. I've seen issues with some of the phones and vehicles at my dealership (not BMW) that are almost exactly what you are describing. There won't be a fix unless the dealer (BMW) or the phone manufacturer comes up with an update. Hopefully Gingerbread will help you out.
Click to expand...
Click to collapse
thats true .. i looked up everywhere and it said the same thing online, i have to wait most likely for the dealer to issue and update.
i even tried my trill on a rented car last weekend ( Camero RS 2011 ) and it was working fine.
so its the Car now, im sure.

quarlow said:
Tried Thriller? I had bt issues with my headset dropping and reconnecting on its own on the stock rom. Haven't had an issue since I flashed Thriller.
Sent from my LG Thrill Faux G
Click to expand...
Click to collapse
i had the same issue on
Stock
Root
Triller
i tried on every case and still the same issue!

moe87 said:
thats true .. i looked up everywhere and it said the same thing online, i have to wait most likely for the dealer to issue and update.
i even tried my trill on a rented car last weekend ( Camero RS 2011 ) and it was working fine.
so its the Car now, im sure.
Click to expand...
Click to collapse
Yea, it kinda sucks. I wish the car manufacturers would be more on top of these things.

My problem with my setup is that the Thrill's AVRCP is still at version 1.0 and only supports basic music streaming. It doesn't even support metadata. My 2 year old Tilt2 supports that. I wonder if custom ROM can fix that. iPhone updated the AVRCP from 1.0 to 1.4 with iOS5

[Q] Does anybody use bluetooth in their car?

I flashed Thriller before being able to test the bluetooth on the stock rom, but I've noticed when I'm connected to my Kenwood Deck's bluetooth in my car it's really hard to understand people half the time, their voices just have a staticy distorted noise.
I'm unsure if it's my phone, the rom, or just something I need to change in the settings. There's the possibility it's my car deck but I never had these problems with my previous phone on bluetooth.

Why don't you flash to stock, see if it makes a difference.
Sent from my LG-P925 using XDA App

Bluetooth issues are the reason my signature doesn't say "Sent from my LG Thrill Faux G" anymore.
I could never find a Bluetooth fix that lasted longer than a week. Stock or Thriller. Doomed Froyo was after I left, but its based on Thriller so I doubt its different.
Sent from my Galaxy S II (i777)

Ronacarino said:
Why don't you flash to stock, see if it makes a difference.
Sent from my LG-P925 using XDA App
Click to expand...
Click to collapse
I would but I don't wanna erase everything and start over again. This is my first Android phone so I'm gonna ask a noob-like question here, but is there a way I can backup my phone as it is right now, flash AT&T stock, then flash Thriller again and restore the backup?
quarlow said:
Bluetooth issues are the reason my signature doesn't say "Sent from my LG Thrill Faux G" anymore.
I could never find a Bluetooth fix that lasted longer than a week. Stock or Thriller. Doomed Froyo was after I left, but its based on Thriller so I doubt its different.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
So your bluetooth also sounds distorted like mine? Are you using it over car speakers or a earpiece?
And it's still not fixed yet for you?

You can make a Nandroid back up in CWM, it will backup your entire phone, Apps, settings, everything. Then you can restore in CWM.
I wasn't having that specific problem, but remember a ton of posts about car Bluetooth issues. They never found fixes.
My issue was with a stereo Bluetooth headset. From what I understand they (stereo headsets and the car audio) both use A2DP to transfer data. My headset would drop its connection, and button presses no longer registered. If I was listening to music and a call came in, even if I didn't answer, I would lose the media connection. I would have to turn off the headset, turn off Bluetooth on the phone (sometimes at this point my phone would freeze and require a battery pull), then turn Bluetooth back on, and finally my headset back on.
My phone did this on stock, then I flashed Thriller and it stopped ... for a week. I reflashed Thriller and got another week.
This was the point when gtg bounced, and I had 3 days to exchange my Thrill. I had to choose: warranty swap the Thrill and risk issues on the new one (as I was not the only one with that issue) or swap for the Galaxy S II.
I have no doubt the Gingerbread update will fix this, plus battery issues. But, the update that was promised in October for the unbranded version was pushed to December, and the ATT version has no estimate what so ever.
If you have time to return for another device I say jump. If not I would keep getting warranty replacements through att. If enough come back with issues that might give some pressure to get the GB update pushed.
Sent from my Galaxy S II (i777)

I love this feature of clockwork. So much better than the methods of flashing roms on my WM phones back in the day.
I actually ended up testing a bluetooth call on a friend's LG Thrill unrooted with the att rom still on it, and the crappy distorted bluetooth was there on his as well! Theres a possibility its a compatibility issue with my deck and this type of bluetooth but im not sure what it is yet..

Bluetooth curiosities?

I didn't want to bog down any of the various ROM threads with this, but I've noticed some odd behavior when pairing my D4 to my JVC head unit.
With stock Moto ICS and Eclipse 1.3.2 (still ICS), when paired to the HU, I can voice dial and control Pandora. I can sort-of control Google Music, but it won't display the ID3 tag info for any of the music, and although I can skip tracks it never recognizes anything but the player being stopped.
Now, if I go to Hashcode's WIP unofficial CM10 port, the HU control of GMusic works completely (as does all the Pandora control). I get ID3 tags, it recognizes when the player is stopped, playing, paused, etc. Of course, the current state of the CM10 port has the same BT issues with the phone side of things that the D3 had early in its development.
So now I'm wondering why there's the difference with the GMusic control/ID3 info. Does anyone know if it's something in the ICS/JB framework, or is it something related to the BT stack? Or perhaps something else entirely?
edit: So it turns out stock ROMs from pretty much every manufacturer (maybe all of them) do not support AVRCP 1.3+, but CyanogenMod does. I'm currently loading Hashcode's stock CM9 to see how it fares.
edit 2: Apparently CM9 has the same BT phone issues as CM10, I hadn't realized that. I guess I'm stuck with stock/Eclipse with no tag info until CM10 matures a bit more.

It is amazing just how many problems that this Droid 4 has when it comes to Bluetooth, and everything else. I don't understand how they could release these phones with so many issues. I see it more of a false advertising deal that just goes unchecked. I have major issues with bluetooth, if I get call waiting it resets my bluetooth connection (to where I hear my BT headset replay its boot up music). Half the time I have to pair the headset, then turn off the BT section and then turn it on again just for it to work. I am also constantly repairing the headsets as well. My two motorcycle headsets also also not happy and do not play well with the Droid 4. These headsets all seem to work fine with my older phones, T-Mobile G1, G2, G2x, and my Acer Iconia A500 tablet as well.
Here are my Headsets:
Jawbone Icon(Current Edition sold at Costco)
Parrot SK4000
Cardo Scala Rider FM
Not sure if my list helps any with research going forward, but it is something.
Tom

Yeah, BT performance is all over the place between Moto-stock, stock-ish Eclipse/mybearfish, and CM9/10.
I noticed while driving around today that in addition to everything I mentioned already, Moto-stock will tell the head unit when I get a text message, but stock-ish Eclipse/mybearfish doesn't. IIRC CM10 wouldn't do it either, but that's not all that surprising given its alpha state now.
I'm at a point now where I might finally be willing to give up the HW keyboard and just get a GNex in a month or two after Google announces whatever the hell is going on with the next Nexus phone(s).

Eh, BT works flawlessly for me. If you aren't stock, you shouldn't complain about BT because it probably isn't Motorola's fault.
If you are stock, that try a factory reset (sorry ), and if it still doesn't work, get a replacement 'cause your stuff is broken (just make sure it isn't your headset first!)

Except it doesn't work "flawlessly" because Motorola didn't put in support for anything newer than AVRCP 1.0. No amount of resets and replacements will change that.

I've only rooted, so it is not that big of a deal. Still is it that hard to upgrade that bluetooth section to something newer? This was supposed to be their latest hardware keyboard phone.
Sent from my DROID4 using xda app-developers app