Jeep Wrangler Forum banner

1 - 20 of 54 Posts

·
Registered
Joined
·
1,259 Posts
Discussion Starter #1
For starters I have a 2013 that came with 130N with Uconnect/connectivity package. I synced my phone and it worked great with the 130N. I pulled the 130N and put in an RBZ and, as expected, the uConnect didn't change so if I pushed the phone button it said "iPhone ready" and I could tell it to call so and so. Work perfect until a week or so ago when I pushed it and gave the command but it interrupted me saying "available commands are.... etc... " telling me all the options I could say. It beeped to allow another command and I told it something for which it ended up interrupting me again telling my options. Like it wasn't hearing me or something. I tried calling directly from my phone while it was linked (showed the battery and antenna status on screen) and bluetooth active on the phone. For 30 seconds or so the audio of the person I called came thorugh the speakers as it should be it was pretty clear after a couple "hello's" that the person wasn't hearing me well until I put my phone to my head and talked into the phone. I hit "phone" on my phone to transfer audio to the handset and that worked. I finished the call on the phone and tried again with the handsfree button. Same routine of ignoring me and telling me the available options.
I erased uConnect from my phone's bluetooth menu figuring I would just re-set it up. Now when I push the phone button it still ignores me and won't go into the setup menu.

Should I pull the battery and see if a reset helps or does it sound like another problem?
 

·
Commercial Member
Joined
·
2,013 Posts
The first thing I'd try is rebooting the phone. Press and hold the power & home buttons on the phone until the white Apple appears, then release them. The phone will now reboot. Then try re-pairing the phone. I have the 4S & the 5, both have to be rebooted a couple times a month for issues other than BT also. You should also periodically check your APPS to make sure they're all closed. (press the home button twice and you'll see all the APPS that you've been using. Then press and hold the home button for a couple seconds till the red(-) is displayed, now start pressing the icons to close them.





For starters I have a 2013 that came with 130N with Uconnect/connectivity package. I synced my phone and it worked great with the 130N. I pulled the 130N and put in an RBZ and, as expected, the uConnect didn't change so if I pushed the phone button it said "iPhone ready" and I could tell it to call so and so. Work perfect until a week or so ago when I pushed it and gave the command but it interrupted me saying "available commands are.... etc... " telling me all the options I could say. It beeped to allow another command and I told it something for which it ended up interrupting me again telling my options. Like it wasn't hearing me or something. I tried calling directly from my phone while it was linked (showed the battery and antenna status on screen) and bluetooth active on the phone. For 30 seconds or so the audio of the person I called came thorugh the speakers as it should be it was pretty clear after a couple "hello's" that the person wasn't hearing me well until I put my phone to my head and talked into the phone. I hit "phone" on my phone to transfer audio to the handset and that worked. I finished the call on the phone and tried again with the handsfree button. Same routine of ignoring me and telling me the available options.
I erased uConnect from my phone's bluetooth menu figuring I would just re-set it up. Now when I push the phone button it still ignores me and won't go into the setup menu.

Should I pull the battery and see if a reset helps or does it sound like another problem?
 

·
Build Thread Queen
Joined
·
13,193 Posts
Same routine of ignoring me and telling me the available options
Is one of those options list phones? Is your phone still contained in the list? You should have given it a name when you connected it the first time, i.e. Joe's phone or Fred's iPhone.

If your phone is still listed, have you tried to delete it and then re-pair it?
 

·
Registered
Joined
·
1,259 Posts
Discussion Starter #5
Is one of those options list phones? Is your phone still contained in the list? You should have given it a name when you connected it the first time, i.e. Joe's phone or Fred's iPhone.

If your phone is still listed, have you tried to delete it and then re-pair it?
didn't get a chance to pull the battery but it's 100% the radio not the phone. When you push the voice control button or phone button it pretty much ignores anything I say, whether it have to do with the phone or any other function voice command should work for. This would seem to prove it's the radio so one of these days I am going to pull a battery terminal and see if a reset on the Jeep does the trick.
 

·
Commercial Member
Joined
·
2,013 Posts
Wouldn't be the radio, Uconnect is a separate module of the radio. Now as for Uconnect listening to what you're saying, if the command isn't what is supported then you'll get a "misrecognition" reply or sometimes even just a end beep. Would you mind making a short video of you trying to use the system and post it? This may be helpful for assisting you.




didn't get a chance to pull the battery but it's 100% the radio not the phone. When you push the voice control button or phone button it pretty much ignores anything I say, whether it have to do with the phone or any other function voice command should work for. This would seem to prove it's the radio so one of these days I am going to pull a battery terminal and see if a reset on the Jeep does the trick.
 

·
Registered
Joined
·
42 Posts
I am having the same symptoms.

I push the phone button, the radio responds "Uconnect Ready" then list the available options. I am trying to enter "Setup".

The radio does not respond at all to my voice commands, not even "unrecognized". It just proceeds to list the available options again.

When I first got the Jeep it worked fine, I was able to pair my phone without problem. I have since factory reset my phone and have to pair it again but the radio is not responding, it is as if it doesn't hear me.

I just tried resetting the radio, I pulled the battery for 20 minutes. Reconnected it and still the same behavior.

Any ideas? Were you able to get yours fixed? Thanks for any help. I figure if I can get it to work in the driveway it would be better than having to sit at the dealer for something silly.
 

·
Commercial Member
Joined
·
2,013 Posts
One of the things that I see that causes a similar issue is when people don't wait for the exit beep. If you start talking before you hear the beep, no system will get anything correct. I originally ran across this issue while training UAW workers how to diagnose electrical failures at the Mustang plant. These guys would change out parts and have the same issue, then I asked them to show me how they were trying to test the system. The system isn't into the "listen" mode until after the exit beep.

Steps taken should be:
1) press and release the Uconnect phone button and say "set up, phone pairing, pair phone (all in one unrushed sentence),
2) Then just follow the prompts after you hear the exit beeps.



I am having the same symptoms.

I push the phone button, the radio responds "Uconnect Ready" then list the available options. I am trying to enter "Setup".

The radio does not respond at all to my voice commands, not even "unrecognized". It just proceeds to list the available options again.

When I first got the Jeep it worked fine, I was able to pair my phone without problem. I have since factory reset my phone and have to pair it again but the radio is not responding, it is as if it doesn't hear me.

I just tried resetting the radio, I pulled the battery for 20 minutes. Reconnected it and still the same behavior.

Any ideas? Were you able to get yours fixed? Thanks for any help. I figure if I can get it to work in the driveway it would be better than having to sit at the dealer for something silly.
 

·
Registered
Joined
·
42 Posts
Thanks, makes sense but no dice. Tried right after the first beep and again after all options were listed.

Looks like my issue has to do with all the voice commands, not just phone related. Tried the voice control to change the radio and had the same results. No acknowledgement of my command. Frustrating, because it worked great previously.

From what I'm reading could be as easy as making sure the mic is still connected or swapping out the Uconnect module.
 

·
Commercial Member
Joined
·
2,013 Posts
hmm, you can check the mic connection in the drivers side "A" pillar. I wouldn't suggest swapping the part out because I honestly don't think that's where the issue is. Would it be possible to make a short video of your attempting to use the VR commands and post it for me to view?


Thanks, makes sense but no dice. Tried right after the first beep and again after all options were listed.

Looks like my issue has to do with all the voice commands, not just phone related. Tried the voice control to change the radio and had the same results. No acknowledgement of my command. Frustrating, because it worked great previously.

From what I'm reading could be as easy as making sure the mic is still connected or swapping out the Uconnect module.
 

·
Registered
Joined
·
42 Posts
Hey thanks for the help and ideas. Have some more info, I think the Uconnect module itself is flaky.

I tried again last night to pair my phone and voila it paired no problem, was able to make a call. I thought everything was back to normal.

I get in the Jeep this morning and nothing, it doesn't respond anymore. Another thing I notice is that now that my phone is paired the bluetooth icon should light up when connected and it's not connected. I confirmed this by going to bluetooth settings, Uconnect is listed but says not connected.

Might take a look behind the dash this weekend, maybe a wire is loose to the module. Probably not, but can't hurt.

So we'll see. I'll probably wind up getting the dealer to look at it. I don't use the phone often so it's not a huge deal, but from what I understand the USB port in the console is part of the Uconnect. If that stops working that would be bad, I use that all the time.
 

·
Registered
Joined
·
4,136 Posts
Dang. It is starting to sound like the module now. Did you ever disconnect the battery for a while? Maybe the Canbus just needs an attitude adjustment.


Bob K.
 

·
Registered
Joined
·
42 Posts
In an attempt to fix this I disconnected the battery Monday for about 20 minutes. Didn't work at first but surprised me last night.

Oh well, can't use the phone with the doors off anyway. :thumb: Unless something else stops working, I'll worry about it in the fall.

Thanks guys!
 

·
Commercial Member
Joined
·
2,013 Posts
@ axeman628,
What phone do you have and what network is it on? Also, I looked and didn't see the year of the vehicle or which radio you have.





In an attempt to fix this I disconnected the battery Monday for about 20 minutes. Didn't work at first but surprised me last night.

Oh well, can't use the phone with the doors off anyway. :thumb: Unless something else stops working, I'll worry about it in the fall.

Thanks guys!
 

·
Registered
Joined
·
1,259 Posts
Discussion Starter #15
My update on this issue.

Jeep came with the 130n which phone and bluetooth worked perfectly.
I pulled the 130 for a second hand 430RBZ, bluetooth (as it should) continued to work flawlessly without any further setup.
IT BROKE (acted like I don't exist....and can't hear me)

I pulled battery for 30 or more minutes and no dice. Same behavior as the poster above noted with the same kind of attempt.

I pulled the 430RBZ for the original 130n.
130n (the original) fired right up without a need for a security code (I thought all '13's required a code) but it's still deaf or at least acting deaf.

It's got to be the uConnect module or a crap microphone wire. Maybe pinched or cut someplace as a result of just riding around/vibration/horrible quality control on how they run it/etc... I'm guessing uConnect module is junk but either way it pisses me off.

I am calling my dealer tomorrow to bring it in. I do use the phone in the Jeep and it's really irritating.
 

·
Registered
Joined
·
42 Posts
@xsdbs
Jeep is a 2013 with the 130S/RES, my phone is a Galaxy S3.

I used to have my old iPhone paired for audio streaming and that worked too.

Current situation is the same as before, Uconnect doesn't acknowledge any commands no matter how I try to talk to it. I took the phone out of the equation and tried other voice control commands and they don't work either.
 

·
Registered
Joined
·
42 Posts
My update on this issue.

Jeep came with the 130n which phone and bluetooth worked perfectly.
I pulled the 130 for a second hand 430RBZ, bluetooth (as it should) continued to work flawlessly without any further setup.
IT BROKE (acted like I don't exist....and can't hear me)

I pulled battery for 30 or more minutes and no dice. Same behavior as the poster above noted with the same kind of attempt.

I pulled the 430RBZ for the original 130n.
130n (the original) fired right up without a need for a security code (I thought all '13's required a code) but it's still deaf or at least acting deaf.

It's got to be the uConnect module or a crap microphone wire. Maybe pinched or cut someplace as a result of just riding around/vibration/horrible quality control on how they run it/etc... I'm guessing uConnect module is junk but either way it pisses me off.

I am calling my dealer tomorrow to bring it in. I do use the phone in the Jeep and it's really irritating.
I'm curious to see what they do for you. Good luck, keep us posted.
 

·
Registered
Joined
·
13 Posts
My JKU is 3 weeks old and I haven't had an issue whatsoever but I ran into this issue this evening. I've tried resetting my phone-Did anyone ever pinpoint how to resolve this??
 

·
Commercial Member
Joined
·
2,013 Posts
I am seriously doubting that it's the module and leaning more to the mic. As for the mic wire harness, it's embedded into the main dash harness, comes out on the drivers side and up the drivers "A" pillar.

What seems odd is that it worked till you pulled out the radio which the mic isn't wired to. It's connected to the Uconnect module is behind the HVAC control head below the radio.

Jeep came with the 130n which phone and bluetooth worked perfectly.
I pulled the 130 for a second hand 430RBZ, bluetooth (as it should) continued to work flawlessly without any further setup.
IT BROKE (acted like I don't exist....and can't hear me)

I pulled battery for 30 or more minutes and no dice. Same behavior as the poster above noted with the same kind of attempt.

I pulled the 430RBZ for the original 130n.
130n (the original) fired right up without a need for a security code (I thought all '13's required a code) but it's still deaf or at least acting deaf.

It's got to be the uConnect module or a crap microphone wire. Maybe pinched or cut someplace as a result of just riding around/vibration/horrible quality control on how they run it/etc... I'm guessing uConnect module is junk but either way it pisses me off.

I am calling my dealer tomorrow to bring it in. I do use the phone in the Jeep and it's really irritating.[/QUOTE]
 

·
Registered
Joined
·
1,259 Posts
Discussion Starter #20
I am seriously doubting that it's the module and leaning more to the mic. As for the mic wire harness, it's embedded into the main dash harness, comes out on the drivers side and up the drivers "A" pillar.

What seems odd is that it worked till you pulled out the radio which the mic isn't wired to. It's connected to the Uconnect module is behind the HVAC control head below the radio.

Jeep came with the 130n which phone and bluetooth worked perfectly.
I pulled the 130 for a second hand 430RBZ, bluetooth (as it should) continued to work flawlessly without any further setup.
IT BROKE (acted like I don't exist....and can't hear me)

I pulled battery for 30 or more minutes and no dice. Same behavior as the poster above noted with the same kind of attempt.

I pulled the 430RBZ for the original 130n.
130n (the original) fired right up without a need for a security code (I thought all '13's required a code) but it's still deaf or at least acting deaf.

It's got to be the uConnect module or a crap microphone wire. Maybe pinched or cut someplace as a result of just riding around/vibration/horrible quality control on how they run it/etc... I'm guessing uConnect module is junk but either way it pisses me off.

I am calling my dealer tomorrow to bring it in. I do use the phone in the Jeep and it's really irritating.
[/QUOTE]

It actually worked fine both before the 130n being pulled and after for literally weeks and a number of telephone calls and streaming music/nav usages.

It stopped one morning without incident. Started Jeep up pulled out of the neighborhood, hit phone button to connect bluetooth to stream music... it wasn't recognized. I hit the voice control button and it acted like it couldn't hear me. The other very odd thing that happened that morning is I noticed that after I gave up on the phone/bluetooth thing that the radio sounded louder up front then I had set the soundstage via fader in the headunit. Checked the audio settings and everything was back at the center position, treble, mid, bass, fader, and balance all in the factory central positions. This would indicate to me that it may have something to do with either the headunit or the Jeeps wiring. Figured if I swapped in the 130n and it worked then it would be the 430RBZ that was having an issue or causing an issue with the uConnect. Low and behold when I swapped back to the 130n nothing changed so now I'm thinking the only option is to find fault with the uConnect module or microphone. Neither one works so without a uConnect module swap I wouldn't be able to troubleshoot it further.

My guess is some sort of power surge/issue in the Jeep that caused the 430RBZ to reset and fried the uConnect or Mic.
 
1 - 20 of 54 Posts
Top