Update: I passed! Hat tip to this document that details the chrysler-drive-cycle-information.
After banging my head on this problem for a while and hearing what Chrysler/Jeep corporate had to say, I drove down to my local dealership on a snowy day. Luckily, there were zero customers in there and a bored (but very nice!) service tech had about an hour or so to sit and trouble shoot the problem with me. As it turns out, despite everything the corporate guys told me my software was WAAAAY out of date.
Then click yes to update the radio software. This update took me from 44.00.01 to 50.00.07. I specifically told the Chrysler/Jeep support techs what my software version was and they continued to tell me that there were no updates. Thanks a lot 1800iAmUseless email, chat, & phone support.
The big question… Is it fixed? Sort of. Yes, it’s updated but as soon as we tested it again after the update, the phone dropped off again. It took longer than the usual 27 seconds, but it still happened at the dealership. They don’t want to take any chances so they are going to swap out the head unit. That being said, it hasn’t dropped off once since then. I’m calling it fixed for now until it gets fixed again aka replaced.
Out of the blue the other day, my uConnect 430N suddenly dropped the bluetooth connection to my phone. Wha? Why?
The Dirty Details
Device: uConnect 430N
Software Version: 44.00.01
Phone: iPhone5, iOS 7.0.5
The problem started on or around 19Feb2014. The iPhone connects immediately, then drops the bluetooth connection after 30 seconds and then reconnects a few seconds later only to repeat the process over and over. There are no new devices in my Jeep that might be causing signal interference, the iPhone is the same one I’ve had for almost a year, there were no updates pushed to either device around the date the problem started. The iPhone connects via Bluetooth to all other devices without any issues.
I’ve already tried…
Power cycling the iPhone
Power cycling the uConnect head unit
Factory resetting the uConnect head units phone pairing
Removing the paired connection from the iPhone
Removing the contact sync features
Pairing again from scratch
1800iAmUseless Chat Support
The uConnect techs claim that there hasn’t been a software update pushed wirelessly and uConnect doesn’t support beyond iOS 7.0.2. However, the connection had no problems for the past 5 months regardless of upgrades from 7.0.2 > 7.0.3 > 7.0.4 > 7.0.5. My current best guess is that the bluetooth module in the 430N has failed or is experiencing intermittent power contact.
After spending a little more time trouble shooting this issue over the past few days, I timed the connection drops and found them to occur exactly every 27 seconds. I’ve also gotten my hands on another iPhone5, this one with iOS 6.1.4 and another hands-free Bluetooth system (Audi’s MMI). I tested my iPhone (iOS 7.0.6) on the Audi MMI and it worked flawlessly. I then tested the iPhone 5 running iOS 6.1.4 on the uConnect and it also operated flawlessly. The interesting part is after testing my uConnect using the 6.1.4 iPhone and then resetting the uConnect system, my iPhone (7.0.6) started working again just fine. It did so for about 15-20 minutes, and then started to drop the connection again as usual. I power cycled the iPhone (7.0.6) and it connected again for a time, but then went back to it’s old 27 second drop off plan. My new theory… Gremlins! Yup, deff gremlins in the uConnect.
Another discussion with the tech support guys have found me doing a full system restore on the iPhone 5 (iOS 7.0.6), a reset to the uConnect 430N, repaired both, tested again and that did absolutely no good. Same connection dropping results. I’ve checked over the Jeep and there are no electronics or even new light bulbs running that hadn’t been running before this problem started. I’m a little stumped as to what else I can check or test at this point.
Per Chrysler support (yes, again), I performed a soft reset of the 430n, and then retested the Bluetooth connection. No change. I also tried pulling the battery connection for 45+ mins, & retesting. Again, no new results.
Back to the drawing board.
After slapping on the new tires, I needed to recalibrate my speedo. I know most folks use a FlashCal or a ProCal, both of which are fantastic devices, but earlier this year I picked up an Aeroforce Tech Interceptor gauge to go in the center of my sPOD. This gauge also features two way communications, a feature that I have yet to take advantage of until now. I flipped through the internets and found an older thread, but still a solid read on JK Forum that gave a good description on how to set your speedo for your new tire size. The OP says “The Tire Size is entered based upon circumference in millimeters. Here’s a little chart to make it easier: (You should round the number e.g. 2656.8 = 02657)”
Starting with that calculation pic, I went to the garage to measure the circumference of my tires using a very scientific method… I wrapped a string around my spare to get 2788 mm. When I tried using that setting, my speedo was waaaaaaaaaaay off. On a side note, for those of us with OEM NAV’s, the speedo on the instrument panel and the speed display on the NAV come from the same source. One isn’t a GPS based number.
After quite a bit of trial and error testing, the perfect measurement to get the speedo to line up with the GPS was actually 2643 mm (or the same revs as a 33.125″ tall tire). Either there’s a been a change to how the 2013’s calculate speed and distance (possible, but unlikely) or a tire under weight actually does compress THAT much. Wow! Did I just learn something new?
From the ground up, the half way point (center of the center cap) is at 17 3/8’s. That translates into a (17.375 * 2) 34.75″ true height. Sooo maybe my math is wonky somewhere or I have no clue how it’s properly calculated. The important thing is that the speedo is dead on accurate and so is the odo. I’m just going to attribute the need to use 2643mm to umm… gremlins. Yup, gremlins.