Welcome to the Android Central Forums Create Your Account or Ask a Question Answers in 5 minutes - no registration required!
Page 2 of 7 FirstFirst 12345 ... LastLast
Results 26 to 50 of 151
Like Tree6Likes
  1. #26  

    Default Re: Jelly bean update and bluetooth Calling issue

    It's definitely not a carrier issue. It's something to do with a compatibility issue between 4.1.1 on S3 and the Bluetooth system of Infiniti!!! It's so frustrating because the only way to fix this issue now would be to roll back to ICS which sucks. let's hope that the next update 4.1.2 fixes the issue.

    Has anybody tried the custom ROM CM10 to see if it fixes the problem?
  2. #27  

    Default Re: Jelly bean update and bluetooth Calling issue

    Google has changed the bluetooth stack since 4.1.1 and the issue still remains on 4.1.2. Now I am wondering how this will eventually get resolved. There are probably still serious bluetooth issues in existance with the latest builds that they are doing with the new bluetooth stack. Hopefully this will be resolved in quarter one of next year.
    ma3loom likes this.
  3. #28  

    Default Re: Jelly bean update and bluetooth Calling issue

    I have the exact same issue since my VZ update and my 2010 Audi A4. I contacted Audi and was told that the S3 only works with Audi A4's newer than 2012 which is absurd. Also the latest bluetooth version from Audi is compatible with 4.04. This is extremely frustrating since I have an old bluetooth headset (Plantronics 520) which connected and worked immediately.
  4. #29  

    Default Re: Jelly bean update and bluetooth Calling issue

    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!
  5. #30  

    Default Re: Jelly bean update and bluetooth Calling issue

    Quote Originally Posted by stupage View Post
    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!
    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.
  6. #31  

    Default Re: Jelly bean update and bluetooth Calling issue

    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.
  7. Thread Author  Thread Author    #32  
    ma3loom's Avatar

    Posts
    34 Posts
    Global Posts
    72 Global Posts

    Default Re: Jelly bean update and bluetooth Calling issue

    Quote Originally Posted by socal.mdb View Post
    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.
    That's the usual PR bull they run with any calls. I went and test drove the Audi S4 2013 and had the same issue with my S3 - so its a load of crap. Bluetooth profiles are always backwards compatible, since I started using an old flip phone in my car for the interim (Phone is circa 2001, so i don't know what they are smoking). There has to be a way to get his issue noticed, because I called TMO yesterday and they said there is no knowledge base to date about the issue, which is bs since I've complained numerous times so there should be at least one. I'm going to try and reach out to someone from Android Central and see if they have any idea how to bring this issue to the forefront, since I'm getting the blame game as well. Call samsung they blame Infiniti, who then blame TMO. If anyone has any thoughts too, would be great
  8. #33  

    Default Re: Jelly bean update and bluetooth Calling issue

    Quote Originally Posted by socal.mdb View Post
    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.
  9. #34  

    Default Re: Jelly bean update and bluetooth Calling issue

    Hi-

    Very similar issues with the Verizon Galaxy S 3 Jelly Bean 4.1. 1 and a 2011 Infinity G37 Convertible.

    Pairs normally for voice but cannot pair audio (music player). Voice connections sound normal to me but the other end says it sounds terrible. Performed the hard resets, same issues Verizon blames the car (of course) however Samsung indicated they were aware of some Bluetooth profile issues and took all the details.

    So for now, no Bluetooth in the car until some kind of fix comes along..... Or I put my phone backwards one OS.
  10. #35  

    Default Re: Jelly bean update and bluetooth Calling issue

    I only use Bluetooth for my phone calls as my car doesn't have bluetooth audio. I did a factory reset on Xmas and my prior problems of my bluetooth dropping seems to have mostly disappeared. I did notice that it dropped completely once but came back and the bars don't match the phone (car shows two bars when phone shows five) but is "seems" to be usable. More driving will give more specifics but these are my preliminary results after a factory reset. Seems like a lot of work to fix this problem but now that it's done it seems worth it to me.
  11. #36  

    Default Re: Jelly bean update and bluetooth Calling issue

    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?
  12. #37  

    Default Re: Jelly bean update and bluetooth Calling issue

    Quote Originally Posted by ComputerJAM View Post
    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.
  13. #38  

    Default Re: Jelly bean update and bluetooth Calling issue

    Here is my understanding and my situation. The problem seems to be narrowed to the s3 as someone said a note 2 was unaffected. What happens (seems to be mostly nissan/infiniti) is when you upgrade your os from ics to jb it over modulates for lack of a better term, short version is when you are on a call you can't understand them and they can't understand you. If you roll back to ics (if you are rooted) or if not rooted, have the carrier send you a new or reconditioned phone that has ics, everything works again. Seems to me it may be combination Google/Samsung problem because supposedly the Samsung Note 2 running JB works fine.

    What I know is everything works now on both our phone and although it was a pain in the a$$ to reinstall everything and lose all the settings, it was worth it to be able to talk while driving our 2008 Infiniti G37s. The 2012 Toyota Tundra worked fine both before and after the upgrade. Hope that helps.
  14. #39  

    Default Re: Jelly bean update and bluetooth Calling issue

    My problems with the Bluetooth began immediately after the forced update by Verizon. Not Samsung and Not Google. It would not maintain a connection with my 2010 Touareg, a VW that is part of the VW-Audi-Porsche Group. Today I stopped in at a Verizon store, a company store not a franchise, and they fooled around with it and pushed a lot of buttons and came to the point that by removing the battery and restarting S3 it would be better. It took it several tries but it did finally pair up again. But it is still acting strange and when I get a call and answer it, there is nothing and then after some time I will hear the person talking.

    The other solution they offered was to do a factory reset which means that you have to back up everything and then reinstall all the applications you have and hope the data gets back in. They offered to get me a "new" phone but at some point the new software would make it back in. So what is the point.

    The other not noticed before item is this "Driving Mode" that shows up in the top banner. What is that all about and does it have anything to do with bluetooth?
  15. #40  

    Default Re: Jelly bean update and bluetooth Calling issue

    Quote Originally Posted by ansextra View Post
    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 have a SG3 running 4.1.1 on TMob, I also have an Audi S5 2013, Ive had no problem whatsoever, wife tells me calls are clear with no dropped calls or breakups.
    Sorry to mess things up, but now Ive got my fingers crossed nothing goes bad.
  16. #41  

    Default Re: Jelly bean update and bluetooth Calling issue

    Quote Originally Posted by ChrisS#AC View Post
    I have a SG3 running 4.1.1 on TMob, I also have an Audi S5 2013, Ive had no problem whatsoever, wife tells me calls are clear with no dropped calls or breakups.
    Sorry to mess things up, but now Ive got my fingers crossed nothing goes bad.
    You're not messing things up. More power to you! Like I said a factory reset seems to have solved most of my bluetooth issues. Although things aren't perfect they are at least working.
  17. #42  

    Default Re: Jelly bean update and bluetooth Calling issue

    Same problem with my 2009 Audi. Bluetooth worked fine with old S3 Android Version software. 4.1.1 now causes real problems. This really stinks as I am in sales and on the road LOTS. I can't be without the bluetooth feature.
  18. #43  

    Default Re: Jelly bean update and bluetooth Calling issue

    Quote Originally Posted by Audi Dan View Post
    Same problem with my 2009 Audi. Bluetooth worked fine with old S3 Android Version software. 4.1.1 now causes real problems. This really stinks as I am in sales and on the road LOTS. I can't be without the bluetooth feature.
    This page AUDI - Bluetooth compatible devices shows the latest version of bluetooth supported by Audi. For now it's still showing the following as the latest firmware officially supported:
    Tested firmware: Android 4.0.3, I535VRLD5
    Last change: 08/31/2012

    As I said it seems to be working much better for me after a factory reset although it is not perfect. I can at least make calls even though the signal meter on my dash does not agree with my phone.
  19. #44  

    Default Re: Jelly bean update and bluetooth Calling issue

    How do I do a Factory Reset? Sorry about needing to ask, but I am not up to speed on these phones.
  20. #45  

    Default Re: Jelly bean update and bluetooth Calling issue

    Quote Originally Posted by Audi Dan View Post
    How do I do a Factory Reset? Sorry about needing to ask, but I am not up to speed on these phones.
    System settings -> Backup and Reset.
    Just understand that a factory reset will wipe EVERYTHING from your phone and it will be just like the day you got it (except with Jellybean instead of ICS. This is the most drastic measure that can be taken but if you go to Verizon or call Samsung they will most likely make you do this before going on to next steps. If your contacts and calendars are sync'd with Google or your Exchange server they will come back once you re-establish those accounts. You should try to back up as much as you can to somewhere before doing the factory reset. Also, it may or may not help. Sorry to give you all the risks but you need to be aware before taking the factory reset step... Good luck!
  21. #46  

    Default Re: Jelly bean update and bluetooth Calling issue

    Thanks!
  22. #47  

    Default Re: Jelly bean update and bluetooth Calling issue

    I have a similar problem. I have a moto razr maxx xt912 with ICS and now pair and connect to my 07 Nissan Versa bluetooth but when I call or receive can only talk on the phone not car system, even though I answer or place the call with the system controls. Level Three at motorola says wait and see if Jellybean update fixes the issue. They know about it even though it took to level 3 to get an answer. It is a google issue not the phone, or carrier. They both throw their hands in the air and say wait and see. I am fed up.
  23. #48  
    wezra's Avatar

    Posts
    114 Posts
    Global Posts
    241 Global Posts

    Default Re: Jelly bean update and bluetooth Calling issue

    My story is a bit different, but possibly helpful in understanding the issue. I had a T-Mobile HTC One S running ICS. I got a 2013 Volt with the full Nav package which includes Bluetooth. In the case of GM they recently turned over the support of Bluetooth to On-Star. GM stopped doing the software builds themselves for all GM brands. Long story, short... I had the same connect/disconnect issues + garbled communication problems many of you are having with your GS3's on jelly bean. I worked very closely with the special GM Volt customer service team on the issue. What they determined is that On-Star was using older Bluetooth protocols that worked only with certain carriers versions of ICS. For example, it was comparable with the AT&T HTC One X, but not the Bluetooth software on the T-Mobile One S. On-Star then updated the Bluetooth software via an OTA update and my One S began to work perfectly. Clearly it was an issue with the software On-Star was using.

    Fast forward two months and I now have upgraded to a GS3 that came pre-loaded with 4.1.1. I am having absolutely no issues with the Bluetooth program in the Volt. In fact I have a TecTile setup in the car and it is set to turn Bluetooth on and off in the car. Again, no issues with pairing and loading my contacts into the system on the car. My feeling is, based on my very frustrating experience with the One S and On-Star, the issues lie with the automobile manufacturers, or whom ever builds their Bluetooth software for their cars, and not the phone manufacturers or carriers. It is the automobile manufacturer's responsibility to insure the Bluetooth protocols they are using are comparable with the various OS builds...not the other way around.
  24. #49  

    Default Re: Jelly bean update and bluetooth Calling issue

    I am having exactly the same issue: after the upgrade, the connection is unusable. I tried my old Droid, and it worked just fine. There is no reason to allow this to go on, as it should be backward compatible. ( I have a 2009 Nissan Altima Coupe that I certainly like more than a stupid phone. I tried to insert a clause in my contract that stipulated if they changed the system to render features inoperable, my contract would be void, but I could have had better luck trying to get an ATM to bake cookies...)
    Anyway, if they don't fix it, I plan to let everyone I know who is considering a phone to be wary of the Samsung...
  25. #50  

    Default Re: Jelly bean update and bluetooth Calling issue

    Quote Originally Posted by IAPNMC View Post
    I am having exactly the same issue: after the upgrade, the connection is unusable. I tried my old Droid, and it worked just fine. There is no reason to allow this to go on, as it should be backward compatible. ( I have a 2009 Nissan Altima Coupe that I certainly like more than a stupid phone. I tried to insert a clause in my contract that stipulated if they changed the system to render features inoperable, my contract would be void, but I could have had better luck trying to get an ATM to bake cookies...)
    Anyway, if they don't fix it, I plan to let everyone I know who is considering a phone to be wary of the Samsung...
    I could be mistaken but I don't believe the problem is a Samsung issue. From what I've seen it's a Jellybean issue.
Page 2 of 7 FirstFirst 12345 ... LastLast

Similar Threads

  1. Major graphics issues since jelly bean update.
    By domdthereal in forum Sprint Galaxy S3
    Replies: 12
    Last Post: 02-26-2013, 09:13 PM
  2. Replies: 18
    Last Post: 12-17-2012, 01:22 PM
  3. Replies: 10
    Last Post: 11-12-2012, 05:45 AM
  4. Questions about Jelly Bean OTA and root access
    By fender7217 in forum Google / Samsung Galaxy Nexus
    Replies: 9
    Last Post: 07-11-2012, 08:46 PM
  5. 1st day Navigation and phone call issue - no sound
    By adiapp in forum Verizon Galaxy Nexus
    Replies: 0
    Last Post: 12-16-2011, 05:47 PM

Posting Permissions