I am unable to get my Captivate to even see my Plantronics 320 headset. I have run several ROMs including the stock, the Samsung update and several versions of Cog 2.2, currently running 2.2.5. I know that it works with my HTC Fuze (Raphael) running Windows Mobile and it pairs though does not work properly when running Xandroid 2.2 on my Fuze (proper bluetooth operation known to be an issue with Xandroid). Normally I would just assume that it is hardware incompatibility between the 320 and Captivate but when I google this issue, there are websites selling the 320 specificially for the Captivate (fommy_com for example). Thanks in advance.
What specifically is happening? First time I flashed to Froyo (Not cognition) I had issues as well, it would pair, prompt for the code, then connect and immediately disconnect. I was stuck in that loop and couldn't get it working. Flashed to Cog shortly after and it's worked fine since.
Also could be simple compatibility issues. That's an older set so if you were having problems in 2.1 that may be th ecase.
With the headset turned on, I enable bluetooth in Android and it scans and does not find the headset. Repeated scans do not find the headset. Pressing the button on the headset does not help. Turning the headset on while scanning does not help. The phone does see my neighbor's Macbook so it appears to be scanning appropriately.
It is funny: I don't use the headset much but it bothers me to no end that I can't get it to pair and I have spent what some people would consider a ridiculous amount of time trying to get it work. Personality flaw.
Fixed issue. Not entirely what I did but now pairs. ?Perhaps I reset the headset with multiple long presses? Anyways, works now.
Related
It's like the elephant in the room around here. The bluetooth service on 2.1 is some crazy, broken crap. No matter how many times and how many ways I try to get it to pair to my brand new Kenwood x994 it refuses to save. It will eventually link up BT audio if I search for devices and let the pairing fail, but what a PIA to mess with every time I get in the car. I rolled back to Fresh 1.1 today and I had it paired and working perfectly in 10 seconds.
So here is the question, can we put the 1.5 BT stack into the 2.1 ROM? I already tried the 1.5 libbluetooth.so in the /system/lib filesystem, but it didn't change anything about the pairing problem (obviously I have no idea what I am doing and stabbing blindly at anything bluetooth related).
Anybody have any ideas? Is the BT compiled into the kernel? Can we recompile it with the 1.5 version?
I've asked this question a few times already and the answers are usually 'no'. Gawd I wish we could as no 2.1 roms (I've tried almost all of them) will pair voice (audio is OK) with my Pioneer Avic D3 car radio. 1.5 works perfect
Mine works exactly the opposite. The hands free phone works perfectly, but the phonebook doesn't download and BT audio fails to connect.
It sounds like it may be your phone, your should update with the official 2.1, then take it to a sprint store and have them replace it.
My phone has worked flawlessly to my jeep stereo with any 2.1 rom I have used in the last several months.
So this whole time I thought it was because we had a leaked version, but is this the official ROM that still has this problem. It's not the device cause I've had it replaced twice and my wifes doesn't work either.
I am not able to connect to my Pioneer AVH btw.
djorijun said:
So this whole time I thought it was because we had a leaked version, but is this the official ROM that still has this problem. It's not the device cause I've had it replaced twice and my wifes doesn't work either.
I am not able to connect to my Pioneer AVH btw.
Click to expand...
Click to collapse
I agree, if it was the hardware it wouldnt work with 1.5 either. Besides, Dan Hesse is my boss. He'd get hacked if I took back my phone
Thread moved.
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.
Hi guys,
I am having problems with car BlueTooth hands free and Samsung Galaxy S:
With Eclair 2.1 it was working flawlesly, connected automaticlay after paired, I could make phonecals, receive phonecals, no quality issue, phonebook worked fine etc... The only problem was that once I did not swithced the BT on my SGS before starting to drive, for some security reasons the car was not searching for phones while driving, so I had to turn the BT in car off and on again and then it connected well. But overal problem free...
With latest 2.2 Froyo (i9000xfjp7) and also previous Froyo distributions (i tried JPA if I remember correctly), the phone can be paired, it connects to the car but after one phonecall it looses connection and works no more. The strange thing is, the BT icon on the phone shows brackets (like when connected) and also the car shows the phone is still connected. But phonecalls cannot be made via car HF and also cannot be received through it. Only by manualy accepting or dialing on the phone. And naturally the sound goes only via the phone, no HF.
The strange thing is, when I turn off the car and leave it, the phone says it is still connected to it, which is impossible.
Any ideas?
Thank you!
czechmate said:
Hi guys,
I am having problems with car BlueTooth hands free and Samsung Galaxy S:
With Eclair 2.1 it was working flawlesly, connected automaticlay after paired, I could make phonecals, receive phonecals, no quality issue, phonebook worked fine etc... The only problem was that once I did not swithced the BT on my SGS before starting to drive, for some security reasons the car was not searching for phones while driving, so I had to turn the BT in car off and on again and then it connected well. But overal problem free...
With latest 2.2 Froyo (i9000xfjp7) and also previous Froyo distributions (i tried JPA if I remember correctly), the phone can be paired, it connects to the car but after one phonecall it looses connection and works no more. The strange thing is, the BT icon on the phone shows brackets (like when connected) and also the car shows the phone is still connected. But phonecalls cannot be made via car HF and also cannot be received through it. Only by manualy accepting or dialing on the phone. And naturally the sound goes only via the phone, no HF.
The strange thing is, when I turn off the car and leave it, the phone says it is still connected to it, which is impossible.
Any ideas?
Thank you!
Click to expand...
Click to collapse
Had exactly same issue I changed to Doc Rom JP8, for last 3-4 days didn't face any issue.
Monu123 said:
Had exactly same issue I changed to Doc Rom JP8, for last 3-4 days didn't face any issue.
Click to expand...
Click to collapse
That is weird... When I switch back to Eclair, it works OK, back to Froyo, no HF after one phonecall...
I dont know how to work with ROMs, I managed to find out how to flash firmwares, I even handled many problems with Odin and its moods, incomplete flashes, etc... But I dont know how to use these custom ROMs...
Anyway, i would appreciate if someone told me how to resolve it without custom ROMs, as I plan to use offical Froyo when it becomes available, but with this issue, it is useless for me, as I travel a lot...
No one else?
I'm having a related problem.
I'm getting music stream cut outs (1 sec max) when streaming bluetooth to caraudio WHILE wifi on.
If i disable wifi, bluetoothaudio works fine. I know they share range bt/wifi, but this is unacceptable. They should negotiate. Everytime wifi scans, i get cutouts. Unusable. Only workaround is disabling wifi (and thats annoying because i have to be constantly activating/disabling it everytime i enter somewhere with wifi etc.
Using Docrom xxjpo v8 with voodoo.
Anyone has some software fix that makes wifi behave better when bluetooth musictream on?
There are some weird issues I have been noticing with my SGS regarding bluetooth.
At first, I got slightly irritated when I found out I was suffering what I thought to be this issue on my SGS (noticed after flashing to JP6, later on JPX and now also on JPY). But since, I have been carefully narrowing down the problem (there seem to be several variants of the issue bundled within the one linked) and have finally figured out how to reproduce the error (sort of, at least in my setting: SGS-I9000, BMW 1series car BT system).
After setting a custom BT device name and pairing to the car, the BT handsfree works flawlessly on spot and if disconnecting and reconnecting later. The problem starts after rebooting. Now, here's where I'm getting inconsistent results.
Most times the bluetooth info I entered is simply reset to factory defaults: the pairing list is empty and the device name is set to the standard "Galaxy S".
Some other times however, it gets much more annoying: all the settings seem to be intact (pairing and device name stay as set) but BT connection always drops after about 60s (regardless of wheather you start/receive a call or not).
Is this a known issue? Did any of you experience this behavior? Any known fixes?
Thanks!
Phil
What ROM are you running? Get yourself onto the newest Froyo and see if the problem goes away. I definitely don't have problems with mine going to headphones, ear headset, or in car system.
Doc kitchen (jan 3rd) + Hardcore kernel JPY (which means latest kernel/drivers). This has been happening to me all along though, despite of rom changes (also happened with stock JP6 and darky's JPX).
Sent from my GT-I9000
Hi,
same problem for me: the bluetooth connection to my Parrot MKI9200 car audio system drops after a few seconds. This was not the case with ROMS older than JPX/JPY.
Are you still having this issue? I just flashed Serendipity 6.2 and have the same problem. When I reboot the Bluetooth settings are reset to default.
goodolsen said:
Are you still having this issue? I just flashed Serendipity 6.2 and have the same problem. When I reboot the Bluetooth settings are reset to default.
Click to expand...
Click to collapse
The issue disappeared on flashing to a new rom. I'm soory not to be able to give you more details because I found out the issue was gone by surprise (I had stopped using the car handsfree alltogether because of the issue).
Right now I'm on a Doc rom (hardcore kernel, JPY radio, ext4 system & data, ext4nj cache) and it works perfectly!
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.