The missing XM and FM and AM tuners happened to me after I reset with three finger reboot. I believe there's a way active via the service menus or I simply rebooted a few more times until they were found.

 

RDX A-Spec, 3 months old, 4,000 miles. Looking back, I do think I tried to change drive modes in reverse and/or before it booted up. Screen seems to switch between day and night mode. Error banner on bottom of screen says drive mode not available. Reset system twice (not the Factory reset). Problem persists. Anyone find a solution, whether through a dealer fix or personally troubleshooting?

Only a hardware malfunction makes sense. However, when going into Dealer Diagnostic mode, I did notice a lot of errors
in the error log. Has anyone tried clearing those?

 

These issues and then some have been happening since the release of the Gen 3 RDX. Going beyond the 1 year mark now for a lot of us. I say again that I seriously doubt that ACURA will EVER fix the infotainment related issues as in NEVER. The Dealers do not even admit that these are issues, All I get as well as others is "Well - hooked up diags and did not show a problem". WAKE UP PEOPLE. Wait until someone really needs the safety features that more than likely do not work properly either.

 

For me, just turn off the car and exit, wait about 20 min and come back to restart it should clear this up.

 

I've never had this issue before, but I just updated system to D.1.2.2 and sure enough the Nav display flashes from day to night and a banner flashes "Drive Mode Change Unavailable." Does the same where on main or side screen. Very annoying. Drive mode works fine as many of you found. I will leave overnight and hope it goes away, but if it doesn't appears that dealers are ignorant about this issue which isn't encouraging. I probably should not have updated since everything was working well before the update.

 

There is a TSB that addresses this very issue. It requires the replacement of the center gauge cluster. The cluster has a component that has bad software. I recently had mine done 2 times( 1st replacement didn’t work because the first cluster had the same bad software). I first had it done right after the TSB came out. Acura authorized another replacement when I had the error come back. Since the second replacement everything has been good. Here is the TSB.

http://www.urvi.net/forumfiles/SB/B20-001.PDF

 

Got it! If it doesn't disappear I'll contact Acura dealership and inform them of this TSB. Thanks so much.

 

Trust me it will keep coming back at random times. Acura knows about this. Take a copy of the TSB with you. Also record it with your phone to show them in case you get the standard WE CANT REPRODUCE IT excuse. I could never reproduce it for my service dept but they couldn’t deny it with the recording I had. On one occasion I drove to the dealer with it happening while I was running errands and let them sit in the drivers seat and watch it live.

 

I printed a copy and saved it electronically should the dealership plead ignorance (commonplace based on my Acura dealership experience). Thanks.

 

No problem glad to help.

 

also, think about taking a short video of the screen while it is happening. That's what I did and emailed it to the dealer. Dealer still was unsure of replacement, until I educated him.

 

The glitches don't even phase me anymore. I just know the type S is on the horizon and this rdx is getting traded in for one of them.

 

Type S = more of the Same, unless Acura gets the infotainment system software worked out.

 

Start over Acura and just put in a touchscreen. How can this still be going on? Should be interesting to see what is in the soon to be revealed TLX Type S....new infotainment hardware and software or more of the same?

 

This late into the second model year is too long to keep having these problems.

 

While I haven’t had this particular problem, I am one of the people who can't get the latest OTA update to install. This too speaks to sloppy software development from Acura. I'm definitely not impressed, and may not risk any future updates since I'm feeling fortunate to have no functionality issues currently. And, I guess this may not be software related, but still not happy seeing this stuff.