Jeep Garage  - Jeep Forum banner

Messaging Bug in 14.25.5??

3K views 9 replies 8 participants last post by  michaelk 
#1 ·
Hi All, I am curious is anyone else is experiencing this problem.

Since June 1, 2014 I have been using my Samsung Galaxy S5 with my Uconnect flawlessly on the previous version of Uconnect code. I regularly send and receive text messages via Uconnect. Pretty much ANY time I am in the car. And it has alwasy worked beautifully.

As of last week, I installed 14.25.5. Beginning immediately after installation of the 14.25.5, the "messaging" button went grey. After numerous reboots of the car and phone, including deleting and repairing, it remained grey. I then deleted ALL exiting text message on the phone, and reconnect the phone and the messaging button became active. So my conclusion is that 1 or more message in that message history was not playing nice with uconnect, and once they were gone uconnect was satisfied. The important thing to note is that messaging was working fine before the update and NO messages were received during the update process, so the message list AFTER the update was identical to the message list BEFORE the update.

The next day I was able to send an receive messages through the day and sometime in the late afternoon, the same thing happened. I had exchanged message with about dozen or more people by that time, and since it was nothing important I deleted the full message history, reconnected and was back in business.

The next day the same thing happened. This time I tried to remove message selectively to determine which might be the troublemaker. I deleted 1 or 3 message at a time, and eventually it came back to life. I was not able to discern which one cause the problem.

The next day the same thing happened, so I now started removing messages sequentially backward along the timeline, I eventually removed one that made messaging come back to life. In this case the problem message was determined, but there was nothing significantly interesting about the message.

In all cases, I have had a blend of standard SMS and MMS, some are group messages and others are singles. In all cases, none of the messages that seem to be the likely suspects have actually been the ones causing trouble.

I am suspecting this is a bug, and quite annoying too, since it is causing me to repeated parse and delete my messages store.

Has anyone else seen this problem?

Also, I don't know if this is related , but I have also noticed that spontaneously Uconnect will stop announcing new messages upon receipt, even though they are showing up in the uconnect inbox, and it was announcing new messages mere minutes beforehand.

I am considering downgrading to the older code to see if these problems go away.
 
See less See more
#2 ·
I'm having the same issue, but I haven't tried deleting messages yet. I'm back to texting on my phone which isn't safe, but it's just as annoying to have to clear my texts every day. I'm on an HTC One M7
 
#3 ·
Hi All, I am curious is anyone else is experiencing this problem.



Since June 1, 2014 I have been using my Samsung Galaxy S5 with my Uconnect flawlessly on the previous version of Uconnect code. I regularly send and receive text messages via Uconnect. Pretty much ANY time I am in the car. And it has alwasy worked beautifully.



As of last week, I installed 14.25.5. Beginning immediately after installation of the 14.25.5, the "messaging" button went grey. After numerous reboots of the car and phone, including deleting and repairing, it remained grey. I then deleted ALL exiting text message on the phone, and reconnect the phone and the messaging button became active. So my conclusion is that 1 or more message in that message history was not playing nice with uconnect, and once they were gone uconnect was satisfied. The important thing to note is that messaging was working fine before the update and NO messages were received during the update process, so the message list AFTER the update was identical to the message list BEFORE the update.



The next day I was able to send an receive messages through the day and sometime in the late afternoon, the same thing happened. I had exchanged message with about dozen or more people by that time, and since it was nothing important I deleted the full message history, reconnected and was back in business.



The next day the same thing happened. This time I tried to remove message selectively to determine which might be the troublemaker. I deleted 1 or 3 message at a time, and eventually it came back to life. I was not able to discern which one cause the problem.



The next day the same thing happened, so I now started removing messages sequentially backward along the timeline, I eventually removed one that made messaging come back to life. In this case the problem message was determined, but there was nothing significantly interesting about the message.



In all cases, I have had a blend of standard SMS and MMS, some are group messages and others are singles. In all cases, none of the messages that seem to be the likely suspects have actually been the ones causing trouble.



I am suspecting this is a bug, and quite annoying too, since it is causing me to repeated parse and delete my messages store.



Has anyone else seen this problem?



Also, I don't know if this is related , but I have also noticed that spontaneously Uconnect will stop announcing new messages upon receipt, even though they are showing up in the uconnect inbox, and it was announcing new messages mere minutes beforehand.



I am considering downgrading to the older code to see if these problems go away.

I have an iphone so I can't relate to being able to compose messages, but I can relate to you on announcement of incoming txts. Yesterday all of a sudden, I lost the announcement of new messages and just like you said, they are in the inbox.


Sent from my iPhone using JeepGarage
 
#5 ·
SG5 here. Think i did the update to that version sometime in July and phone and uconnect work hand in hand beautifully for me as of yet. No issues with the voice text or making calls.
 
#6 ·
I'm having this same problem with an S3... will try deleting messages and reconnecting to see if that fixes it for me, but so far I haven't seen anything other than random connections.

Footnote, my "recent calls" button also grays out when "messaging" is gray. :mad:
 
#7 ·
I had the same symptom today with my Droid Maxx. Messaging and recent calls grayed out when i first got in the truck.

I only have had my Durango like 2 weeks now so honestly it's the first time i tried to use the messaging as soon as i got in.

I turned off and back on my phone's Bluetooth and that did not immediately repair it. I moved on to something else and a couple minutes later it was fine. I didn't really pay attention during those couple minutes so not sure what else was going on.

I assumed it just takes a couple minutes to connect the messaging bit until I read this thread. Before i read this thread, I was figuring it first connected the phone bit, then synced the phone book (mine is a little large- ~510 contacts so i figured that was what was taking so long), then once that synced it connects messaging and recent calls.

Sounds like my guess may not exactly be what is going on.....
 
#8 ·
Also, I don't know if this is related , but I have also noticed that spontaneously Uconnect will stop announcing new messages upon receipt, even though they are showing up in the uconnect inbox, and it was announcing new messages mere minutes beforehand.

I am considering downgrading to the older code to see if these problems go away.
I've had this last issue. It's happened on multiple versions of Uconnect and Multiple Phones HTC and Samsung.

It seems a little better lately. S5 with UConnect 14.25.05

It seems related to if you respond to a message and how fast you respond before another message comes in.
 
#9 ·
I have an iPhone and I know out going messages do not work. What was weird was that one day the messaging stopped working. I reset network settings, deleted the pairs on the radio and the iphone and repaired. No joy. It was late so I gave up and went to bed. The next morning got in the car and it was working again. Gremlins? Maybe. I think the uConnect software takes longer to shut down/reboot than I thought. I compare it to putting a PC to sleep rather that a hard reboot.
Another thing I noticed is that it can take up to 30 seconds sometimes for the messaging button to be active. My apps list is the same way. Pandora can take 30 seconds before it will show up in the list of apps.
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top