Jelly bean update and bluetooth Calling issue

Just adding my name to the list of frustrated customers. I have the same problem here after my OTA update to Jelly Bean a couple of months ago. I have a SG3 I747 on Bell Mobility (Canada) and a 2008 Infiniti G37. I get totally garbled sound when making or receiving a call. The Bluetooth worked flawlessly when my phone had ICS but nowadays hands free calls in the car means my phone in my lap with speaker phone on. Boourns!
 
I have a 2008 Nissan Altima, which shares the same bluetooth hardware as the Infinitis from the same time... I am also having issues. The phone pairs and connects fine... the calls even go through. But, the audio is all garbled.

This happened to me when I had a G1 many years ago. And, after researching it then I am fairly confident that this is a bluetooth protocol issue. Whether it be through oversight or a mistake (hopefully it wasn't a design decision) the backwards compatibility protocols for certain older bluetooth systems apparently didn't get done correctly.

Sure, ICS will work because they got the protocols correct on that version... so my hope is that it gets fixed at some point with an update to JB. Now, I'm with Verizon so I don't know if this issue is carrier specific, or OS specific... that could help narrow it down if we could figure that out.
 
I'm on Verizon as well and this is a T-Mobile forum so it definitely is NOT carrier-specific.
 
Quick update:

I read this a day or two ago on, and don't quote me on it, that Google knows about the bluetooth A2D (or is it AD2) audio protocol problem but specifically with streaming music through the bluetooth to other audio devices - like your car for instance. They say a patch is on the way but didn't specify a timeline.

Correction* Found the article - don't know if it speaks to our problem but hopefully the resolution of that problem resolves it for all of us...Fingers crossed...Check out the link below

Google Confirms Bluetooth A2DP Audio Streaming Fix For The 'Next Release' Of Android 4.2
 
I'm with Bell Mobility too. I upgraded to JB awhile ago and I haven't been able to connect to anything regarding bluetooth. It's connected, than no connection. It really sucks. I never had an issue before this upgrade. I'm truly disappointed.
 
So I had the galaxy s2 it worked for my car. I bought t mobile galaxy s3 and the Bluetooth connects to my Nissan altima coupe 2008. I have a full tech pakage with navigation system and everything, and the audio is also garbaged doing a blue tooth call same problem!
 
My 2 weeks old S3 BT doesn't work with my Volvo MY12 BT, but it works with my 2012 Mazda 3 . It's looking for connection and syncing over and over....... non stop. when you double press the home key on the S3. my S3 totally crashed. No light, no respond from any key.I took the battery out and restarted the S3. I am going to take S3 back to the shop tomorrow to check up. But I don't think i will get the right answer from them. S3 is a phone doesn't do what it should do. I should stay with my iphone, at least it works when I need it.:mad:
 
Last edited:
Since upgrading to Jelly Bean from Ice cream sandwich bluetooth on my 2013 BMW X3 keeps disconnecting. Took to dealership and they say it's a problem with Samsung S3... Ugh... Please, Samsung, do something about this! I work out of my car and Verizon said there is no way to go back to the old version.
 
I own the very same car Infiniti G35S Iam having the very same problem you are, with distoration sound
when calling out or incoming calls. I have tired other phones and they all work great. I called the Infiniti bluetooth
department and they said they have recieved alot of calls about the same issues. It is not a problem with the
bluetooth in the car. It defintely a issue with the galaxys3. I got my phone back in october and it worked fine and then
all of a sudden it started making that crazy noise. I called samsung and they were no help at all. They want me to
to send the phone back to them so that they can check it out. I would be with out a phone for two weeks or so. I would
like to know how to roll it back to the 4.0.4 ICS. and hopefully they will fix there jelly bean issue.
So how do you roll back??? HELP:mad:
 
Same exact problem ever since I upgraded to jelly bean with my 2013 BMW. Samsung says the car manufacturer needs to update their bloothtooth technology. It worked just fine with Ice cream sandwich. Better figure it out Samsung.
 
Same exact problem ever since I upgraded to jelly bean with my 2013 BMW. Samsung says the car manufacturer needs to update their bloothtooth technology. It worked just fine with Ice cream sandwich. Better figure it out Samsung.
There are other phones not working. In fact the Nexus 7 supposedly is not working with bluetooth. I don't think it's a Samsung issue. I think it's a Google issue. I just switched my S3 to use Speakerphone when in the car dock instead of bluetooth. It's not the greatest fix but at least I have connectivity when I need it.
 
There are other phones not working. In fact the Nexus 7 supposedly is not working with bluetooth. I don't think it's a Samsung issue. I think it's a Google issue. I just switched my S3 to use Speakerphone when in the car dock instead of bluetooth. It's not the greatest fix but at least I have connectivity when I need it.

How do you make the speakerphone default? Mine always defaults to car audio (which doesn't work); I can change it to the speakerphone on my my but it's a hassle each time. I did go back to the previous version (4.2.1) and bluetooth is working great with my car now.
 
How do you make the speakerphone default? Mine always defaults to car audio (which doesn't work); I can change it to the speakerphone on my my but it's a hassle each time. I did go back to the previous version (4.2.1) and bluetooth is working great with my car now.
I'm using my S3 with the iBolt car dock. It's an option in Car Home Ultra which I use. Sorry I didn't make that clear. Car Home Ultra also has an option to default to bluetooth which I used to use until JB screwed everything up. Well worth the $1.99 in the Play Store.
 
I'm another person adding my woes this thread. My 2010 Renault Megane was working brilliantly when my phone was running 4.0.4.
After the upgrade to 4.1.1 the Bluetooth still connects straight away, but drops out then back in approximately every 30 secs or so, making it unusable. The upgrade to 4.1.2 has made no difference at all, problem still exists. I hope they get their act together with the 4.2 upgrade, but I won't be holding my breathe...
 
The same issues happen a lot on several bluetooth devices. Try removing the device from your paired devices list, reset the bluetooth device, disable the Wi-Fi in the phone then pair!
 
The same issues happen a lot on several bluetooth devices. Try removing the device from your paired devices list, reset the bluetooth device, disable the Wi-Fi in the phone then pair!
I don't want to tell you how many times I've tried that with no improvement. Hopefully others do better.
 
Hello,

I currently have the same issue between my HTC ONE S and SEAT(VAG) Altea 2009/bluetooth integrated to MP3 radio.

Was working fine in ICS when address book was no longer than 100 records.

Symptoms:
Contact list doesn't seem to update complettly.
When placing a call bluetooth hang and connection set up again few seconds later.

Workaround:
Forbid adress book synchronization :-( but then you can call from the phone and use car embedded audio.
Restrict address book in the phone to SIM only with few contact inside: then it works fine!

Conclusions:

My hypothesis currently is that some fields used in Google contacts are not compliant with old systems.
I will try step by step to include contact by contact to sync, hope to identify none complient field...

Does anyone know what was the changes done by google in the adress book with Jelly bean?
 
I have the same problem with my Infiniti. Have a Blackberry Bold and T-Mobile Android Slide which have worked perfectly with the car for years. Complained to T-Mobile who had me jumping through test hoops like everyone else. My new S3 actually worked perfectly the day I activated but then the Bluetooth went south the next day after the automatic android software update. Apparently Samsung and T-Mobile screwed up the last build of Jelly Bean and a number of the bluetooth protocalls dont work now. Android developers have been complaining about it for months. I finally pressed the issue with T-Mobile support who were clueless about this major defect in the operating system. It seems that neither Samsung or T-Mobile wants to acknowledge the bad news and feel that playing dumb wasting customer and tech support time is a better option.

The T-Mobile Tech I was dealing with actually confirmed the bug from links I gave her and documented the problem in the T-Mobile database. They only way to get this fixed to to pressure them will lots of tech support complaints as Samsung does not want to deal with it and in denial. Call TMoble support and insist that they add your complaint to the now documented known issue.
 

Trending Posts

Forum statistics

Threads
956,397
Messages
6,968,051
Members
3,163,538
Latest member
boone