Ram Heavy Duty Forum
Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
2022 Uconnect 5 12.0 Glitches
- Thread starter dillonybarbo
- Start date
That's what the 26 f250 did i test drove. Really liked it's infotainment center. It was more of a square display. 3/4 of it was AA the rest was as far as I could tell in the 15 minutes I drove it could be whatever you wanted.
Want to watch two external cameras? You bet.
Want to see various guages? Here go.
Want to make AA full screen and not see all that extra? Click this screen icon.
@RamCares i think you all should go barrow a new F250/350 and check out what they're doing with the infotainment center. That and the center console with the rest of the ram interior/cummins would be the perfect truck. Oh and add the HUD the Chevy 2500/3500 have.
Apple only has more market share in the USA, and it is not by a huge margin. WW, Android is far more popular.
Rodehawg97
Member
- Messages
- 22
- Reaction score
- 27
- Points
- 13
I've taken my 2022 Power Wagon with the Level 2 trim in to the dealer twice now for glitches (screen going black, radio station changing by itself) with the infotainment console. The first time they tried to gaslight me by telling me the problems were due to "all the electronics that were added to my truck" such as the retracting steps and sPod for the lights and air compressor. They couldn't explain how "all those electronics" affected my truck. The problems continued and now have added two new ones: "Incorrect gear 7 ratio" and trailer brakes (brand new trailer) failing to release until I shut the truck off and turn it back on. The service coordinator texted me that they had found an intermittent 'open' on the cellular antenna which required replacing the antenna. I have yet to get the dealer to explain to me how that is the cause of all my problems. Stay tuned for more.
Aluminati79
New Member
- Messages
- 3
- Reaction score
- 0
- Points
- 1
I posted this in another thread, but this may help some people here:
Long time member of sister site 5thGenRams, average poster, but back into it since my December 2025 purchase of a 2026 Ram 2500. I came from a 1500 mainly to upgrade to a bigger more stable truck for trailering horses. To start, had this message pop up from the very first start up on day of delivery. Was persistent ever since, but would either come on right away, or after 30 secs of the truck being on. Took it to a local dealer to get inspected (was purchased out of state) and mentioned this message. The dealer said there's a known bulletin about this and an OTA update would be coming this year to fix it. (cue Morgan Freeman voice) It was at this moment, I knew it was messed up.
Fast forward 2 weeks (and mind you, was at the dealer a second time in those 2 weeks for a busted tailight bulb), after activating my Uconnect subscription and adding the truck to my Ram app, I noticed the remote start, lock doors, or location of vehicle DID NOT work. Called Uconnect cust service and they logged a ticket/case for me. This was Friday 1/16/26. Went to start truck the next morning, and DEAD. Dead as a doornail. Dash all lit up and all gauges went haywire, brake lights stayed on. Brake lights also stayed on for maybe 45 mins after I tried to start truck. Measured voltage on battery at 2.5V. Jumped truck to get it out of the garage and then voltage jumped to 12.5V. Also started up right away after shutting down from jump. Called dealer and they wanted to test battery, so made appt to bring it in.
Dropped truck off and after all day 1/19/26, they reported it started up multiple times, battery tested fine. Wanted to keep overnight to monitor any battery draw. Here's the important twist of this story: dealer called 1/20/26 after it sat all night and reported a code was stored on the truck pointing to the Radio/Telematic Box. Shop foreman was going back and forth with Ram engineers: they told him dont replace box if this code appears. Ram told him if the security gateway has this code, do nothing. But the dealer told them, the code is not at the security gateway, its the Telematics box. Code that was thrown was U3033-00.
The dealer finally called back and said they are replacing the telematics box. They reported that nationwide, there are only 15 of these boxes available and 18 on order. They put a box on order for me and the good news (or some sort of relief), is mine is getting replaced, but not sure when. I basically have to limit bluetooth use and cant really use any of the Uconnect functions.
I've owned Rams more than any other brand of truck, and quite simply, I'm tired of these manufacturers making subpar stuff. It's almost altering my usual calm, happy go lucky personality. It's in every industry today, and a challenge to get them to do anything about it. I almost wish to see these companies go under as punishment for deceiving the public with the stuff they sell.
Kudos to the dealer I have dealt with to get this fixed. Sounds like they are going above and beyond to get this fixed.
Long time member of sister site 5thGenRams, average poster, but back into it since my December 2025 purchase of a 2026 Ram 2500. I came from a 1500 mainly to upgrade to a bigger more stable truck for trailering horses. To start, had this message pop up from the very first start up on day of delivery. Was persistent ever since, but would either come on right away, or after 30 secs of the truck being on. Took it to a local dealer to get inspected (was purchased out of state) and mentioned this message. The dealer said there's a known bulletin about this and an OTA update would be coming this year to fix it. (cue Morgan Freeman voice) It was at this moment, I knew it was messed up.
Fast forward 2 weeks (and mind you, was at the dealer a second time in those 2 weeks for a busted tailight bulb), after activating my Uconnect subscription and adding the truck to my Ram app, I noticed the remote start, lock doors, or location of vehicle DID NOT work. Called Uconnect cust service and they logged a ticket/case for me. This was Friday 1/16/26. Went to start truck the next morning, and DEAD. Dead as a doornail. Dash all lit up and all gauges went haywire, brake lights stayed on. Brake lights also stayed on for maybe 45 mins after I tried to start truck. Measured voltage on battery at 2.5V. Jumped truck to get it out of the garage and then voltage jumped to 12.5V. Also started up right away after shutting down from jump. Called dealer and they wanted to test battery, so made appt to bring it in.
Dropped truck off and after all day 1/19/26, they reported it started up multiple times, battery tested fine. Wanted to keep overnight to monitor any battery draw. Here's the important twist of this story: dealer called 1/20/26 after it sat all night and reported a code was stored on the truck pointing to the Radio/Telematic Box. Shop foreman was going back and forth with Ram engineers: they told him dont replace box if this code appears. Ram told him if the security gateway has this code, do nothing. But the dealer told them, the code is not at the security gateway, its the Telematics box. Code that was thrown was U3033-00.
The dealer finally called back and said they are replacing the telematics box. They reported that nationwide, there are only 15 of these boxes available and 18 on order. They put a box on order for me and the good news (or some sort of relief), is mine is getting replaced, but not sure when. I basically have to limit bluetooth use and cant really use any of the Uconnect functions.
I've owned Rams more than any other brand of truck, and quite simply, I'm tired of these manufacturers making subpar stuff. It's almost altering my usual calm, happy go lucky personality. It's in every industry today, and a challenge to get them to do anything about it. I almost wish to see these companies go under as punishment for deceiving the public with the stuff they sell.
Kudos to the dealer I have dealt with to get this fixed. Sounds like they are going above and beyond to get this fixed.
Last edited: