Jeep Wrangler Forum - Reply to Topic
Jeep Wrangler Forum

Go Back   Jeep Wrangler Forum > JK Jeep Wrangler Forum > JK General Discussion Forum > Uconnect bluetooth disconnect, 430N and HTC DNA

Join Wrangler Forum Today


Thread: Uconnect bluetooth disconnect, 430N and HTC DNA Reply to Thread
Title:
  
Message:
Post Icons
You may choose an icon for your message from the following list:
 

Register Now

In order to be able to post messages on the Jeep Wrangler Forum forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in

Human Verification

In order to verify that you are a human and not a spam bot, please enter the answer into the following box below based on the instructions contained in the graphic.



Additional Options
Miscellaneous Options

Topic Review (Newest First)
01-16-2014 09:39 PM
apddevo Having the same problem with my samsung galaxy s3. It reads incoming texts and sends outgoing texts fine, but disconnects the phone calls as some previous posters have said. Major PITA!
01-16-2014 07:38 PM
SilverMiner
Quote:
Originally Posted by simchippy View Post
I have the exact same problem 80-90% of dialed calls. I have a Samsung Note II with Verizon. I'm so close to ripping my 430n out of the dash and beating like the fax machine in office space. I just received the most recent Android 4.3 update last week with no improvement. I hate this radio. My phone works perfect in 3 other cars and multiple BT devices.
My issue was resolved with an update from HTC, and the radio works fine with other phones too. So, I think the issue is phone related, may have to bug Samsung and hope they listen.
01-16-2014 05:09 PM
simchippy I have the exact same problem 80-90% of dialed calls. I have a Samsung Note II with Verizon. I'm so close to ripping my 430n out of the dash and beating like the fax machine in office space. I just received the most recent Android 4.3 update last week with no improvement. I hate this radio. My phone works perfect in 3 other cars and multiple BT devices.
02-15-2013 01:23 PM
xsdbs you're correct about that, there are 20 generic prerecorded messages. They don't want you concentrating on a long message as if you were thumbing it into the phone to send. Less distraction.




Quote:
Originally Posted by SilverMiner View Post
I've never tried sending texts through Uconnect, looked like you could only do canned messages so there isn't much use to me.
02-15-2013 12:30 PM
SilverMiner
Quote:
Originally Posted by xsdbs View Post
I just updated my buddies also and it has not dropped a call (I've placed about 20+). Well that's good but I am curious why they didn't attack MAP (Message Access Profile) for texting thru BT. You can receive messages but sending fails. Maybe there was more involved than there was to help placing calls. Not to mention that the "Chinese New Year" is this week.
Now I have to check on the Rezound, I don't see anything for it yet.
I've never tried sending texts through Uconnect, looked like you could only do canned messages so there isn't much use to me.
02-15-2013 12:01 PM
xsdbs I just updated my buddies also and it has not dropped a call (I've placed about 20+). Well that's good but I am curious why they didn't attack MAP (Message Access Profile) for texting thru BT. You can receive messages but sending fails. Maybe there was more involved than there was to help placing calls. Not to mention that the "Chinese New Year" is this week.
Now I have to check on the Rezound, I don't see anything for it yet.




Quote:
Originally Posted by SilverMiner View Post
Awesome! Going to try it now without repairing.

It works!! Yay. Only tried 3 calls but mine was doing it almost every time. I'm thinking it's fixed.
02-15-2013 10:42 AM
SilverMiner
Quote:
Originally Posted by solinary View Post
I was having the same issue...placed calls were dropped from the radio almost right away and received calls were okay.

I updated my DNA this morning, removed/readded the pairing and after 15 test outbound calls, not a single one has shown any issues at all.
Awesome! Going to try it now without repairing.

It works!! Yay. Only tried 3 calls but mine was doing it almost every time. I'm thinking it's fixed.
02-15-2013 10:36 AM
SilverMiner
Quote:
Originally Posted by xsdbs View Post
cool, hope for the best huh. Can you give me the SW info so I can add it to my notes? Thanks
Will do.

Here you go:
Source: Verizon Wireless
Name: HTC6435LVW_2_04.605.2-1.15.605.4

Software Number: 2.04.605.2 71ORD
HTC SDK API level: 4.63

Build number: 2.04.605.2 CL147796 release-keys


There are other version numbers for various things, let me know if you want anything else.

Thanks so much xsdbs for making HTC aware of the issue, looks like they got right on it.
02-15-2013 10:26 AM
solinary I was having the same issue...placed calls were dropped from the radio almost right away and received calls were okay.

I updated my DNA this morning, removed/readded the pairing and after 15 test outbound calls, not a single one has shown any issues at all.
02-15-2013 07:08 AM
xsdbs cool, hope for the best huh. Can you give me the SW info so I can add it to my notes? Thanks



Quote:
Originally Posted by SilverMiner View Post
I got a new firmware that was released for the HTC DNA tonight. I haven't checked to see if it fixes this issue.
02-14-2013 07:06 PM
SilverMiner I got a new firmware that was released for the HTC DNA tonight. I haven't checked to see if it fixes this issue.
02-13-2013 09:39 AM
KittyPrawn
Quote:
Originally Posted by xsdbs View Post
@ kittyprawn,
I have been able to borrow a friends EVO 4G LTE, it's on Sprint but according to HTC, it should be the same SW as in the Verizon phone even though the #'s aren't the exact same.

Originally the SW package was:
Android : 4.0.4
SW version : 2.13.651.1710RD

Today, I updated to:
Android : 4.1.1
SW version : 3.16.651.3710RD
So far I can't duplicate your calling issue. My calls stay connected no matter when I try them. I will continue to use this phone for a couple days and see if there are any different results.
I do have a couple of questions for you:
1) You said that the 1st call after getting into the vehicle is when you get the "call completed" message. When this happens, is the call still going thru on the phone itself or does it end as well?
2) How long after you get into the vehicle are you trying to make a call?
Thanks,
The phone I have is also on Sprint now, not Verizon. I switched services.

To answer your questions:
1 - The last time this happened, I noticed that my phone was still connected to the line. When I tried to speak into the phone, I didn't hear anything. I don't know if at that point my party had hung up, or if I was in voicemail.

2 - I usually try to make a call within the first few minutes of driving. But, I don't know for sure if that's consistent. I haven't fully paid attention to when I start making calls in the phone.

I have since updated my phone and it is 4.1.1 and 3.16.651.3 710RD. This didn't resolve the problem for me, however. I haven't tried unpairing it, and will try that out when I can.

FTP and MAP were unchecked. I have checked them now, and I will see if that fixes the issue before I try to unpair.
02-13-2013 09:38 AM
xsdbs Wow, I was just going to edit this but it got closed quickly,
KP,
Can you look in you settings menu --> SW update. Have the phone search for an update, supposedly there is a .3.16 update that is available which is the same as the one that I applied to this phone. There were some BT fixes in it. Please give that a try, then delete you phone from Uconnect & Uconnect from your phone, then go thru a fresh pairing session. (Also, did you check the MAP & FTP boxes in the Advanced settings menu once you're in the BT menu)?




Quote:
Originally Posted by xsdbs View Post
@ kittyprawn,
I have been able to borrow a friends EVO 4G LTE, it's on Sprint but according to HTC, it should be the same SW as in the Verizon phone even though the #'s aren't the exact same.

Originally the SW package was:
Android : 4.0.4
SW version : 2.13.651.1710RD

Today, I updated to:
Android : 4.1.1
SW version : 3.16.651.3710RD
So far I can't duplicate your calling issue. My calls stay connected no matter when I try them. I will continue to use this phone for a couple days and see if there are any different results.
I do have a couple of questions for you:
1) You said that the 1st call after getting into the vehicle is when you get the "call completed" message. When this happens, is the call still going thru on the phone itself or does it end as well?
2) How long after you get into the vehicle are you trying to make a call?
Thanks,
02-13-2013 09:32 AM
xsdbs @ SilverMiner: (and anyone that has the HTC DNA & Rezound)

I have stumbled onto a work around that will let you use your phone thru Uconnect until a complete fix becomes available thru HTC. This is a "band-aid", but as I said you can use your phone.

Here's what I did:

1) go into your contacts and add a new contact with an odd # that won't call anyone. EX:

I added:
(name) ABC, ( I used the mobile number slot) 111-1111
Now we know with that # we will get a network message about the # being incorrect. (we want this to happen). This message will end in about 10-15 seconds (good)

2) This new contact is the band-aid.
3) when you want to place a call, you'll want to use this contact,
press and release the UC phone button and say "call ABC, mobile". UC will say calling "ABC mobile is this correct?" (yes)
4) the call & recording will start, then you'll hear the "call completed".
Now place the real call that you want to make (ex: call Jeremy, mobile).
5) The network reply for the wrong # will play a couple times on your phone and then the network will hang up and you don't have to worry about it, but Jeremy's call will go thru and stay connected.

Now I know you're thinking, "dude, that's such a P.I.T.A. and really sucks. Well, yes you're correct about that but after you try it a couple times, you'll see that it's actually quite simple and guess what(?) you get to use your phone thru the Uconnect system which in a lot of areas will keep you from getting tickets.
So as I said, this is a band-aid that I stumbled on from trying a few things. You are welcome to use it if you like but please, don't throw any abuse my way. I am only offering some help and hopefully there will be a correct fix soon.
02-13-2013 09:02 AM
xsdbs @ kittyprawn,
I have been able to borrow a friends EVO 4G LTE, it's on Sprint but according to HTC, it should be the same SW as in the Verizon phone even though the #'s aren't the exact same.

Originally the SW package was:
Android : 4.0.4
SW version : 2.13.651.1710RD

Today, I updated to:
Android : 4.1.1
SW version : 3.16.651.3710RD
So far I can't duplicate your calling issue. My calls stay connected no matter when I try them. I will continue to use this phone for a couple days and see if there are any different results.
I do have a couple of questions for you:
1) You said that the 1st call after getting into the vehicle is when you get the "call completed" message. When this happens, is the call still going thru on the phone itself or does it end as well?
2) How long after you get into the vehicle are you trying to make a call?
Thanks,






Quote:
Originally Posted by KittyPrawn View Post
Just bringing this thread to the top with some new information...

I now have an HTC EVO 4G LTE and now have a problem. It is not quite the same as the OP. The first call of the drive that I initiate, whether through the phone or through UConnect, will ring once or twice and then disconnect. I will then have to call the number again. The second time I call I don't have the issue.

Software version: 3.15.651.16 710RD
Android version 4.1.1
HTC Sense version 4+
Kernel 3.4.10-g014d33e
build: 3.15.651.16 CL124461
02-07-2013 09:06 AM
SilverMiner
Quote:
Originally Posted by xsdbs View Post
Just an update on the Rezound & DNA. The issue is still being looked into. HTC knows about them now and I was told that sometimes there is a delay getting into fixes when the Eng teams are working on new devices.
Good to know, thanks.
02-07-2013 07:27 AM
xsdbs Just an update on the Rezound & DNA. The issue is still being looked into. HTC knows about them now and I was told that sometimes there is a delay getting into fixes when the Eng teams are working on new devices.
02-07-2013 07:24 AM
xsdbs americonium, Your screen name sounds familiar. Have I helped you before?
What is the year of your Jeep and which radio do you have? Thanks





Quote:
Originally Posted by americonium View Post
I have a Samsung Galaxy S3 w/Verizon and the official JB release. My phone only recently started doing this after the JB was pushed to my phone, and it's maddening.
02-07-2013 07:21 AM
xsdbs KP, the SW in is an older version and my friend doesn't want to update it because it works fine now and he doesn't want to have any issues. I'll look into seeing if I can find one with the newer SW version in it.




Quote:
Originally Posted by KittyPrawn View Post
Oh yeah. I just think it is weird that it is inconsistent per phone. My Rezound was perfect.
02-04-2013 05:35 PM
SilverMiner
Quote:
Originally Posted by americonium View Post
I have a Samsung Galaxy S3 w/Verizon and the official JB release. My phone only recently started doing this after the JB was pushed to my phone, and it's maddening.
Interesting in that it's a whole new manufacturer. I'm wondering if it's an Android issue now.
02-04-2013 05:04 PM
americonium I have a Samsung Galaxy S3 w/Verizon and the official JB release. My phone only recently started doing this after the JB was pushed to my phone, and it's maddening.
02-02-2013 02:09 PM
xsdbs yeah, that is something that I find quite interesting as well. I'll get with you when I'm back home next week.



Quote:
Originally Posted by KittyPrawn View Post
Oh yeah. I just think it is weird that it is inconsistent per phone. My Rezound was perfect.
02-02-2013 08:32 AM
KittyPrawn
Quote:
Originally Posted by xsdbs View Post
Goes to prove that it was an HTC issue and not Uconnect. HTC is still trying to have their Eng's look into a fix for it.
Oh yeah. I just think it is weird that it is inconsistent per phone. My Rezound was perfect.
02-01-2013 11:01 PM
xsdbs Goes to prove that it was an HTC issue and not Uconnect. HTC is still trying to have their Eng's look into a fix for it.




Quote:
Originally Posted by prophet View Post
This was a major problem with my Rezound but the Rezound has been replaced by a Droid RAZR MAXX HD and the problem is gone. My wife just loved having to call me back after hearing dead air 75% of the time.
02-01-2013 10:59 PM
xsdbs Hello kittyprawn, sorry I haven't been able to look into this much more yet with the DNA & Rezound. I see that you now have the EVO 4G LTE. I'll have to check your SW vs the one on the phone that I had tried out a short while back. I got called out of town for work and will be back next Wed or Thurs. I'll be able to look into these issues more then, ok.



Quote:
Originally Posted by KittyPrawn View Post
Just bringing this thread to the top with some new information...

I now have an HTC EVO 4G LTE and now have a problem. It is not quite the same as the OP. The first call of the drive that I initiate, whether through the phone or through UConnect, will ring once or twice and then disconnect. I will then have to call the number again. The second time I call I don't have the issue.

Software version: 3.15.651.16 710RD
Android version 4.1.1
HTC Sense version 4+
Kernel 3.4.10-g014d33e
build: 3.15.651.16 CL124461
02-01-2013 09:03 PM
SilverMiner
Quote:
Originally Posted by prophet View Post
This was a major problem with my Rezound but the Rezound has been replaced by a Droid RAZR MAXX HD and the problem is gone. My wife just loved having to call me back after hearing dead air 75% of the time.
I'm glad that it appears to be a phone issue, hopefully it will get addressed in a firmware update.
02-01-2013 08:52 PM
prophet This was a major problem with my Rezound but the Rezound has been replaced by a Droid RAZR MAXX HD and the problem is gone. My wife just loved having to call me back after hearing dead air 75% of the time.
02-01-2013 02:27 PM
SilverMiner
Quote:
Originally Posted by KittyPrawn View Post
Just bringing this thread to the top with some new information...

I now have an HTC EVO 4G LTE and now have a problem. It is not quite the same as the OP. The first call of the drive that I initiate, whether through the phone or through UConnect, will ring once or twice and then disconnect. I will then have to call the number again. The second time I call I don't have the issue.

Software version: 3.15.651.16 710RD
Android version 4.1.1
HTC Sense version 4+
Kernel 3.4.10-g014d33e
build: 3.15.651.16 CL124461

Interesting. Mine will definitely do it more than once, but it's not every time. I don't see a pattern yet.
02-01-2013 12:59 PM
KittyPrawn Just bringing this thread to the top with some new information...

I now have an HTC EVO 4G LTE and now have a problem. It is not quite the same as the OP. The first call of the drive that I initiate, whether through the phone or through UConnect, will ring once or twice and then disconnect. I will then have to call the number again. The second time I call I don't have the issue.

Software version: 3.15.651.16 710RD
Android version 4.1.1
HTC Sense version 4+
Kernel 3.4.10-g014d33e
build: 3.15.651.16 CL124461
01-21-2013 08:58 AM
xsdbs kittyprawn,
I used the HTC EVO 4G a few months back and had no issues with it. In fact SMS texting thru BT also worked well. It looks like Jelly Bean is available for it now, I'll have to see if my friend has updated and retest with the JB. I'll let you know about that one also. I'm still messing around with the Rezound, I got tied up this past weekend.






Quote:
Originally Posted by KittyPrawn View Post
Oh, it's not your fault. Work is keeping me up all night. This problem was a distraction, haha!

I really do want to figure out what is causing this though. Especially since my phone seems to be working fine, but i will be switching to a sprint Htc evo soon and now I'm afraid it will give me trouble!
This thread has more than 30 replies. Click here to review the whole thread.

Posting Rules
You may post new threads
You may 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


All times are GMT -5. The time now is 09:15 PM.



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