Uconnect dropping calls - Jeep Wrangler Forum

Go Back   Jeep Wrangler Forum > JK Jeep Wrangler Forum > JK General Discussion Forum

Join Wrangler Forum Today


Reply
 
Thread Tools

Please support our sponsors and let them know you heard about them on WranglerForum.com
Old 03-11-2014, 11:54 AM   #1
Jeeper
 
Join Date: Jun 2012
Posts: 290
Uconnect dropping calls

14 JKUR. I push the phone button and say call so and so. It will drop the call several times before it hooks up. So frustrating. If I manually dial the call on the phone it will pick it up and work fine, but the voice prompt system sucks. Any fix?

elToro is offline   Quote
Old 03-11-2014, 11:57 AM   #2
Jeeper
 
Mcrock's Avatar
 
Join Date: Mar 2009
Posts: 298
Background noise maybe
Windows up?
Top on or off?

__________________
'85CJ, '92YJ, '00 TJ, '08 JK, '13 JK, '17 ??
Mcrock is offline   Quote
Old 03-11-2014, 12:02 PM   #3
Jeeper
 
Join Date: Jun 2012
Posts: 290
No. Windows up and top on. Totally quiet. Sometimes it will ring once or twice and sometimes the other person actually picks up the phone, then it drops. So I knows it's calling out, but then it fails. Really annoying.
elToro is offline   Quote
Old 03-11-2014, 12:29 PM   #4
Jeeper
 
Nuke83's Avatar
 
Join Date: Apr 2013
Location: NW of Atlanta
Posts: 772
On my phone, that's the AT&T "feature"
Nuke83 is offline   Quote
Old 03-11-2014, 01:33 PM   #5
Jeeper
 
Join Date: Feb 2013
Posts: 312
Let me guess...you're running an android phone with android 4.3?

I have the same problem. There are a few threads on it, here is one:

Anyone know if Samsung Galaxy S4 or Note 2 is Bluetooth Compatible w/JKU 130 System?


This is a common problem. The uconnect system pings the device to see if there is an open call and the phone is failing to send an active call back to the uconnect, so it drops the call. This is a phone problem, not a uconnect problem.
I think that frankly, the software in your bluetooth unit is too new and the android system isnt working correctly with it.

Hopefully it will be addressed in Android 4.4
__________________
2013 JKU Sahara
nitroz680 is offline   Quote
Old 03-11-2014, 01:34 PM   #6
Jeeper
 
Join Date: Feb 2013
Posts: 312
__________________
2013 JKU Sahara
nitroz680 is offline   Quote
Old 03-11-2014, 01:37 PM   #7
Jeeper
 
mattjopete's Avatar
 
Join Date: Apr 2012
Location: St. Louis Mo
Posts: 564
FWIW I was able to call my wife via a 730N with my 4.4 android device though we didn't talk as we were just testing the functionality.
__________________
'12 JKU COD MW3 Bright Silver Auto 4.10's
'12 JKU Sahara Deep Cherry Red 6-speed 3.21's - Gone
mattjopete is offline   Quote
Old 03-11-2014, 02:20 PM   #8
Jeeper

WF Supporting Member
 
Cshelton323's Avatar
 
Join Date: Oct 2013
Location: Gardner, KS (suburb of KC)
Posts: 124
Mine does the same thing and it is annoying! I thought it had something to do with my clock spring going bad but that got fixed and it still does it! I have the S4 so hopefully it is just an android thing.
__________________
2014 Wrangler Unlimited Sport (Anvil)
Leveling kit, Fuel Revolvers, 33" Nitto Trail Grappler MT, N-Fab Nerf bars(Line-xed)


1942 Willy's MB (own)
2011 Wrangler Unlimited Sport Flame Red (sold)
2014 Wrangler Willy's Edition Hydro Blue (own)
Cshelton323 is offline   Quote
Old 03-11-2014, 02:23 PM   #9
Jeeper

WF Supporting Member
 
Cshelton323's Avatar
 
Join Date: Oct 2013
Location: Gardner, KS (suburb of KC)
Posts: 124
Quote:
Originally Posted by Cshelton323 View Post
Mine does the same thing and it is annoying! I thought it had something to do with my clock spring going bad but that got fixed and it still does it! I have the S4 so hopefully it is just an android thing.
I just looked at my phone and I am running 4.4
__________________
2014 Wrangler Unlimited Sport (Anvil)
Leveling kit, Fuel Revolvers, 33" Nitto Trail Grappler MT, N-Fab Nerf bars(Line-xed)


1942 Willy's MB (own)
2011 Wrangler Unlimited Sport Flame Red (sold)
2014 Wrangler Willy's Edition Hydro Blue (own)
Cshelton323 is offline   Quote
Old 03-11-2014, 02:27 PM   #10
Jeeper
 
mattjopete's Avatar
 
Join Date: Apr 2012
Location: St. Louis Mo
Posts: 564
Quote:
Originally Posted by Cshelton323 View Post

I just looked at my phone and I am running 4.4
KitKat is nothing to be sad about! What phone do you have? It might just be a touchwiz(Samsung) thing.
__________________
'12 JKU COD MW3 Bright Silver Auto 4.10's
'12 JKU Sahara Deep Cherry Red 6-speed 3.21's - Gone
mattjopete is offline   Quote
Old 03-11-2014, 02:39 PM   #11
Jeeper

WF Supporting Member
 
Cshelton323's Avatar
 
Join Date: Oct 2013
Location: Gardner, KS (suburb of KC)
Posts: 124
Quote:
Originally Posted by mattjopete View Post

KitKat is nothing to be sad about! What phone do you have? It might just be a touchwiz(Samsung) thing.
I have the Samsung Galaxy S4. Sprint is the carrier. It is so frustrating to have to place the call 3 or 4 times before it goes through!
__________________
2014 Wrangler Unlimited Sport (Anvil)
Leveling kit, Fuel Revolvers, 33" Nitto Trail Grappler MT, N-Fab Nerf bars(Line-xed)


1942 Willy's MB (own)
2011 Wrangler Unlimited Sport Flame Red (sold)
2014 Wrangler Willy's Edition Hydro Blue (own)
Cshelton323 is offline   Quote
Old 03-11-2014, 02:48 PM   #12
Jeeper
 
Join Date: Feb 2014
Location: Dayton, Ohio
Posts: 208
Same problem. GS3 with 4.3 ...sometimes rings twice then drops. even worse - sometimes it just disconnects the b/t connection, but retains the phone call on the device (does not disconnect!). ...so then who ever you are calling can hear you cuss out your jeep's uconnect. been there.
hypoxic1911 is offline   Quote
Old 03-11-2014, 02:55 PM   #13
Jeeper

WF Supporting Member
 
Cshelton323's Avatar
 
Join Date: Oct 2013
Location: Gardner, KS (suburb of KC)
Posts: 124
. ...so then who ever you are calling can hear you cuss out your jeep's uconnect. been there.[/QUOTE]

Lol! Done that!
__________________
2014 Wrangler Unlimited Sport (Anvil)
Leveling kit, Fuel Revolvers, 33" Nitto Trail Grappler MT, N-Fab Nerf bars(Line-xed)


1942 Willy's MB (own)
2011 Wrangler Unlimited Sport Flame Red (sold)
2014 Wrangler Willy's Edition Hydro Blue (own)
Cshelton323 is offline   Quote
Old 03-11-2014, 05:38 PM   #14
Jeeper
 
reade's Avatar
 
Join Date: Oct 2012
Posts: 430
The best thing I did was to turn U Connect off. Mind was more of a pain in the butt than it was worth.
reade is offline   Quote
Old 03-11-2014, 09:31 PM   #15
Jeeper
 
Join Date: Jun 2012
Posts: 290
I do have a Samsung S3 Droid with Verizon. Come to think of it, just went thru a phone update and never remembered having this problem before. That sucks! Some update! So is there a hack/fix for this? Any way to go back to the old OS?
elToro is offline   Quote
Old 03-12-2014, 07:58 AM   #16
Commercial Member

WF Supporting Member
 
Join Date: Apr 2011
Posts: 2,430
wow nitroz680, I see you beat me to this. I was just scrolling thru to see the comments when I see my response was pretty much already inserted.


Quote:
Originally Posted by nitroz680 View Post
Let me guess...you're running an android phone with android 4.3?

I have the same problem. There are a few threads on it, here is one:

Anyone know if Samsung Galaxy S4 or Note 2 is Bluetooth Compatible w/JKU 130 System?


This is a common problem. The uconnect system pings the device to see if there is an open call and the phone is failing to send an active call back to the uconnect, so it drops the call. This is a phone problem, not a uconnect problem.
I think that frankly, the software in your bluetooth unit is too new and the android system isnt working correctly with it.

Hopefully it will be addressed in Android 4.4
xsdbs is offline   Quote
Old 03-12-2014, 08:00 AM   #17
Commercial Member

WF Supporting Member
 
Join Date: Apr 2011
Posts: 2,430
Voice commands can be an issue if you're used to commands in a different vehicle brand and if you're not using the correct command as well.



Quote:
Originally Posted by elToro View Post
14 JKUR. I push the phone button and say call so and so. It will drop the call several times before it hooks up. So frustrating. If I manually dial the call on the phone it will pick it up and work fine, but the voice prompt system sucks. Any fix?
xsdbs is offline   Quote
Old 03-12-2014, 08:02 AM   #18
Jeeper
 
Join Date: Feb 2013
Posts: 312
Quote:
Originally Posted by xsdbs View Post
wow nitroz680, I see you beat me to this. I was just scrolling thru to see the comments when I see my response was pretty much already inserted.
I should have cited my source, which is you!
__________________
2013 JKU Sahara
nitroz680 is offline   Quote
Old 03-12-2014, 08:14 AM   #19
Commercial Member

WF Supporting Member
 
Join Date: Apr 2011
Posts: 2,430
The Samsung phones didn't have any issues with the Android 4.2.1 & .2 but with the 4.3 update came this "call completed" issue. When you place an outgoing call, Uconnect will ask the phone about the call. The first question to the phone should be answered "call is in set up", then the next question should tell Uconnect if the call is either still in "set up or is active". The phone is responding back with "no active call", so Uconnect thinks there isn't a call and returns to the radio mode.
Verizon will be rolling out the KitKat (4.4) update later this month thru early April which will have the patch to correct this issue. Samsung is aware of the issue and I tested the patch for them with no issues.
No, I can't pass the patch out, I was lucky enough to receive it thru contacts and also had to sign a "Non Disclosure" form. You & others need to just hang tight for a few weeks and in the meantime try initiating the call from the phone itself. I have about 80 - 90% success rate doing it that way.



Quote:
Originally Posted by elToro View Post
I do have a Samsung S3 Droid with Verizon. Come to think of it, just went thru a phone update and never remembered having this problem before. That sucks! Some update! So is there a hack/fix for this? Any way to go back to the old OS?
xsdbs is offline   Quote
Old 03-12-2014, 08:16 AM   #20
Jeeper
 
Join Date: Feb 2013
Posts: 312
XSDBS, good to hear you are confirming that this issue is being addressed in 4.4. I wasnt sure what made it all into the new software and was concerned this issue wasnt going to be addressed.

I'll just hold tight for now...
Thanks
__________________
2013 JKU Sahara
nitroz680 is offline   Quote
Old 03-12-2014, 08:20 AM   #21
Commercial Member

WF Supporting Member
 
Join Date: Apr 2011
Posts: 2,430
no problem. I won't get you for Plagiarism.
Funny thing, my daughter was doing a Jr High paper and forgot to note where she had looked up some information on one item and the teacher took away 2 points for Plagiarism. She had added notes for all the other looked up information and forgot about the one, I was surprised that the teacher didn't just add a note instead of knocking off 2 points.


Quote:
Originally Posted by nitroz680 View Post
I should have cited my source, which is you!
xsdbs is offline   Quote
Old 03-12-2014, 08:25 AM   #22
Commercial Member

WF Supporting Member
 
Join Date: Apr 2011
Posts: 2,430
The BT specs are extremely loosely written which allows people to interpret them differently. Not all BT car kits will ask about the calls in progress so they won't have this issue. That's the case here, the 730N does not query the phone about calls. However the 730N does have it's own issues that some of the other radios don't have. So basically, there is no perfect system yet until the specs get tighter.



Quote:
Originally Posted by mattjopete View Post
FWIW I was able to call my wife via a 730N with my 4.4 android device though we didn't talk as we were just testing the functionality.
xsdbs is offline   Quote
Old 03-12-2014, 08:27 AM   #23
Commercial Member

WF Supporting Member
 
Join Date: Apr 2011
Posts: 2,430
Should be cussing out the phone, it's not a Uconnect issue.




Quote:
Originally Posted by Cshelton323 View Post
. ...so then who ever you are calling can hear you cuss out your jeep's uconnect. been there.
Lol! Done that![/QUOTE]
xsdbs is offline   Quote
Old 03-12-2014, 08:31 AM   #24
Commercial Member

WF Supporting Member
 
Join Date: Apr 2011
Posts: 2,430
Yes, when Verizon releases the KK update, it will contain the patch. Unfortunately Sprint released the KK update too early. They had released it prior to Samsung being able to get them the KK update with the patch included. Due to that timing, the Samsung phones on Sprint will still have the "call Completed" issue till Samsung & Sprint work it out with a new OTA update.



Quote:
Originally Posted by nitroz680 View Post
XSDBS, good to hear you are confirming that this issue is being addressed in 4.4. I wasnt sure what made it all into the new software and was concerned this issue wasnt going to be addressed.

I'll just hold tight for now...
Thanks
xsdbs is offline   Quote
Old 03-12-2014, 08:33 AM   #25
Commercial Member

WF Supporting Member
 
Join Date: Apr 2011
Posts: 2,430
What made it a "pain in the butt" for you? Maybe I can offer some help.




Quote:
Originally Posted by reade View Post
The best thing I did was to turn U Connect off. Mind was more of a pain in the butt than it was worth.
xsdbs is offline   Quote
Old 03-12-2014, 08:33 AM   #26
Jeeper
 
mattjopete's Avatar
 
Join Date: Apr 2012
Location: St. Louis Mo
Posts: 564
Quote:
Originally Posted by xsdbs View Post
Yes, when Verizon releases the KK update, it will contain the patch. Unfortunately Sprint released the KK update too early. They had released it prior to Samsung being able to get them the KK update with the patch included. Due to that timing, the Samsung phones on Sprint will still have the "call Completed" issue till Samsung & Sprint work it out with a new OTA update.
That'll take months!
__________________
'12 JKU COD MW3 Bright Silver Auto 4.10's
'12 JKU Sahara Deep Cherry Red 6-speed 3.21's - Gone
mattjopete is offline   Quote
Old 03-12-2014, 08:42 AM   #27
Commercial Member

WF Supporting Member
 
Join Date: Apr 2011
Posts: 2,430
What makes you think that the BT connection is "disconnected"? Actually that's not what is happening. This issue is a Samsung issue not Uconnect. We must remember what got the update as well as what actually worked prior to the update. These Samsung phones worked fine with the 4.2.1 & 4.2.2 Android versions. The phone mfg's should spend more time testing their updates with the systems that customers already have on the road to find out if there are (or will be) any issues, then fix the issues before releasing updates.
However this really isn't anything new, I mean look at the Automotive industry and how many SW updates they have to come up with after a new Model is released.



Quote:
Originally Posted by hypoxic1911 View Post
Same problem. GS3 with 4.3 ...sometimes rings twice then drops. even worse - sometimes it just disconnects the b/t connection, but retains the phone call on the device (does not disconnect!). ...so then who ever you are calling can hear you cuss out your jeep's uconnect. been there.
xsdbs is offline   Quote
Old 03-12-2014, 08:52 AM   #28
Commercial Member

WF Supporting Member
 
Join Date: Apr 2011
Posts: 2,430
Hopefully not. The only other thing that I can think of is if you recently bought the phone, maybe take it back to Sprint and have them replace it for one that has the older SW version and then don't perform the 4.3 or 4.4 update until they offer a more current version of KK.


Quote:
Originally Posted by mattjopete View Post
That'll take months!
xsdbs is offline   Quote
Old 03-12-2014, 08:54 AM   #29
Jeeper
 
Join Date: Feb 2014
Location: Dayton, Ohio
Posts: 208
Quote:
Originally Posted by xsdbs View Post
What makes you think that the BT connection is "disconnected"? Actually that's not what is happening. This issue is a Samsung issue not Uconnect. We must remember what got the update as well as what actually worked prior to the update. These Samsung phones worked fine with the 4.2.1 & 4.2.2 Android versions. The phone mfg's should spend more time testing their updates with the systems that customers already have on the road to find out if there are (or will be) any issues, then fix the issues before releasing updates.
However this really isn't anything new, I mean look at the Automotive industry and how many SW updates they have to come up with after a new Model is released.
I got it. just making the point the device and uconnect are no longer communicating with each other. Looking forward to the update & hopefully the fix.
hypoxic1911 is offline   Quote
Old 03-12-2014, 09:57 AM   #30
Commercial Member

WF Supporting Member
 
Join Date: Apr 2011
Posts: 2,430



Quote:
Originally Posted by hypoxic1911 View Post
I got it. just making the point the device and uconnect are no longer communicating with each other. Looking forward to the update & hopefully the fix.

xsdbs is offline   Quote
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off




Download our Mobile App

» Featured Product

All times are GMT -5. The time now is 03:25 PM.


User Alert System provided by Advanced User Tagging v3.1.0 (Pro) - vBulletin Mods & Addons Copyright © 2015 DragonByte Technologies Ltd.

Jeep®, Wrangler, Liberty, Wagoneer, Cherokee, and Grand Cherokee are copyrighted and trademarked to Chrysler Motors LLC.
Wranglerforum.com is not in any way associated with the Chrysler Motors LLC