I am having problems with ICS and the a2dp streaming after initial connection. I can't stream audio to any devices after the 2nd connection. This issue can be fixed with a cold boot (usually).
As near as I can tell this is an issue with all Rezound ICS ROMs
I have been trying to edit /etc/bluetooth/audio.conf and going through different iterations, but so far haven't been able to find the right combination (if it is even possible to fix from there).
I noticed there have been other bluetooth issues with other ICS ROMs for other devices (see: http://forum.xda-developers.com/showthread.php?t=1450962), note the a2dp fix in the changes log.
I am not sure if this is even the same issue on that ROM, but it may help provide a clue.
Anyone else have any thoughts or ideas?
Thanks!
Or a similar problem I have been having is connecting fine after initial pairing but being unable to reconnect without unpairing and a cold restart. Same problem in every ICS rom.
There's times mine will connect and work fine. Other times it says connected but sound will come out the phone speakers instead of the car speakers. This seems random and comes and goes. I haven't rebooted today and I was able to connect fine three or four times and a couple times I wasn't.
I havent been able to stream music at all.
Related
Is it possible to put the old android 1.6 bluetooth control into a nexus ROM?
My G1 worked great with my car's built in bluetooth system, but my N1 wants to be a PITA. It refuses to stay connected, it is constantly disconnecting and reconnecting, disconnects after about 30 seconds and reconnects a couple minutes later and then repeats this cycle. (I know this because my car tells me audibly every time this happens) It also will not transfer audio to the system, or the system voice controls will not answer or start calls even when the phone and system show connected (the brief times that it does show connected). That fact makes me wonder if the bluetooth audio problems others complain about is the same issue I am having, and that their phones are not connecting properly as well. I think the issue may be caused by how the N1 treats phonebook access. With the G1 I would get a "connection complete" message when the bluetooth connects and a "transfer complete" message when the phonebook access completes. I never receive the transfer complete message for the N1
The real crazy thing is that I can get it to work if:
I do not have the phones bluetooth turned on
I then get into the car and start the car (its bluetooth then turns on)
I then turn on the phones bluetooth (if the phone does not connect to the system immediately I click connect manually)
I then must make a phone call within just a few seconds after the phone connects
After that everything works as expected. I have found no other combination of turning on or off bluetooth on the phone or car system that also works.
I was having problems with my car audio as well, until I updated to Cyanogen's latest. Everything seems to be working quite well now. What ROM are you using???
Stock ATM. The N1 is good enough stock (as opposed to the G1) but for the lack of free tethering. I'm sure it can be even better though. Staying connected to my cars system seems to be my biggest issue, audio works great when I get it to connect properly.
if got the same issue on my parrot.
but the problem still persists on the latest cyanogen mod
Yeah, I don't know what it is that is different in 2.1, but 1.6 works great with bluetooth.
I don't guess its possable to do, I hope an official fix comes soon.
So my Jawbone Prime was connecting fine before I updated to ICS LPQ (was on GB LA4 before) and now it doesn't even show up on the devices list even when I try to re-pair or reset the headset.
I tried 2 different sets to no avail.
Anyone know of a solution?
Connects to A2DP BT Headset (Motorola) but only allows media audio to connect. Phone audio doesnt stick.
ICS has some compatibility issues with certain bluetooth devices.
GB my phone always paired with my car stereo and streamed music without any issues.
So far every ICS release, even official, has caused my phone to reboot after streaming music over BT for 10+ minutes.
Its pretty sad they dropped the ball here. GB worked fine, and they borked it.
Well I can connect my BT keyboard fine. I just tried my Motorola BT earphones which are A2DP and it connects but won't allow phone audio to go through the BT earphones. However Media does go through. At least it detects it.
It doesn't detect it at all on the Jawbone Prime (which is not A2DP).
Update:
I managed to connect my jawbone and actually have 2 phone calls on it. After that I had the phone in my pocket and when I checked maybe 15mins later it had frozen and I had to keep power pressed to shutdown/reboot.
It kind of matches Chakker3D's pattern of working then not working. It's like there's a memory leak in the bluetooth stack? maybe I'm just spitballing here.
What I know is that in GB whenever I deactivated BT it took a good 20-25secs. In ICS it's instant to turn off or on. In GB however there was 0 issues.
I just really hope Samsung addresses it. Or if we are lucky, a dev will rework a rom so this problem is gone.
But from what I can tell, very few are having this problem.
Airbag888 said:
So my Jawbone Prime was connecting fine before I updated to ICS LPQ (was on GB LA4 before) and now it doesn't even show up on the devices list even when I try to re-pair or reset the headset.
I tried 2 different sets to no avail.
Anyone know of a solution?
Connects to A2DP BT Headset (Motorola) but only allows media audio to connect. Phone audio doesnt stick.
Click to expand...
Click to collapse
Sometimes is helps when you change kernel. Give a try
078gregory said:
Sometimes is helps when you change kernel. Give a try
Click to expand...
Click to collapse
Another update:
Without any intervention on my part other than keeping on trying it finally discovered my BT headpiece. In fact it discovered both.
Now it's still not 100% perfect because it discovers it, connects and immediately disconnects. If I press a button on the headpiece while it connects then it stays connected and it hasn't restarted/locked the phone yet. I even connected my 2nd headset (another Prime) and it worked.
Keeping fingers crossed. Now I need to see what happens when I walk out of range and back in range.
My phone has the JB update that was released to a few earlier this week. All is working very well so far, except for a Bluetooth issue I am having.
First, I have a Belkin CarAudio Connect in my truck and bluetooth works perfectly with this just like it did with ICS. I can use it for both phone calls and streaming audio without any problem. For this reason, I know that bluetooth is working on my phone after the JB update.
I also have a 2011 Jeep Grand Cherokee with the Uconnect 430N stereo system in it. With ICS, my phone worked flawlessly with this stereo. Now with JB, the phone does connect, but a few seconds after starting a phone call or staring a music stream via bluetooth, the audio drops and shortly after, the stereo no longer recognizes the phone. I have tried re-paring a couple of times without success. Since the bluetooth connection worked prior to the JB update, I assume this is a software issue with the JB update on the phone and not an issue with the stereo.
Any ideas/suggestions?
Tried a FDR? That's my only suggestion at this point.
Factory reset
Sent from my XT910 using xda premium
My LTEVO (running Stock w Goodies 3.28 rom) bluetooth problems started last week when I tried to play music through my Alpine deck. I noticed it was skipping and stopping so I unpaired it, after that my deck couldn't find my phone and my phone couldn't find my deck. Also tried to connect to my Bose Soundlink and Moto Keyboard, no dice. Any advice?
If you haven't already you can try a full wipe and a fresh install?? Or have you tried a different kernel ??
Also you can make a nand of your current rom and try a fresh install of a different rom. Also you can try a nand of an prior rom you may have to see if the problem still exists.
#Root-Hack_Mod*Always=SG3
3.28 gave me bt issues. Skipping, failing to pair, ect.
Jumped to viper 3.0 with no issues. Might be isolated issues but a reflash of 3.28 didn't help the issue. Seems like a rom related issue and there are better roms out these days. Might as well as make the jump.
Bluetooth Problem Solved
I know it's 2 years later, but here is the solution, and it is so simple that is laughable. You see, the issue is really a hardware problem. There needs to be more pressure on the contacts inside of the phone near the camera lens for both Bluetooth & WIFI. The solution is demonstrated in this simple You Tube video. Go to You Tube, and search for the following title: "Connection, Wifi and Bluetooth problems on HTC One X - SOLVED (not opening the phone)"
It is known that Custom ROMs of Legacyxperia SEMC 2011 has still remaining Bluetooth problems.
So what are those problems in detail?...
The following symptoms I noticed at my Ray:
1.) The pairing to some devices doesn't work or works only after several tries.
2.) After successful pairing the connecting and reconnecting works fine as long as bluetooth is not switched off. But if you switch it off and on again the connection of paired devices ALWAYS does NOT work! And this is VERY nerving.
I could imagine that this is a problem that could have been fixed, couldn't it?
You can only connect to the device again if you delete the pairing before and pair again. Often it is even difficult to delete the pairing info. Then you additionally have to switch if BT.
Can anybody confirm my test results??
So can anybody tell me why we have this problem and which are the reasons for this strange phenomena?...
It would be so fine if this problem could still be fixed by a patch!
Thank you very much!