As many of you know, 3G end of life for your Sprint connected vehicle is 3/31/22 and the FCA/Stellantis plan of attack is the T-Mobile OBD-II port adapter. Knowing that the RA4 will still have connectivity until the end of March, I've refrained from taking the time to install the adapter until roughly two weeks ago.* After doing so, one night last week after driving the vehicle I get a "Vehicle Malfunction Indicator Light Alert" email telling me that my vehicle has a triggered powertrain alert and that I have 714,632 miles on my '15 R/T. Having just arrived home and with no recollection of any indicator lights on on the dash, I took a minute and went out to the vehicle and checked for any codes. No codes confirmed, pending or permanent in the system, no lights on, and of course, the odometer had not added an extra 643,169 miles while I wasn't looking... I log in to mopar.com and the mileage issue is there as well, though oddly enough the MIL was missing, still no explanation for why that was the case.
I get on the phone with Uconn Access the next day and the best they could do was to reset my account on the back end as an attempt to resolve the issue. Logging in to my account online was then showing mileage/data from October last year, but that only lasted so long before it was overtaken again with 700,000 plus miles and emailing me about another bogus MIL.
So, who else has had this issue pop up, and if so, were you able to determine the true underlying cause and find a resolution? I have been in contact with one other forum member who is also experiencing the same situation. I should be able to get some feedback from an "engineer" later today. My off the cuff guess is that there is a firmware issue with the T-Mo Adapter that is incorrectly reporting mileage a decimal off and somehow also generating bogus MILs.
*Installed it to try using it as the data source for my Escort MAXcam 360c instead of my phone.
I get on the phone with Uconn Access the next day and the best they could do was to reset my account on the back end as an attempt to resolve the issue. Logging in to my account online was then showing mileage/data from October last year, but that only lasted so long before it was overtaken again with 700,000 plus miles and emailing me about another bogus MIL.
So, who else has had this issue pop up, and if so, were you able to determine the true underlying cause and find a resolution? I have been in contact with one other forum member who is also experiencing the same situation. I should be able to get some feedback from an "engineer" later today. My off the cuff guess is that there is a firmware issue with the T-Mo Adapter that is incorrectly reporting mileage a decimal off and somehow also generating bogus MILs.
*Installed it to try using it as the data source for my Escort MAXcam 360c instead of my phone.