Related
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
My droid would use whatever BT headset (stereo or not) for the phone when my headphone jack was also in use (to use car stereo) for audiobook player.
I have new Fascinate and I swear it did the same until I rooted it. Regardless, it will be close to a deal breaker if I cannot find a solution to this.
Even if the headset indicator is ON, the sound still goes to the headphone jack, RIDICULOUS
In my opinion, plugging into headphone jack should only take over media type output (music, audiobook player, video) and LEAVE PHONE ON BLUETOOTH. We should at least be able to chose this behavior in a setting.
So is this a Samsung screwup? do other Samsung devices behave this.
How hard would it be for a dev to build an app to FIX this on Fascinate.
I thought I was the only one with that situation... I would love to know the answer/fix, however I have a feeling someone will be by soon to move this to the general forum...
I actually wanted the opposite. Overall, I liked how bluetooth was handled on my old chocolate and was surprised by the differences in eclair. I expected my bluetooth to be able to grab all audio, regardless of what apps were running. For instance I wanted to use my BT with a fring call. Seemed sensible!
Anyway, I went searching, and the prevailing opinion was that bluetooth was locked up until Froyo (and tightly tied to actual calls).
Does anyone know if audio is handled in a gracefully way in current AOSP or CM?
Swyped w/ XDA App. When in doubt, mumble.
soba49 said:
I actually wanted the opposite. Overall, I liked how bluetooth was handled on my old chocolate and was surprised by the differences in eclair. I expected my bluetooth to be able to grab all audio, regardless of what apps were running. For instance I wanted to use my BT with a fring call. Seemed sensible!
Anyway, I went searching, and the prevailing opinion was that bluetooth was locked up until Froyo (and tightly tied to actual calls).
Does anyone know if audio is handled in a gracefully way in current AOSP or CM?
Click to expand...
Click to collapse
I believe that my Droid 1 behaved my desired way on 2.1 and 2.2, can't remember if I used this way on 2.0...
I was assuming this was a 'problem' on Fascinate or Samsung, not android OS in general.
I thinj its a problem with fascinate. I was driving for 5 hours last week and I had bluetooth connected to my garmin and used one of those cassette thingies to play music from my fascinate. Sometimes I were able to talk without unplugging the headset.
Another reason I suspect its fascinate is cuz when I use my old blackberry headphones I have unplug and replug to use it for conversations.
Btw whats good stereo heaphones with mic that works with the fascinate?
Sent from my SCH-I500 using XDA App
I have a friend with a Vibrant and his apparently does NOT have this problem, so I am wondering if a Bluetooth file from his system might work on my phone.
There are 3 BT files in system dump:
BT OPP
BT services
BT test mode
so is one of these the file that would determine what path audio would take in any given situation? (e.g. headphone jack occupied while BT headset connected, desired paths media>headphone phone>BT)
I REALLY need to fix this before my 30 days are up or phone probably going back.
I got my hopes up when I discovered the 'secret menu', but I don't see any setting in there that seems appropriate.
I've tested with the superclean 0.7 DL30 rom and this same problem still exists
Please let me know if anyone finds a solution.
[email protected] said:
i've tested with the superclean 0.7 dl30 rom and this same problem still exists
please let me know if anyone finds a solution.
Click to expand...
Click to collapse
stupid ass samsung friggin morons!
It looks like this is a problem on other Samsung Galaxy S phones as well, see a thread and app someone made in the Epic forums.
http://forum.xda-developers.com/showthread.php?t=842571
it is just the phone app
this problem is extremely frustrating. if i have headphones plugged in the mic works just fine. the mic is only turned off when i use an AUX cable. It would be nice to be able to drive and not have to worry about unplugging the AUX cable everytime I wanted to use my phone.
I downloaded the Epic app they made over there but all it did was hard lock my phone with my first test. I dug into the code but I'm a wee bit over my head so I'll hit up the books and see if I can't work with the guy who made the Epic one to see about getting it working with our phone.
This was with the .7 superclean DL30 rom, I'd love for someone else to try one of the other DL30 roms and see if they have any better success.
I contacted the author of the app and he replied back stating he had a buddy with a fascinate test it and it worked fine and that it might be an issue with the busybox version included with the .7 superclean 2.2 rom I was running and that it relied on busybox having the pidof command. Later tonight I'll dig into this a bit more and post back hopefully a fix and instructions on hwo to ensure this is working
I got this working http://forum.xda-developers.com/showthread.php?t=842571
The Froyo version works just fine on the original DL30 leak and on rubiks .3 DL30 but does NOT work on DL30 super clean .7 or .9. In .7 I got a hard lock that I had to do a battery pull to fix and in .9 the app ran and looked like it worked, but the audio routing did not change as expected.
All credit to cicada, I did nothing more than test it
I have not tested this on any 2.1 ROMS
thande said:
I got this working http://forum.xda-developers.com/showthread.php?t=842571
The Froyo version works just fine on the original DL30 leak and on rubiks .3 DL30 but does NOT work on DL30 super clean .7 or .9. In .7 I got a hard lock that I had to do a battery pull to fix and in .9 the app ran and looked like it worked, but the audio routing did not change as expected.
All credit to cicada, I did nothing more than test it
I have not tested this on any 2.1 ROMS
Click to expand...
Click to collapse
I am on original DL30 leak and did NOT work for me... at least with Ambling Book Player. Not sure if it matters what app we are using to play media file. It shouldn't, but this whole problem should not exist. SAMSUNG morons!
Ok so i tried with my Rubiks DL30 ROM installed. The app opens up, no FCs or bricks or anything, but it doesn't work. I had my wife call me when i was driving, I picked up and she said she could hear me but I still couldn't hear her. I'm assuming that the car's mic is functioning but it still doesn't fix the issue. Is there a bluetooth adapter out there i can stick in the aux jack? Well i guess the first question should be, can the phone handle having two BT devices connected at the same time? i.e. hands-free calling and BT audio adapter
I'd say maybe try another full wipe and re-flash. I've switched over to the superclean EB01 roms, currently on 2.3 and hasn't had any issues with this working on 2.1, 2.2 or 2.3. I did have 2.2 initially not function with this tool, similar to what you reported above with it looking like it was working but not actually doing anything but a full wipe and reflash did the trick.
ok... thanks, at least you've run into that problem so i'm willing to give it another go. I'm currently on SC 2.4 so i guess i can be your guinea pig
I'm on SC 2.4 currently and had it stop working on me again. At work now but I'm going to try setting the app off and then back on, I have had to do that sometimes when flashing as the files get overwritten. This was working properly in SC 2.3
Hey man, thanks for the updates and info... you're really like the ONLY person that's giving me any hope on this. I thought the compatibility issues were busybox related? So I don't see why it wouldn't work on SC2.4
Would someone please fix this on Fascinate... ? pleeeeezzzzzz
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
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.
Frankly it's poor, call is fine, but the media I get distortion and crackling, I've heard others talk about it, but no one had mentioned a fix. Is anyone aware of a resolution, it's quite aggravating. There was a file I could edit on my captivate back in the day that upped the transmission rate that took care of it. Is there something similar that could be done here?
Sent from my HTC One X+ using xda premium
That's Interesting. I don't have any problems with the bluetooth audio streaming quality. Sure, nothing beats an aux cable quality wise, but it's always sounded pretty good to my ears. I consider myself a little bit of an audiophile too.
I notice it mostly in my car, but I also bought backbeat go ear buds today, and it really just didn't sound right, it's not in your face like holy cow why does his voice sound like that, it's more like crackling in the highs, I don't get it through aux though, I would have thought it was my phone, but I had seen it mentioned a couple other places
Sent from my HTC One X+ using xda premium
alpine type-r interiors and sub, alpine bt head unit, everything is powered by alpine v-power amps, and I gotta say, I hear the distortion pretty clearly over bt. My old inspsire 4G running cm7 sounded AMAZING over bt. I hope someone finds away to bump up the clarity some. devs? Lol
So I think it's safe to say, you like alpine ha ha, but seriously though, thanks for the +1, didn't want people to think I was just crazy or something.
Sent from my HTC One X+ using xda premium
You guys have tried this fix as stated in the General HOX+ Q&A?
Or it is a different issue?
IIRC that was the first mod I flashed for this phone, and while it helped 10 fold with the call quality, it did little to nothing for media and other audio.
i got the answer you're looking for...
i noticed this problem the first time i used my hox+ with my car stereo. same problem...bt calls are ok, but if you are listen to music, you hear ugly distortion in the highs...the sound isn't clear and the stereo image is bad.
after doing some research i found out that it has to do with the bluetooth bitpool settings. but what can you do against it: maxween did a bluetooth fix for me, which worked perfectly. it is implemented in the newest builds of his AOKP roms, and in the newest versions of Liors cm 10.1 roms.
so you can use this fix in every aosp rom.
unfortunently, there isn't a fix for stock-, and sense rom's jet. i've made a demand to mike1986 if he can implent it in his android revolution hd 6.5 rom, but it's not done atm.
so if you want to listen to some fine bt music quality (it sounds awesome in my stereo now btw.), you have to install the actual aokp or cm 10.1 rom...otherwise you have to wait for a sense fix.
ps: we've connected the brandnew htc on from my friend in my car stereo. same issue! looks like htc is doing this intentionally to sell more of the aptx care stereo adapters and beats accessoiries with the aptx codec...
I also have this problem. It annoys the hell out of me because I can ALWAYS hear it. Maybe i'm too sensitive. I don't know. Either way, I'm going to see if the Elegancia ROM can get the fix implemented.
Thanks for letting us know there is a fix.
The only way i have found to lessen the distortion is turn the media volume on the phone down to at least 3/4 and use the vehicle/Home stereo receiver to control the volume increase needed. It helps a lot, but a true fix is really needed
Indeed, and check to see if your receiver or head unit has a secondary volume control for each input. My alpine for instance, allows me to tweak the volumes for each specific input (AUX, HD radio, Bluethooth, CD) from a rang of -5db to +5. IF i set it anything above 0 it sounds like crap. Hope this helps some.
if the connection's fine, you should not have to turn down the volume. the sound quality is even better when the bt output vol is on max on your phone. on the other devices, i would recommend an input of 0db, if you are going above it, you have the risk of digital distortion, and this is sounding really ugly.
i'll post a link from maxween later so if any developer of a sense custom rom could do a fix would it be awesome
http://code.google.com/p/android/issues/detail?id=39632#c151
here is a thread about this issue, i also found a german page from a guy which used this fix for his htc one and it worked.
http://forum.xda-developers.com/showthread.php?t=1880298http://
i tried it out on my one x+ but unforunently it didn't work...so if some developer could make this "audio.a2dp.default.so" fix working on the hox+ (sense rom's) it would be awesome...
Thanks for all your research and time mr_breaks. I am hoping we can get a fix for this issue.
Using an aux audio cable is not a big deal but listening through BT is so much easier and allows me to control my music from my car controls. I like that functionality.
same here. i don't like to plug in the cable everytime and the control over my car is much confortable and safer.
btw: with the patch the bt sound is better than with cable
imo... of course it depends on the car unit, but i had very good results with my system and my hox+...
Sent from my HTC One X+ using xda app-developers app
So did you fix it or not? I thought you said you tried fixing the bitrate settings but it didn't work.
If I can change the settings myself, i'd like to try it if you could guide me.
not yet. there is no way to change the bitpool manually, it has to be done in the file called "audio.a2dp.default.so".
i'm waiting for support form the developers, cause i don't have the know-how to do a fix by myself. ..."i would, if i could"
mr_breaks said:
not yet. there is no way to change the bitpool manually, it has to be done in the file called "audio.a2dp.default.so".
i'm waiting for support form the developers, cause i don't have the know-how to do a fix by myself. ..."i would, if i could"
Click to expand...
Click to collapse
well as you know we don't have source for the exact version sense is using
if a version compiled from 4.1.2 is working must be tested
I can provide a version later
Sent from my HTC One X+ using xda app-developers app
maxwen said:
well as you know we don't have source for the exact version sense is using
if a version compiled from 4.1.2 is working must be tested
I can provide a version later
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
man, you are the man! if you can find a fix, i deffo gonna hit the donate button
mr_breaks said:
man, you are the man! if you can find a fix, i deffo gonna hit the donate button
Click to expand...
Click to collapse
ditto. it worth a few bucks IMO.