Uconnect Rebooting

2018 Big Horn 1500 Black Edition


2/13/2018


My Uconnect screen just started rebooting itself yesterday around 4pm. and today it continues to do the same thing. My boss just came and told me that several people he knows just started having the same problem with their Uconnect system. Dealer says Chrysler is working on a fix.


If anyone has any other input that would be appreciated.

 

Wow, thanks for the quick reply. Sounds like a firmware bug they can possibly fix remotely. I'm hoping they can because finding time to get the truck to the dealer right now is going to be a pain in the ass.

Thanks again!

 

Just chatted with the Mopar Owners website and this is what they told me:

We are currently aware of an issue causing the radios to restart repeatedly. At the moment we are working on a resolution to this concern however as of right now there is not. The concern did start on Friday and engineers have been contacted. At this time we are able to create a case here for you in regards to this issue and we are advising our customer to contact us back in a couple business days in regards to a solution. We are working as quickly as possible to get this resolved and we do apologize for the inconvenience.

They can't say for certain but they think the fix will come across the vehicle automatically. You may want to chat with someone on the site and let them know you're having this problem. She said that since I have a case opened they'll contact me about the solution.

 

It seems there was an over the air update that caused this last Friday.

Affecting only the 2018 models since they have the newer head units (by Panasonic).

https://jalopnik.com/fiat-chrysler-pushed-a-uconnect-update-that-causes-cons-1822939437

 

Yup, that seems to be the issue. Hopefully they'll fix it soon, but since they've known about it since last Friday it must be difficult.

 

Some of the comments Ive read said this has happened before and it was an issue on the Sirius/XM side.

Either way, Chrysler should really come up with a way to flash older firmwares, specifically for issues like this.

 

I wonder if they'll have issues flashing the new fix if the radio can't keep running for longer than 45 seconds without powering off......

 

Sounds like the 2013 Ford Explorer we used to have with MFT

 

Try this temporary fix. Put a location in the nav, start the guidance and then mute the nav. This should stop the rebooting. You’ll have to do it every time you restart the truck.

https://jalopnik.com/theres-a-fix-for-the-chrysler-uconnect-rebooting-proble-1822972650

My radio is not affected so I can’t test it myself.

 

Update from Uconnect 8 hours ago:

Regarding customers experiencing repeated system rebooting: We have identified that the concern is related to SiriusXM Travel Link services. In the next 48 hours we’ll temporarily suspend the Travel Link feature in order to cease the reboot. We appreciate your patience.

 

Thank you for sharing our statement, bbdmac! If anyone has any additional questions, please feel free to send us a private message.
Julie
Ram Social Care Specialist

 

I just tried the temporary fix and it does work but what I found is that there is not enough time to type in address so what I did was I went to the map screen and selected a location on the map and set that as my destination. The screen did stop rebooting and my does work.


I also just talked with service from where I bought my truck and it will be an over the air update but they still do not know when or how long it will take.

 

I recall my 2016 RA4 8.4N radio flashing a message on the screen that read something like

Subscription Update

That happened about 1 PM on February 8, 2018 California time
I thought that we were getting another OTA, ( Over The Air ), but there was no follow up screen reading the normal download or postpone message that was sent out last summer.

Maybe that communication was a radio check to see what radios had the newest software with Apple Car Play, which only the newest vehicles have. :4-dontknow:

 

I drove 35 minutes to work this morning and not one reboot took place. So it appears to be fixed on my truck. It's odd that I haven't seen any messages about the fix being rolled out yet. I couldn't go for more than a minute without the reboot taking place prior to this morning. I hope it continues to work. I also checked the "Travel Link" and it seemed to be working and wasn't turned off. Hoping for the best!

 

I have a feeling it was fixed on Sirius/XMs side.

Ive seen stuff like this before happen with my satellite *TV* receivers when bad data (programming guide, video bitstream, etc) comes across. The receivers go into fits because they cant handle the errant data but once the data is fixed everything goes back to normal.

Probably something in the OTA update for the '18 radios that was expecting X from the service but got Y and caused the radio to go into fits.

 

I received confirmation that the fix started going out yesterday.

 

My 2014 Ram 2500 is rebooting over & over. This is the worst!!! Any ideas on what to fix this??!!

 

I have a 2013 dodge durango citadel. We have a brand new radio installed cause the last one had a broke screen. Ever since it was replaced the radio reboots constantly. It is driving me insane. Not to mention the kids would really like to watch a DVD on a long trip (reason we bought this one) anyways we have called sinus xm.. went to the dealership, and still nothing. Its very annoying and really hard to drive at night when it reboots every 3 minutes with full brightness. Someone please help us figure this out!!

 

Hi there--

Sorry to hear about the concerns you've been experiencing recently with your Uconnect system. If you're still experiencing these concerns and would like us to look into it for you, please don't hesitate to send us a private message with your VIN and any additional details/documentation that will help me get a better understanding of your situation.

Thanks in advance,

Courtney
Ram Cares

 

My 2018 8.4 screen just started the rebooting thing. Anyone else having this issue currently?