robtuck
New member
I have an 08 G37 and having the same issue after todays JB update. I tried in my BMW 550 and MB ML450 - no problems. I believe this is a problem with the Galaxy S3 update not the carrier for sure!
I've spoken to Samsung and they say it's an Audi (in my case) issue. I have spoken to Audi and they won't promise anything since my car is apparently "old" after two years. This is extremely frustrating as I make business calls from the car at times and need them to sound clear.I have the exact same issue. I have a Samsung Galaxy S3 on Verizon and a 2010 VW Tiguan. When I drove to work in the morning the bluetooth connection on my S3 was fine. I updated to Jelly Bean while at the office and when I drove home from work it could not hold a BT connection for more than 30 seconds. It also does not import my contacts and calls, which were in there prior to the Jelly Bean update. Very frustrating. Samsung has to iron this out quickly!
Update.
After speaking with Samsung customer service and being told it was not their problem, that AT&T accepted the software and that it is HIGHLY unlikely the issue will be address in any future software updates and they can't possibly ensure that the phone will work with all cars (even though the last version did), I contacted AT&T again.
They sent us two new phones with ice cream sandwich and everything is back to normal.
With Verizon sooner or later the update forces itself to install. I would assume that's the same with all carriers. To me a carrier sending phones with an outdated OS is a bandaid not a fix.Update.
After speaking with Samsung customer service and being told it was not their problem, that AT&T accepted the software and that it is HIGHLY unlikely the issue will be address in any future software updates and they can't possibly ensure that the phone will work with all cars (even though the last version did), I contacted AT&T again.
They sent us two new phones with ice cream sandwich and everything is back to normal.
For me it has to do with Audi since I use their built-in bluetooth to make and receive calls while in the car. According to Audi's website the bluetooth driver they include is only certified to work with Android 4.04... In my mind it's partly Samsung's issue because they included the driver without thoroughly testing it with their version of Android. It's partly Audi's issue since they haven't updated the driver yet. And, of course, it's Google's issue for releasing the driver in the first place.I'm not sure I'm following the direction this thread is going.
I too, am having some bluetooth issues with my GS3 Tmobile with 4.1.1 and a Plantronics headset. The headset also connects simultaneously to my work Blackberry 9930.
Anyhow, you guys are saying that after you updated to 4.1 the bluetooth issues started to appear. Then some of you are saying that when you rolled back to ICS 4.0 the problems stopped.
What does this problem have to to with Audi, BMW or any other car manufacturer? and what does it have to do with Samsung, or Tmobile or AT&T? Besides them providing an update from Google.
It seems like the fingers should be pointed at the OS maker, in this case Google, since they broke it with the update. Que no?
For me it has to do with Audi since I use their built-in bluetooth to make and receive calls while in the car. According to Audi's website the bluetooth driver they include is only certified to work with Android 4.04... In my mind it's partly Samsung's issue because they included the driver without thoroughly testing it with their version of Android. It's partly Audi's issue since they haven't updated the driver yet. And, of course, it's Google's issue for releasing the driver in the first place.