Jelly bean update and bluetooth Calling issue

[mx337]

First let me say that this thread seems to be about two (2) different problems under the same heading of "Problems with Samsung S3/Jellybean/Bluetooth." One problem is dropped bluetooth connection(s) and the other problem is static/noise/garbled sound on stable, connected, OEM in-car bluetooth audio systems. My problem is in the latter category. I have a 2009 Bentley GTC; everything worked fine with my HTC Droid. Bought a new Samsung S3 and it too worked fine -- for two days! Then static/noise/garbled sound (people on other end of calls either got noise or nothing at all); I assume the S3 updated and that's when the trouble began. I went through all the steps with Tmo and Samsung and tried three different S3's from the Tmo store but they all did the same thing, every other brand of phone that was paired with the car worked fine. I finally had the Tmo store give me a Google Nexus 4 which I don't like as well as the S3, but it pairs up in my car and there are no bluetooth problems at all. So clearly the problem (the static/noise one anyway) is squarely in Samsung's lap. Samsung should be able to figure out what they've altered or over-layed in the basic Android OS that is causing the problem and fix it.

 

[oube00]

Hi guys,

I'm still having the same issue of distorted phone audio quality via car Bluetooth in Samsung Galaxy S3 after updating to jellybean 4.1.1. It's been a while now! i was doing some research about this issue today and found this https://code.google.com/p/android/issues/detail?id=41628
it seems like there is a workaround that worked for a couple guys (#63) I haven't tried it yet but will definitely do on the way back home later. Hopefully that will help!

Anybody has tried installing a custom ROM to see if it fixes the issue?

Thanks,

 

[lodaka]

Hi guys,

I'm still having the same issue of distorted phone audio quality via car Bluetooth in Samsung Galaxy S3 after updating to jellybean 4.1.1. It's been a while now! i was doing some research about this issue today and found this https://code.google.com/p/android/issues/detail?id=41628
it seems like there is a workaround that worked for a couple guys (#63) I haven't tried it yet but will definitely do on the way back home later. Hopefully that will help!

Anybody has tried installing a custom ROM to see if it fixes the issue?

Thanks,

I am running Galaxy S2 on Cyanogenmod 10.1, which is based on (the last version I tested) 4.2.2. Bluetooth pairs and connects but no audio for me. From my research, I found out that Google decided to abandon whatever Bluetooth drivers (stack?) that they were using before 4.2.1 (4.2.1 is the version that started this whole mess), and this is causing some incompatibility issues with some (not all) devices -- and this issue manifests itself in different ways, i.e. .garbled audio, dropped pairing and no audio, etc. Version 4.2.2 was supposed to fix this (and improve on) Bluetooth issue but sadly at least for me 4.2.2. is not the answer yet.

I went back to Cyanogenmod 10 (based 4.1.2) which is working fine. Every now and then, I try installing 4.2.2 (when there is a new nightly out for Cyanogenmod 10.1) but no luck yet.

Based on my experiences and research, I still think it's Google's issue and Samsung has no control over this.

 

[Jim Culver]

I just purchased a 2013 Honda CRV. Same issue. Signal dropped and reconnects every 30 seconds.
Does anyone have a fix for this?

 

[ansextra]

I just purchased a 2013 Honda CRV. Same issue. Signal dropped and reconnects every 30 seconds.
Does anyone have a fix for this?

An earlier message suggesting not syncing contacts with the car has worked for me.

 

[alpaslan1977]

I've KIA SOUL. After Jelly bean update, my Galaxy Note can make only 1 call over bluetooth. when i tried to make a second call, the car loses the connection. Then i have off my bluetooth over my phone and again on. But this can not be call as a SOLUTION ! Now I'll try some other extra bluetooth apps for my phone on googleplay.

 

[JW Park]

My cell phone is Verizon Galaxy Nexus. The software has recently been upgraded to JB 4.2. Everything was OK except for Bluetooth phone connection with my 2006 BMW 530i. Connection is made to the car, but somehow the Galaxy phone doesn't allow the car's access to the phone's Contact List or Call History. Making a call by dialing a number or receiving a phone call is OK. I visited 2 Verizon stores, but it was not very helpful. Does anyone have the same problem and answers to the problem?

JW Park

 

[ma3loom]

So after waiting as long as I could wait with TMO to solve the whole bluetooth issue (which btw seems to now encompass all forms of car bluetooth issueson this forum) I decided to root my phone and flash the Liquid Smooth Jelly Bean rom. As soon as I did that I tested the bluetooth with my car and it works perfectly. Also, now that I've experienced something outside of touchwiz (Samsung's furnishing on top of android) I think I'm going to wait for the next Nexus. The base vanilla experience is so much better and I have to say, if you want to get bluetooth on your phone definitely flash the Liquid Smooth. I unplugged my phone at 9 am and its almost midnight and I'm at 60% battery. Anyway, not trying plug roms really but at this point until 4.2.2 comes out I think that's the only solution. I might flash back later to Samsung when they reach 4.2.2 but I'm really loving this rom.

good luck

 

[ma3loom]

My cell phone is Verizon Galaxy Nexus. The software has recently been upgraded to JB 4.2. Everything was OK except for Bluetooth phone connection with my 2006 BMW 530i. Connection is made to the car, but somehow the Galaxy phone doesn't allow the car's access to the phone's Contact List or Call History. Making a call by dialing a number or receiving a phone call is OK. I visited 2 Verizon stores, but it was not very helpful. Does anyone have the same problem and answers to the problem?

JW Park

I think you're confusing phones here for some reason. the Nexus is an LG, while the Galaxy is a Samsung. Although on both cases doesnt really matter if it's trying to read your phone book. I'd repair the phone with the car, if you haven't already. You should get a prompt asking you to sync contacts, if its anything like the Porsche bluetooth system.

 

[oube00]

Thanks for the tip. I'm tired of touchwiz anyway, I was just waiting to confirm that Custom ROMs fix this issue. I will try Liquid Smooth this weekend.
Thanks

 

[nataSofCols]

My cell phone is Verizon Galaxy Nexus. The software has recently been upgraded to JB 4.2. Everything was OK except for Bluetooth phone connection with my 2006 BMW 530i. Connection is made to the car, but somehow the Galaxy phone doesn't allow the car's access to the phone's Contact List or Call History. Making a call by dialing a number or receiving a phone call is OK. I visited 2 Verizon stores, but it was not very helpful. Does anyone have the same problem and answers to the problem?

JW Park

I think you're confusing phones here for some reason. the Nexus is an LG, while the Galaxy is a Samsung. Although on both cases doesnt really matter if it's trying to read your phone book. I'd repair the phone with the car, if you haven't already. You should get a prompt asking you to sync contacts, if its anything like the Porsche bluetooth system.

Samsung made the Galaxy Nexus last year. LG makes the newer Nexus 4. I have the older Galaxy Nexus from Verizon myself.

JW Park, I'm having the same issue of my bluetooth system not being able to import contacts. Usually I can just turn the bluetooth off and on again on the phone to resolve, sometimes I have to power the phone off. I've got a 2013 Accord, so this leads me to believe that the phone is more likely the issue than the car. I didn't have my car for long before I got the update, so I wasn't sure if this was an issue that just hadn't surfaced initially or if it was from the update.

 

[dookieshooter]

I have a Skyrocket that just took the JB update and now my G35S (07) has problems. Before that, the skyrocket was absolutely perfect on BT. I've tried deleting the pairings, rebooting, etc... but nothing seems to work. The skyrocket is the first phone that worked perfectly with my car, and now... junk. I'm thinking of trying a factory reset, but I doubt it will do me any good.

 

[ansextra]

I have a Skyrocket that just took the JB update and now my G35S (07) has problems. Before that, the skyrocket was absolutely perfect on BT. I've tried deleting the pairings, rebooting, etc... but nothing seems to work. The skyrocket is the first phone that worked perfectly with my car, and now... junk. I'm thinking of trying a factory reset, but I doubt it will do me any good.

Try not sync'ing your phone clients to your car bluetooth. That has worked for me.

 

[dookieshooter]

I didn't sync any contacts this go around. still no luck.

 

[ma3loom]

I didn't sync any contacts this go around. still no luck.

dookie

Yeah you've got the problem we all have. The only solution I've found is rooting your phone and installing a custom rom. I did that with my TMO S3 and now my bluetooth works fine in my G35 '07. If you're willing to root and are tech savvy its a pretty painless process. That's the only work around that I've heard so far. Also the custom roms give awesome battery life so I'm happier than I was with stock carrier OS

 

[djshotty]

Oh Thank the stars there's someone talking about this issue with JB ROMs!!! I'm running SlimBean 4.0.4 on my i9100 (Galaxy S2) simply because every time I throw anything Jellybean on it, I lose the ability to hear phone call audio over my Eclipse branded head unit in my 1994 model Mazda. Like everyone else, never had an issue with Froyo, Ginger and IceCream ROMs (stock or custom) until now, and when I am running a JB ROM, I can still play music through the car system (Google Music Player) and the phone pairs without any other drama beside the calling issue. From a heap of reading about this around the place (this forum, XDA and others) I'm confident the 4.2.2 update hasn't fixed the a2dp fault. GRRRR!!!

 

[dookieshooter]

dookie

Yeah you've got the problem we all have. The only solution I've found is rooting your phone and installing a custom rom. I did that with my TMO S3 and now my bluetooth works fine in my G35 '07. If you're willing to root and are tech savvy its a pretty painless process. That's the only work around that I've heard so far. Also the custom roms give awesome battery life so I'm happier than I was with stock carrier OS

Thanks man. I'm more than tech savvy. I've rooted, rom'd, etc... in the past. I just was trying to keep this particular phone stock-ish as possible. I'm going to factory wipe tonight to see if that clears anything up. My guess is not. Then I'll look into roms.

 

[mmohn01]

I used to work for at&t, and I had a customer with a 2005 BMW with the same bluetooth issue. The dealer blamed the phone. I told him to go to the dealership to see if there were any updates thru could install for his bluetooth. Again, they blamed his phone (updates are free and they make no money from the customer for doing them). He called me from the dealership and I told him to insist that they do the update or tell them he would not be back to buy his next car. They did the update and voil?. .... it worked perfectly. So, I suggest taking the card in for a software update to see if that rectified the issue.

Sent from my SAMSUNG-SGH-I317 using Android Central Forums

 

[dookieshooter]

I used to work for at&t, and I had a customer with a 2005 BMW with the same bluetooth issue. The dealer blamed the phone. I told him to go to the dealership to see if there were any updates thru could install for his bluetooth. Again, they blamed his phone (updates are free and they make no money from the customer for doing them). He called me from the dealership and I told him to insist that they do the update or tell them he would not be back to buy his next car. They did the update and voil?. .... it worked perfectly. So, I suggest taking the card in for a software update to see if that rectified the issue.

Sent from my SAMSUNG-SGH-I317 using Android Central Forums

Infiniti and BT updates don't go well together ( at least on models before 2009/2010 ), as in "they don't have any"

 

[Gloriosa]

So after waiting as long as I could wait with TMO to solve the whole bluetooth issue (which btw seems to now encompass all forms of car bluetooth issueson this forum) I decided to root my phone and flash the Liquid Smooth Jelly Bean rom. As soon as I did that I tested the bluetooth with my car and it works perfectly. Also, now that I've experienced something outside of touchwiz (Samsung's furnishing on top of android) I think I'm going to wait for the next Nexus. The base vanilla experience is so much better and I have to say, if you want to get bluetooth on your phone definitely flash the Liquid Smooth. I unplugged my phone at 9 am and its almost midnight and I'm at 60% battery. Anyway, not trying plug roms really but at this point until 4.2.2 comes out I think that's the only solution. I might flash back later to Samsung when they reach 4.2.2 but I'm really loving this rom.

good luck

2 quick questions....

1) Do you have a URL to the Liquid Smooth ROM (yours is not the 1st post I've read that says it's great) ?

2) What are the consequences of rooting a phone (I've never been clear and I know carriers try and scare you)? I'm a programmer - so the technical side isn't an issue - just not sure if I can go back to stock ROM and unrooted staus?

Thanks in advance!