2012 Uconnect SW update
I have a 2012 Charger with the 8.4N/RB5 radio. Have there been any updates yet? Are there any coming that anyone is aware of? There are some bugs in the current version with Bluetooth and nav that i'm hoping will be fixed. I just rented a 2013 300 on a trip and the new system is amazing. I was quite jealous.
Thanks,
Vince
Thanks,
Vince
Being that your vehicle build date was 6-11 then you have the V1 2012 SW in your system, it (2012) was a carry over with some enhancements. You could apply the SW update that is in post #1 of this thread. You'll get better streaming audio sound and recognition of Voice commands as well as the supporting of MAP (Message Access Profile) for texting. However in order for MAP to work correctly, the phone also needs to support MAP and there are a handful that work correctly and a handful that don't. MAP is still in an infancy mode for hands free systems.
Being that your vehicle build date was 6-11 then you have the V1 2012 SW in your system, it (2012) was a carry over with some enhancements. You could apply the SW update that is in post #1 of this thread. You'll get better streaming audio sound and recognition of Voice commands as well as the supporting of MAP (Message Access Profile) for texting. However in order for MAP to work correctly, the phone also needs to support MAP and there are a handful that work correctly and a handful that don't. MAP is still in an infancy mode for hands free systems.
things are great-they went very smoothly, my only advice is print out the directions take them with you in the car and FOLLOW them to the letter.
Thanks
Last edited by hoeky; Feb 22, 2013 at 04:14 PM. Reason: forgot to say thanks
Great, so you performed the update and it helped? Glad that I could help you out.
Hi guys, back again.
Does anyone get a situation where the Uconnect will prematurely say
"call completed"
during dialing and disconnect the phone call from the stereo. But the call continues on the phone and you have to scramble to get the phone out of your pocket? This is happening to me frequently now, other times it'll work just fine. I have a Samsung Galaxy S3 with Android 4.1.2 on it. I've tried all kinds of phone software and it all does the same thing to me occasionally, so I have to point back to the Uconnect software.
XSDBS, would reflashing the Uconnect update (TSB 08-018-12) in the OP of this thread do any harm?
Has anything been released that's newer?
[history, I borked up my stereo bad, had to have dealer salvage it for me, which they did, ever since then, the Uconnect doesn't seem to operate properly for me on calls]
Does anyone get a situation where the Uconnect will prematurely say
"call completed"
during dialing and disconnect the phone call from the stereo. But the call continues on the phone and you have to scramble to get the phone out of your pocket? This is happening to me frequently now, other times it'll work just fine. I have a Samsung Galaxy S3 with Android 4.1.2 on it. I've tried all kinds of phone software and it all does the same thing to me occasionally, so I have to point back to the Uconnect software.
XSDBS, would reflashing the Uconnect update (TSB 08-018-12) in the OP of this thread do any harm?
Has anything been released that's newer?
[history, I borked up my stereo bad, had to have dealer salvage it for me, which they did, ever since then, the Uconnect doesn't seem to operate properly for me on calls]
1) What network is the G III on?
2) What is the build date of your vehicle?
3) When you broke the stereo, what did you do to it? Do you know what the dealer did to get it working?
4) How have you tried "all kinds of phone SW"? I didn't think that you could go backwards once you updated the phone SW.
5) Have you tried a different phone to compare the results when making a call?
6) Have you rebooted the phone by removing the battery from the phone for a few minutes and then reinsert it? I have seen this cure some phone issues.
Now just a little FYI about what happens when you place a call:
A) You use Uconnect to tell the phone to place a call and Uconnect also puts the radio into hands free mode,
B) Uconnect tells the phone to place the call,
C) The phone starts dialing the call,
D) Uconnect will ask the phone if there is an active call,
E) The phone needs to reply back with an answer of yes or no,
F) This answer will tell Uconnect if there is still a call, and if "yes" is the response then Uconnect will keep sending the message to the radio to stay in hands free mode. If the reply is "no" or there is no reply back from the phone at all, the Uconnect will tell the radio to go back to stereo mode as well as say "call completed".
G) If the call is still going thru on the phone but not thru Uconnect, then the phone did not reply back properly when it was asked about the call.
2) What is the build date of your vehicle?
3) When you broke the stereo, what did you do to it? Do you know what the dealer did to get it working?
4) How have you tried "all kinds of phone SW"? I didn't think that you could go backwards once you updated the phone SW.
5) Have you tried a different phone to compare the results when making a call?
6) Have you rebooted the phone by removing the battery from the phone for a few minutes and then reinsert it? I have seen this cure some phone issues.
Now just a little FYI about what happens when you place a call:
A) You use Uconnect to tell the phone to place a call and Uconnect also puts the radio into hands free mode,
B) Uconnect tells the phone to place the call,
C) The phone starts dialing the call,
D) Uconnect will ask the phone if there is an active call,
E) The phone needs to reply back with an answer of yes or no,
F) This answer will tell Uconnect if there is still a call, and if "yes" is the response then Uconnect will keep sending the message to the radio to stay in hands free mode. If the reply is "no" or there is no reply back from the phone at all, the Uconnect will tell the radio to go back to stereo mode as well as say "call completed".
G) If the call is still going thru on the phone but not thru Uconnect, then the phone did not reply back properly when it was asked about the call.
Hi guys, back again.
Does anyone get a situation where the Uconnect will prematurely say
"call completed"
during dialing and disconnect the phone call from the stereo. But the call continues on the phone and you have to scramble to get the phone out of your pocket? This is happening to me frequently now, other times it'll work just fine. I have a Samsung Galaxy S3 with Android 4.1.2 on it. I've tried all kinds of phone software and it all does the same thing to me occasionally, so I have to point back to the Uconnect software.
XSDBS, would reflashing the Uconnect update (TSB 08-018-12) in the OP of this thread do any harm?
Has anything been released that's newer?
[history, I borked up my stereo bad, had to have dealer salvage it for me, which they did, ever since then, the Uconnect doesn't seem to operate properly for me on calls]
Does anyone get a situation where the Uconnect will prematurely say
"call completed"
during dialing and disconnect the phone call from the stereo. But the call continues on the phone and you have to scramble to get the phone out of your pocket? This is happening to me frequently now, other times it'll work just fine. I have a Samsung Galaxy S3 with Android 4.1.2 on it. I've tried all kinds of phone software and it all does the same thing to me occasionally, so I have to point back to the Uconnect software.
XSDBS, would reflashing the Uconnect update (TSB 08-018-12) in the OP of this thread do any harm?
Has anything been released that's newer?
[history, I borked up my stereo bad, had to have dealer salvage it for me, which they did, ever since then, the Uconnect doesn't seem to operate properly for me on calls]



