I've been having this issue for a while. It seems that no rom beyond 2.2 can route calls through the car speakers correctly. I've finally gotten tired of waiting and ordered an auxiliary plug with a mic from amazon so I can move on to new roms, but now the rom I'm using (simply honey, the 2.2.1 version) won't even let me hear the other person talk.
Does anyone know a workaround to get the calls to route correctly through the speakers? I don't understand why any music app I have doesn't have this problem, only voice calls.
Many thanks for any help.
Sent from my GT-I9000 using XDA App
Is your issue something like this?
http://forum.xda-developers.com/showthread.php?t=842059
Or is it with bluetooth? I know I have a Jabra Cruiser and i can hear music and calls just fine through my car speakers. Of course thats with bluetooth. Good luck!
The wired headset never worked properly in 2.2.1. It has to do with the mapping of the contacts on the plug itself. Most of our 2.2.1 ports are sourced from the European i9000 build, which while it is a Galaxy S phone, is different enough that some things dont work, like your wired headset. We never did find a fix for it when I was playing with 2.2.1, accept to use a bluetooth device instead of a wired headset.
On a side note, in my humble experience, KB5 based 2.2 works much better on our Vibrants than any 2.2.1 build ever did, and the headset works.
Sent from my ZenDroid, meditating on the XDA App
Thanks for the replies, I managed to get it fixed!
Sent from my GT-I9000 using XDA App
Related
So I'm surprised that Cyanogen is the only ROM to date that actually addresses the A2DP audio quality problem with the Vibrant. By default the stock kernels lock in the bitpool setting at 32 when it can be set as high as 54. As a result the 'highs' sound distorted and tinny as if I'm listening to music streaming through RealPlayer circa 1997. Why more people aren't complaining about this is a mystery but there are a lot of people that aren't happy.
To the developers, is this bitpool setting in Bluez something thats rolled into the kernel when compiling or is it something that can be easily changed? Possibly a configuration file? I've googled this issue to death over the last three months hoping for a solution to pop up, I've read up on Bluez but the documentation is poor. Does anyone have more information or can point me in the right direction to solving this myself? Having to wire up my phone every morning for music is driving me nuts.
Any help would be greatly appreciated!
I couldn't agree more man. I am going nuts over the horrible quality. I think it hasn't been addressed as much because not as many people have bluetooth stereo headphones or bluetooth adapters in their cars. Cross your fingers.
Sent from my SGH-T959 using XDA App
Hmm! I was gonna start using my s9 wireless headphones. Now I'm skeered!
Sent from my GT-I9000 using XDA App
Seriously, no one knows anything about the bluetooth stack?
I can't believe that no one has said anything about this being fixed. There has to be a way of manually going into the root directory and adjusting the bitpool information that you're referring to. The tinniness is killing me man!
Weird, but I don't have any sound quality issues over BT.
Couldn't agree more OP. BT is seriously jacked on these. It works, but not like it should quality wise.
Ya, the BT streaming audio doesnt sound nearly as good as wired. Hopefully someone more knowledgeable regarding the subject could chime in, I know Supercurio did a lot of reverse engineering for sound quality, but I dont know if he worked on A2DP
Devs moved it from Development to Q&A... not sure I agree with that as I don't think this is a setting as much as its a fundamental portion of the kernel and needs to be rolled into a released ROM.
edit:
I just noticed theses guys seem really close....
http://forum.xda-developers.com/showthread.php?t=708685&page=3
Still no one cares? Can anyone help!
There's a whole slew of complaints here:
http://code.google.com/p/android/issues/detail?id=9888
Bump...
Sent from my SGH-T959 using XDA App
Bunp...Bump...
Sent from my SGH-T959 using XDA App
Just got my new bt streaming head unit for Xmas and couldn't be more disappointed. I'm having the exact same issue and am also frustrated at the lack of interest in the problem.
I'm not a Dev BY any means, but I can sometimes hack and slash my way through stuff like code. If cm fixed it,and his source is available, I don't understand why more kernel devs aren't including it in their kernels. Do you think if someone like netarchy asked cyanogen what he did for that, the cyanogen guys would share?
I want to do something to fix this for all android devices, but I don't know where to start other than start pming devs and hope they listen.
I'm baffled at how few people notice or care that the bluetooth audio is rubbish on essentially most new android handsets. They're multimedia hubs and can do most everything, and yet the audio doesn't work properly. I'm really discouraged at this point. I've had this handicapped phone for 6 months now hoping someone would fix this eventually but apparently I was naive. I'm tempted to recommission my 2.5 year old G1 to take care of audio duty in my car since modern Android builds aren't up to the task.
I'm gonna be looking into it for my next kernel =] I didnt know this was an issue because I really dont use BT......are you guys wanting to use BT for music? is that what this is? Cause honestly music stream over BT is like rubbing you D with sand paper and saying it feels good (IMHO). BT audio compression reduces the audio quality to much for my taste, but I'll fix it anyways =P
Hey ECOTOX, does the BT audio control function reside in the kernel? Or the ROM? My fwd/back buttons aren't working on my headset.
Sent from my SGH-T959 using XDA Premium App
FReQ Z said:
Hey ECOTOX, does the BT audio control function reside in the kernel? Or the ROM? My fwd/back buttons aren't working on my headset.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
thats a headset thing, the phone shouldnt control that
Worked with Bionix and Simply Galaxy. Doesn't work with Simply Honey or Project V. Hmmm... I'll do some troubleshooting.
Sent from my SGH-T959 using XDA Premium App
worked in froyo and not gb then?
Sent from my SGH-T959 using Tapatalk
I found out that certain combinations of ROMS and Kernels work better with my CAR Bluetooth then other combinations. For instance CM6 is not working perfect and is uncertain to reconnect to my Car system. On the other hand most Sense ROMS work better with my Car system.
So in this project I wanna track down first which components have influence on the bluetooth stack, and more important which specific parts of the kernel, software and other things are related.
This to improve the BT Car system of at least my Scenic but I have the feeling more Car systems have issues.
Please if you have info about this put it in this treath so we can make it better.
Nice initiative. My BT system in my car works flawlessly with WinMo, but as soon as I connect my nexus, my speakers begin shrieking like all hell breaks loose. Also, My Nexus the seems to lock up and I need to pull the battery for all misery to end.
LOL.
That was the first time I connected the bugger, so I wasprobably still running Eclair when I tried it.
6.1.1 works well for me, both bluetooth calling and a2dp.
Theres a little fuzziness going on when nothing is playing, like white noise, but that's pretty much my only problem. No wait, there is one more thing actually, every now and then while music is playing it'll skip more or less a second
Just to add... I have to repair and disable/enable by every time I get in the car or the sound will drop out every 15-30s on any rom that uses froyo. GB seems to help where I only need to disable / enable bt. Kenwood x-993 with parrot bt. Using latest bt firmware.
Sent from my Nexus One using XDA App
PhantomRampage said:
Theres a little fuzziness going on when nothing is playing, like white noise, but that's pretty much my only problem. No wait, there is one more thing actually, every now and then while music is playing it'll skip more or less a second
Click to expand...
Click to collapse
This happens to me too once every three or four songs, but it's such a small thing it doesn't bother me much. On the other hand, for the short while I was using MIUI, I felt it was happening much less, but I may have been imagining that
Heres my setup, and it works flawlessly every time i start the car.
Car Deck: JVC KD-R900 (Using the small bluetooth adapter that came with the unit mounted in the back USB port)
ROM: Enomthers TheOfficial Nexus1 v2.14.3
Kernel: 2.6.32.35-TheOfficial-AudioMOD-720p
Radio: 32.41.00.32U_5.08.00.04
OS Version: 2.2.1
Like i said earlier i have no problems with the audio quality or connecting to my unit. As soon as i turn my Bluetooth on it connects within about a minute.
Calling quality is good, audio quality is good and AVRCP works also (play/pause/next/prev)
If you need anymore info just let me know.
Its good to see there is some reaction on the start of this.....
My goal is to achieve and to find out which components are involved in the Bluetooth experience:
F.I. :
* Kernel modules and libs
* Application in the rom to actually making the connection
* Bluez configuration and settings
I have done some searching but found that even with the same Bluez settings there can be a difference between some roms in combination with kernel.
jscat1 said:
Just to add... I have to repair and disable/enable by every time I get in the car or the sound will drop out every 15-30s on any rom that uses froyo. GB seems to help where I only need to disable / enable bt. Kenwood x-993 with parrot bt. Using latest bt firmware.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I have the same issue on my Kenwood system.
jscat1 said:
Just to add... I have to repair and disable/enable by every time I get in the car or the sound will drop out every 15-30s on any rom that uses froyo. GB seems to help where I only need to disable / enable bt. Kenwood x-993 with parrot bt. Using latest bt firmware.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Me too, same model. I've updated the firmware on the X993 and it seemed to help.
elfblackdeath said:
I have the same issue on my Kenwood system.
Click to expand...
Click to collapse
Same here on my DDX-812. Almost everything "works", I just get the drop-out when streaming music if it's not a fresh pairing.
The bluez stack was updated with Gingerbread...I'm hoping against hope that that fixes some things.
i have to use a no-audio-boost kernel with my jabra headset, otherwise the call quality is abysmal. lots of metallic clicking and other strange effects going on.
but i have seen no differences in the overall connection stability otherwise.
hmm i have a problem with my car dock and bluetooth i think. when using the navigation the voice plays via the phones speaker not the dock speaker. is this similar to the problem in the 1st post? if so, would love a fix!
I'm on CyanogenMod Nightlies with the included Kernel and have a Kenwood DDX8024BT with built in bluetooth. It connects up perfectly when I turn the ignition on and seems fine when in call. I don't use the A2DP much but when I have I've not had any problems.
Slightly OT, the only problem I have is with reading contacts from the phone. I have two phones paired. I usually have the Nexus connected but occasionally switch to my work phone (a Tocco Lite). At some point it took the contacts from my work phone and then wouldn't redownload the Nexus contacts when it was reconnected. It's now done it at some point but there's a handful of contacts that still won't transfer no matter what I try.
On a side note, I have a Clarion CZ500 rig in my car, and the N1 is incompatible with the microphone boost firmwares they offer on their site. All I hear is crackling when I try to make or receive a call.
What's odd is that the HTC Desire works fine with those firmware. Even Blackberry Pearl.
I ordered the N1 dock on eBay. I guess I'll see if the dock can handle the firmware.
i have a n1 and im still running cm 5.0.8 with android 2.1
my phone pairs with my car without any problems and i am able to talk to people and whatnot. Now as far as music, i use a blackberry music gateway bluetooth device that i plug into my car's 3.5mm jack and then i pair that device with my phones bluetooth. It pretty much connects automatically all the time and sound quality is awsome however as someone mentioned earlier in this thread, i get the occasional 1 second skip every so often. Does anyone have any idea whats causing this and how can i fix it? It is extremely annoying!!! I paired the blackberry gateway device with my gf's mytouch and there was no such problem, which leads me to believe that the problem is in my n1 :/
My $02: I cannot use a2dp and hands free at the same time. If both are connected the the a2dp drops out all the time.
This is not an issue with my HD7.
A workaround would be awesome.
Sent from my Nexus One using XDA App
I suspect the main difference, hardware combinations aside, between Stock/CM and Sense roms is that they use different bluetooth stacks.
Differences in the bluetooth stack that have caused issue for the FM radio on stock roms, an issues for bluetooth file transfer on Sense roms as far as I know.
Like iphone fanboys would say: fragmentation
On a related note the behavior of my N1 with the Parrot handsfree has vastly improved in GB.
i have the kensington liquidaux bt adapter in the car and cm7 rc4 with stock kernel skipped constantly. rc2 was better, but still unbearable.
i am currently on intersectraven's 4/3/2011 kernel and from limited use, has not skipped on me yet.
have people tried bt music streaming with other kernels with cm7 rc4? wildmonk? pershoot? etc.. thanks.
Try CM7 Issue 3233 fix
d1mitrov said:
It pretty much connects automatically all the time and sound quality is awsome however as someone mentioned earlier in this thread, i get the occasional 1 second skip every so often. Does anyone have any idea whats causing this and how can i fix it? It is extremely annoying!!!
Click to expand...
Click to collapse
Can you try the fix in Issue #3233 on the CM7 bug tracker? http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
scotte9999 said:
Can you try the fix in Issue #3233 on the CM7 bug tracker? http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
Click to expand...
Click to collapse
i think thats exactly what my problem is, when the phone is connected to the car and the music gateway is connected as well i get the intermittent connection and it skips every so often but if i disconnect the phone part then the music never skips...however im not on CM7 so i dont know if that fix applies to me and i dont know how to begin changing those settings
I have one major issue with the thunderbolt and it is 100% a software issue. I believe ASOP roms or desensed roms may fix the issue and would like someone to verify before I purchase.
The issue is as follows:
* Plug in Normal headphones or aux cable without a inline mic and attempt to make a phone call or receive one....the other side cannot hear you till you either put them on speakerphone or unplug your headset/aux cable.
* All other Mic required application will still work Google V search, Skype, etc, just the built in dialer doesn't.
What I'm interested in:
* People with custom roms/kernels testing above and letting me know if the Mic isn't getting muted for them when they "Plug in Normal headphones or aux cable without a inline mic and attempt to make a phone call or receive one"
* What Rom/kernels you are using.
/bump ten char
I've experienced the same thing on various roms, not sure of a fix. Happens on das BAMF, tesla, and the pre-alpha CM7
I bought my TB from my buddy specifically because that was a #1 requirement for him. Bluetooth stereo with hands free and A2DP for me
i've heard of this issue on non-sense roms, but didn't have the stock rom on the phone long enough to test this...
It's due to the noise cancellation stuff in the device...
Sent from my ADR6400L using XDA App
adrynalyne said:
It's due to the noise cancellation stuff in the device...
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Any way around it?
I've been using the Shure MPA-3C adapter for several phones now. Worked great with my TP2 and DX. You can use any headphones you like and since it provides the mic there is no hacking required.
Www dot shure dot com/americas/products/earphones-headphones/music-mobile/mpa-music-phone-adapter
I heard that HTC is aware of the issue and is working on a fix. (i think i read it in a forum on android central). Would be nice to be able to use the regular mic with headphones.
Hi all,
I am using my gs2 with my Sony headunit (bt2600) in my car. It's great for calls but the quality while playing music is poor. It seems to always be slightly distorted and crackles at any volume combination on the phone and headunit. It has no quality problems using an auxiliary cable from the headphone port.
Has anyone else had this problem and know of a fix?
I'm using the standard unrooted XYKI4 rom but will happily change if another rom would solve it.
Thanks
This is the famous A2DP problem. No solution has been found until now and Samsung hasn't done anything either.
So you can use CM7 or MIUI where this problem has been fixed, or else wait for a stable ICS...
Ah ok, thanks for the reply. I'll need to decide whether to wait for Samsung or take the plunge and install a custom rom.
It's been fixed on the nexus. So there is a chance it shall be fine on ICS. I've battled this issue on my Sony headunit but cm7 and MIUI works a treat. Take the plunge but be careful.
Sent from my GT-I9100 using xda premium
My girlfriend has a GS2 with a Pioneer headunit without any problems. I have my GS2 connected to my Toyota in-car satnav headunit and also there bt audio sounds fine without any distortion.
Btw I am on 2.3.6 (KI4) stock with Siyah 2.6.3 kernel.
Sent from my GT-I9100 using XDA App
I just got a BT2800 and don't have any issues with the sound. It is better with the BT volume from the phone turned down a bit though.
I'm using checkrom v4
I tried ICS myself, and the problem has indeed been fixed. So that's some good news.
If I remember correctly, it was a problem in Gingerbread, Google fixed it later on but Samsung never bothered to apply that particular fix - at least up to the XWKK5 firmware.
A couple of relevant discussion topics here on XDA:
http://forum.xda-developers.com/showthread.php?t=1187488
http://forum.xda-developers.com/showthread.php?t=708685
After installing and replacing a few Liquid ICS roms (liquid0624, jester & twistedumbrella), all of them seem to one common problem that I can not solve...Making a phone call with a bluetooth headset (Jawbone ERA & BlueAnt Q2) is very difficult. Here is the scenario...I pair the headset, when I then try to place a call, the phone acts as if it has connected, however, there is no sound at either end of the call. I go through this maybe two or three times before the call is 'connected'. If i try the call with out the headset...no problem Any thoughts??? Thank you for the help...
What kernel is your ROM using? Try the latest imoseyon AOSP kernel if you are using another. This fixed my issues.
Sent from my ADR6400L using xda premium
What Next...??
Currently, I am using twistedumbrella's Liquid ICS/CM9 rom...very nice.
It took my Thunderbolt to Android 4.0.4 and uses Kernel version: 2.6.35.14-TwistedMecha-v1.0.6+...
Is this the most up-to-date kernel for an ICS rom or is there another kernel that is more reliable..
What are my options??
Ty
ghdroiduser
Actually my bad. Unless imoseyen updated his kernels his doesn't support ICS. When I had ICS I don't remember what I did to get BT working but I do remember it was kernel related. I'll see if I can go back and see what it was, unless someone comments before me.
Sent from my ADR6400L using xda premium
ghdroiduser said:
After installing and replacing a few Liquid ICS roms (liquid0624, jester & twistedumbrella), all of them seem to one common problem that I can not solve...Making a phone call with a bluetooth headset (Jawbone ERA & BlueAnt Q2) is very difficult. Here is the scenario...I pair the headset, when I then try to place a call, the phone acts as if it has connected, however, there is no sound at either end of the call. I go through this maybe two or three times before the call is 'connected'. If i try the call with out the headset...no problem Any thoughts??? Thank you for the help...
Click to expand...
Click to collapse
This is a known intermittent problem, and I have experienced it too. There is a very easy workaround. While in the call screen, switch from bluetooth to handset or speaker, then back to bluetooth. Then you will hear the other person and vice versa. If you do this while the call is ringing, then the other person won't experience dead air at all.