Database Develop

A2DP Bluetooth Audio interrupts

Hi Guys,
i have this problem for a long time and didn't find anything about it in web or in xda forums.
I have a HTC Dream + HBH-IS 800 Sony Ericsson Headset.
When i listen to music via A2DP the connection is not very stable...
the connection interrupts very often for about 2 or 3 seconds, then works for about 3 seconds.
This only happens when i am outside, not in buildings. I this the reason is because of interferences. The connection gets better when i move the G1 into a specific orientation (upper side up) and don't turn my head to the right
On my old Windows mobile phone i played around with bitpool (=ratio between quality and connection stability by constant bitrate) settings... is there a possibility to get the connection more stable, when playing around with this setting?!
How can this setting be changed on android?
Further information:
-ROM Cyanogen 4.2.5 but same problem on stock ROM
-HTC Dream has been replaced one by a new device -> same problem
-Headset was never exchanged, but worked perfectly on my old Touch Pro with WM 6.1
Thanks for your help

There is a known issue on the Bluetooth stack and is suppose to be fixed in the Elclair 2.0 fix, the temporary work around is to first pair and connect then disconnect and reconnect it again i'm having to do that several times a day when i use my RocketFish bluetooth stereo headset. Hope that helps

thanks for this workaround, will try it tomorrow and will post if it works for me too

hmm, didnt really work for me... no change after pairing disconnecting and connecting again.
i wonder why this only happens outside, not in buildings... another frequencys which interferences maybe?!

Be sure to disable wifi.

Not trying to hi-jack your thread. If you want me to open another i will. However this is a BT question as well.
my G1 is set to connect to my stereo in my car. Pioneer BT head unit. I find that i have to manually tell it to connect every time i get in the car. When i had a blackberry before it would just connect every time on its own without me doing anything once i made the initial connection.
Any ideas?
thanks.

Press1Now said:
There is a known issue on the Bluetooth stack and is suppose to be fixed in the Elclair 2.0 fix, the temporary work around is to first pair and connect then disconnect and reconnect it again i'm having to do that several times a day when i use my RocketFish bluetooth stereo headset. Hope that helps
Click to expand...
Click to collapse
Worked on Dell Streak A1.6

I have Dell BH200 headset as well, and I have the same exact problem its like the audio stutters but when I first connect it its more stutter than music so you can barely even understand the music until after 30secs when it starts to normal out.
ATM im runnning Stock 1.6 for G1, im going to try Cyanogenmod 6.0 tomorrow and see if anything changes.
but everyday I go back and forth with my laptop and phone since my headphones run for atleast 3-4 days.

wow, finally someone having the same problem.
and even the same description of the connection issues.
I recently bought a orange SanFran and, as the device is fairly cheap, a nokia bh-504 along with it.
The connection isnt stable even when I put it in my breast pocket.
As soon as I move my head to the right, the streaming stops. Completely.
I can easily stop the music when holding my hand in front of the right earpiece.
so i will try the disconnect / connect again "workaround", but I don't think that will help.
I paired the same headset with my gf's netbook and I could walk through the whole apartment and the signal was stable even through up to 4 walls.
so no one here knows how to tweak BT settings in android?

Help with Bluetooth and Fresh 1.1

For some reason when my phone connects to a headset that supports both audio and phone the audio will not auto connect. I have to open the bluetooth options and hold down on the device i want to connect to then check the audio box.

sounds similar to the problem I'm having... I connect my phone via bluetooth to my car (Ford Sync) and I need to turn bluetooth off then on at least once (if not twice) for the car to recognize the phone.
I am getting so fustrated with this phone... Its been replaced twice (like replacing hardware is going to fix a software bug).
i really want to stay with an Android phone... maybe the Samsung Moment? it appears as if 2.x is now available (unofficially?) since Samsung released the Kernel source like they were supposed to.
TL

It worked before fresh 1.1 so maybe it was just a change in something.

I'm using the stock software and I have the problem so it is not freshrom

man we need an update HTC!!!!!!!

q1 almost over so we're that much closer to getting our official 2.1 update.

I've also got a bluetooth problem - would really appreciate any help you can offer.
I have a Tomtom and headphoned in my Bike Crash Helmet. I want to connect so I can hear music and phone calls through the phone in my helmet and also hear the TomTom.
The Tomtom connects to the Helmet, the phone connects to the Tomtom and I can get calls through the speakers via the Tomtom but music won't play (apart from an annoying second or two after dropping a call).
If I can get the phone to advertise headset features I could connect the Tomtom to the phone and the phone to the speakers (think that would work), otherwise I believe the Tomtom is not advertising media audio, only phone audio and don't expect I can change that.
Any thoughts...?
PS - Have tried the market headset app - unfortunately it doesn't fix the problem...

Time_Lord said:
sounds similar to the problem I'm having... I connect my phone via bluetooth to my car (Ford Sync) and I need to turn bluetooth off then on at least once (if not twice) for the car to recognize the phone.
I am getting so fustrated with this phone... Its been replaced twice (like replacing hardware is going to fix a software bug).
i really want to stay with an Android phone... maybe the Samsung Moment? it appears as if 2.x is now available (unofficially?) since Samsung released the Kernel source like they were supposed to.
TL
Click to expand...
Click to collapse
well now the source for the CDMA hero is out so shouldnt be long till a lot of the little bugs arre resolved.

Bluetooth nexus one connecting to Renault carkit

I recently got my new Renault Scenic car and discovered a rather strange situation.
The phone pairs with the carkit and connects the first time without issues and works like a charm.
But however when I start the car and thus also the carkit the phone connects also but no audio is heared trough the carkit when calling or getting called. The phone says it transfers the connection to the carkit but nothing is heared.
It only works when I have bluetooth off, starts the car and then turning bluetooth on the phone on. Wait till it connects and make a call. With this procedure the connection is good till I step out the car.
Its a work around but hmmm not the one i would love to.
I have a nexus one rooted with the latest MCR (21) and an intersect kernel. Though I tried different kernels also but no go.
Hopefully one of you guys have an idea

Ok I searched a bit and found out the Bluetooth is done with the opensource code Bluez. So I wonder which version of Bluez is in the froyo roms and how it can be updated if possible to a new version.
Anyone knows ?

I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.

igalan said:
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
Click to expand...
Click to collapse
Hi,
I've just come across your post. Did the situation improve ?
I'd just point out that for me it comes from the Android system : I own a Renault Mégane 3 and was able to fully use the bluetooth system with my HTC HD2 (Windows Mobile 6.5). Now, I've just installed Android 2.2 on it and I encounter a similar behavior... and the car can't connect to the phone directory either...
Looks like I'll boot back on Windows Mobile when driving...
Regards,
Stéphane

My Hero with the official 2.1 ROM is now 100% reliable. The Nexus One with Froyo isn't, A2DP is still hit & miss.

Well... I'm getting the same but not with Renault ones.
I have LiquidAUX on my car and to have both phone and a2dp synced, I have to restart phone BT and LiquidAUX every time I go into car. And most of the times I can only have 1 connection each time, or phone is on and a2dp is off or a2dp is on and phone is off. It's really annoying since I had an HTC Hero with Android 2.2 and it used to work with no problems...

Hello, I've the same issue with my new Renault and Nexus LG. The phone pairs with the carkit and connects the first time without issues and works like fine. Once someone calls, the connection is terrible or lost! I checked the phone compatibility list at Reanoult and the NEXUS LG is on that list. So it should work. Updated R-link2, same issue. I went to the Renault garage and they told me that this is a bug in the Renault software, they can't do anything about it. Can't believe this, there should be a solution or fix.

Bluetooth - Auto connect?

i've paired a few things (bt headset, parrot car hands free, computer) but it won't automatically connect to anything. i have to manually tell it to connect. is there a setting that i'm overlooking, or a tweak to allow this?
thanks.

Yeah I noticed the same thing in the car today. Maybe because of whether it is discoverable or not? When you turn that on it only does 120secs. I haven't played with it, but i sure hope it can auto connect, or at least with froyo.

It auto-connects to my car, but not to my home phone. I think that's because the car itself initializes the connection... Would be nice to figure out how to fix this, so I wouldn't have to connect manually every time I come home.

wgarrido said:
Yeah I noticed the same thing in the car today. Maybe because of whether it is discoverable or not? When you turn that on it only does 120secs. I haven't played with it, but i sure hope it can auto connect, or at least with froyo.
Click to expand...
Click to collapse
In my 10' BMW, I had to check mark to always allow the car to access my contacts. Once I did that, it would automatically connect to my car upon startup of the car.
Hope that helps.

rajsharma714 said:
In my 10' BMW, I had to check mark to always allow the car to access my contacts. Once I did that, it would automatically connect to my car upon startup of the car.
Hope that helps.
Click to expand...
Click to collapse
in my '10 Genesis Coupe, I cannot get it to auto connect, even though i reset it two times and checked "always allow." This is the first phone this has ever happened with, every other one auto connected (HTC Touch Pro2 with winmo 6.5 AND a hacked android 2.0, htc hero w/ 2.0 and 2.1, n1 w/ 2.1 and 2.2, and a feature samsung phone) so I know its not the car.
Any more ideas?

What I figured out is that auto-connect on this phone just doesn't seem to work at all. The only time it auto-connects is to my 06 Acura when I start it and only if it's not already connected to anything else. But that's because when I start my car, it's the car that initiates a connection, not the phone. If I'm connected to something else (like my home phone, for example), when I start my car, and drive off, Bluetooth connection to my home phone will get dropped after I get away for more than 100 feet, but it will never connect to my car after that. And it never connects to my home phone on it's own. Very painful!:-(

My Captivate will automatically connect to my Parrot hands free device when I get into the car. I don't know which device is pushing the connection. However, I also have a Miccus BluBridge Receiver in my car plugged into the Aux jack. This device doesn't auto connect.
To get things working I have to go to the home screen, settings, wireless, blue tooth, then click on the device. A friend of mine was talking about Tasker as a possible app to use, but I don't really want to spend the money on it until I know it will do what I want. The other annoyance I have is that speaker, headset, and bluetooth volume are all the same. It looked like Tasker would solve my second problem, but perhaps not my first. Has anyone else investigated this?

Bluetooth auto connect
I too thought I had an issue with this. Mine is now working OK most of the time. One thing I discovered is that if there is more than one BT device available the phone sometimes will not connect automatically.
I wonder if this has to do with the fact that it will not connect to more than one device at a time. This is big downside for me that I hope get corrected (but please GPS first)

It won't conect correctly because there is no setting for always visible. The handsfree device searches for your phone to initiate the conection and if it can't see it it won't try to conect.

jbl7979 said:
in my '10 Genesis Coupe, I cannot get it to auto connect, even though i reset it two times and checked "always allow." This is the first phone this has ever happened with, every other one auto connected (HTC Touch Pro2 with winmo 6.5 AND a hacked android 2.0, htc hero w/ 2.0 and 2.1, n1 w/ 2.1 and 2.2, and a feature samsung phone) so I know its not the car.
Any more ideas?
Click to expand...
Click to collapse
I also have a Genesis Coupe 2010 (3.8 in case you care) and my vibrant connects just as well as my TouchPro2 and my Nexus One running Foyo.
The Nexus One stock 2.1 never worked, reconnecting every couple of minutes.
My first Vibrant (same as captivate) did not work well either. I expected it was because the BT stack in Eclair did not support car profile, but after I exchanged my Vibrant due to a rattling volume key, it has worked very reliably with the GC'10. It autoconnects ad soon as I turn on the engine, without having to do anythong, followed by "transfer complete".
I leave BT on all the time. My phone is not rooted or modifief in any way, running stock software for everything.
Sent from my SGH-T959 using XDA App

thumper_1151 said:
It won't conect correctly because there is no setting for always visible. The handsfree device searches for your phone to initiate the conection and if it can't see it it won't try to conect.
Click to expand...
Click to collapse
That is not true and it is not necessary, not even during pairing, ad the connection is initiated by the phone. Once passkeys are echanged, visibility is not required.
Please verify your answers prior to posting to prevent other people from getting confused.
Sent from my SGH-T959 using XDA App

jbl7979 said:
in my '10 Genesis Coupe, I cannot get it to auto connect, even though i reset it two times and checked "always allow." This is the first phone this has ever happened with, every other one auto connected (HTC Touch Pro2 with winmo 6.5 AND a hacked android 2.0, htc hero w/ 2.0 and 2.1, n1 w/ 2.1 and 2.2, and a feature samsung phone) so I know its not the car.
Any more ideas?
Click to expand...
Click to collapse
What firmware do you have on your GC? Have you deleted all phones?
Things to try:
Delete all phones from the car (setup/delete all phones)
Restore the phone to factory settings.
Upgrade the car's radio/BT firmware (see dealership for details or try gencoupe.com)
Call ATT support (?)
Wait for froyo
Get used to
Return/sell the phone
Hope this helps
Sent from my SGH-T959 using XDA App

I have the same issue with my Plantronics Voyager Pro . Can't get it to auto-connect! Anyone have an idea what the problem is?
Sent from my SAMSUNG-SGH-I897 using XDA App

I am a tech for mercedes and we have to set the phone to always visible or it wont auto connect. It is the same way with pioneer bt radios. I am just speaking from what mercedes told us and personal experience with pairing phones. I have had the problem probobly 100 plus times at work where phones wont auto connect evan though they are paired corectly and when you change the phone to always visible it fixes it every time. I know the phone can initiate the conection, i just know they don't all do it automatically.

thumper_1151 said:
I am a tech for mercedes and we have to set the phone to always visible or it wont auto connect. It is the same way with pioneer bt radios. I am just speaking from what mercedes told us and personal experience with pairing phones. I have had the problem probobly 100 plus times at work where phones wont auto connect evan though they are paired corectly and when you change the phone to always visible it fixes it every time. I know the phone can initiate the conection, i just know they don't all do it automatically.
Click to expand...
Click to collapse
Never had the problem with any of the Pioneer radios we've had, and my Eclipse doesn't have that problem either. To be fair, I've no experience with MB cars, but that shouldn't be the case.
I know with my Eclipse HU, I had to initiate the connection while in the phone menu otherwise it would connect for BT audio but not for the phone. After setting up the phone it will connect as its supposed to regardless of what input I'm using.

just as an update to my initial problem... my parrot system in my car auto pairs all the time now (it just takes ~30-45 sec to do so), but the phone still will not auto pair to bt headset or computer...

I don't think its supposed to auto connect to the computer. I think its a need based connection.
And on that note, when i send a file my phone does connect. I don't use a dedicated bt headset so i can't talk about that unfortunately.
Sent from my SAMSUNG-SGH-I897 using XDA App

Lucke said:
just as an update to my initial problem... my parrot system in my car auto pairs all the time now (it just takes ~30-45 sec to do so), but the phone still will not auto pair to bt headset or computer...
Click to expand...
Click to collapse
When you say 30~45 sec, does it mean from powering the car up until BT is usable through the car system? That's is normal and the duration depends on how many contacts you have in your phone book and how many phones per contact. Mine take about the same.

BigJayDogg3 said:
I don't think its supposed to auto connect to the computer. I think its a need based connection.
And on that note, when i send a file my phone does connect. I don't use a dedicated bt headset so i can't talk about that unfortunately.
Click to expand...
Click to collapse
I agree. It is only supposed to autoconnect to devices that support the handfree profiles, if the handfree profile is set as default.

I tired turning visible on right before i started the car and it connected no problem. Really annoying. I have a pioneer as well. Too bad you can't set it to visible always. Other than that it works much better than it did with the Fuze/Any WinMo phone. Never had a phone that worked right in the car, except for my GF IPhone, works great.
I hope it works better in Froyo.

[Q] bluetooth with car stereo problems, you guessed it

Okay, so lots of people have problems with their bluetooth. I am too. I have a JVC KW-XR810 car stereo and the bluetooth keeps shutting down on one or the other. My questions are:
Does anyone else have this stereo and problem? If so, whats the situation?
Is there a ROM that works flawlessly (or close to) with the bluetooth?
Its odd though, that my headset works perfectly and I didn't have many problems with another stereo I've used. Makes me wonder if its the stereo or the phone. Still, many others have bluetooth problems with this phone...
Thanks for any responses.
Stock Froyo
Rooted
One click lag fix

My last 3 phones (including this one) have all worked flawlessly with my Sony MEX-BT3700 head unit. Phone calls, BT dialing, streaming music, all work perfectly.

Yep, same here - AT&T replaced my Captivate under warranty about 2 or 3 weeks ago due to the random shut-down issue. Took the new one home, installed Froyo, and rooted it. Everything works well, except lately I've been getting frequent bluetooth disconnects from my car stereo (Pioneer AVIC-X920BT).
The usual pattern seems to be it's good for about one call, and then shortly after ending that call, I notice that they are no longer connected. I usually turn off BT on the phone (seems to take a while to terminate) and then turn it back on, but it will usually only be good for a single call. It's been frustrating, and I'm leaning toward the problem being on the phone side, since that's where there have been recent changes.

Must be a problem with Stock Froyo. Glad I'm not using it.

I've had this issue with certain roms I was running. I have a Kenwood KDC-X993. So far on CM7 it stayed connected.
Sent from my SGH-I897

i have the same (or similar) problem with my OEM headunit on a VW Golf. BT randomly disconnects but my music (pandora) still plays through the BT stereo, unless I stop it. Then its completely disconnected and I'll have to reconnect the phone to the car.
annoying but I just deal with it.

I'm running Paragon 6 and have a Dual head unit. I haven't had any disconnect issues, my problem is the crappy Pandora app.

mdaudioguy said:
Yep, same here - AT&T replaced my Captivate under warranty about 2 or 3 weeks ago due to the random shut-down issue. Took the new one home, installed Froyo, and rooted it. Everything works well, except lately I've been getting frequent bluetooth disconnects from my car stereo (Pioneer AVIC-X920BT).
The usual pattern seems to be it's good for about one call, and then shortly after ending that call, I notice that they are no longer connected. I usually turn off BT on the phone (seems to take a while to terminate) and then turn it back on, but it will usually only be good for a single call. It's been frustrating, and I'm leaning toward the problem being on the phone side, since that's where there have been recent changes.
Click to expand...
Click to collapse
Same here, I have a Parrot mki system in my car, but I found a workaround that I hope works for you too:
Unpair with the device, and when you re-pair it, when it asks you to synchronize contacts, do not let it. It will bug you every time it connects, but just ignore the requests.
I haven't had a single disconnect since doing this weeks ago.

I've read about the contacts request from other users but it doesn't happen with mine. Another thing, when I lose the connection and I turn off bt one the phone out shuts off. Completely. Pushing the power button does nothing. Holding the volume up and power buttons together for a few seconds seems to restart it but theres no animation. Just the lock screen, media scanner, etc. Maybe its restarting on its own and the button pushing has nothing to do with it. Also, I listened to my bt headset for hours last night with no probs at alI. Idk. Is bt different for head units? I thought it all used the same protocals.
So it seems that its not my head unit, but the phone. Are there any good solutions for us?
Sent from my SAMSUNG-SGH-I897 using XDA App

My head unit never asks to download contacts. Could it be that some do because they store that info in order to identify and announce incoming calls? That would mean there's more going on than just a simple BT connection.

Yeah. One post I read said something about it using a data connection the hu for contacts. I have no idea what he was talking about though.
Sent from my SAMSUNG-SGH-I897 using XDA App

My head unit have the ability to sync contacts. When I first paired it, the phone asks me for permission and there's a check box to always allow.
Sent from my SGH-I897

nahrah said:
My head unit have the ability to sync contacts. When I first paired it, the phone asks me for permission and there's a check box to always allow.
Sent from my SGH-I897
Click to expand...
Click to collapse
The only purpose I can see for this is if the head unit has an integrated nav system. That would allow you to bring up a contact as a nav target independent of the phone.

Okay, gettinging back to my original questions. So far we've established that this is endemic to the captivate, mostly. There have been two replies saying that cm7 and paragon 6 have stable bt connections with head units. I read in another post that axura works as well. This is so frustrating that I'm just about willng to learn how to flash this thing.
Sent from my SAMSUNG-SGH-I897 using XDA App

NvigR8 said:
Okay, gettinging back to my original questions. So far we've established that this is endemic to the captivate, mostly.
Click to expand...
Click to collapse
We have? My first post says I have zero issues with this on my head unit with my phone on Eclair, Froyo and now Andromeda. If it is a phone issue mine is not suffering from it. Sounds more like it has something to do with head units that store contact data. Mine apparently doesn't.

Hmmm.
Yet in your second post you posited that it must be a Froyo issue.
Regardless of whether it is the phone or OS, a lot of Captivate owners seem to have bt issues of one kind or another with various devices. Maybe this is just a bt issue in general that everyone deals with (not just Captivate owners) and I'm just being sensitive because I haven't had much bt exposure.
Any help is appreciated here. I'm just looking for suggestions on what to do short of buying a new phone or head unit. It would be great if other users experiencing this problem would benefit from the discussion as well.
So far it appears that flashing a different ROM may be a solution but which one? Is there any way to change only the bt stack?

Sorry if that sounded short, but I'm REALLY frustrated with this.
My hu will store contacts as most do these days, but it doesn't ask for them. I don't think the problem is related to the contacts. I guess its just a random incompatibility thing.

I said it "might" be a problem with stock Froyo. I didn't see it the 3 days I was running it and my current ROM is Froyo-based and working without issue. The only other variable I can see is that others posting problems have reported having to deny access to contacts, something my head unit never asks for, in order to get it to work. That would appear to indicate the difference is in the head units and not the phones, but unless I could connect to one of these other head units to verify, I'm only guessing. Sorry.

i notice that if I toggle the bluetooth on my phone right before connecting it to my car, it works flawlessly

Installed a Kenwood X994 and had all kinds of issues with BT. Worked for awhile but would never auto connect. Only vehicle and area where I had BT issues. I realized it was due to the downloading of contacts at every connect. sometimes it would download than immediately disconnect. frustrating. Was on serendipity, Tried a native Cappy ROM, Cognition and now Phoenix..
The unit has the Parrot system in it so it should be ok. Finally decided to update the Firmware on the HU. So far so good. I like the contact download so I don't need to use the phone at all to make a call. Receiving calls is no problem.
Will test further tomorrow.
BTW I have a BT Garmin mounted in the truck and used it before getting the head unit. no problems connecting. The only issue with that was a delay between pressing the call button and the call being made. Hanging up was an issue as well.