D.1.2.1 issues
#1
D.1.2.1 issues
No software is without bugs. Here are a couple bugs I experienced with D.1.2.1 update.
AndroidAuto doesn't always connect successfully.
Have to unplug, wait for a few minutes, replug the phone a few times, or reboot the infotainment. There's an issue that neither Google nor Acura acknowledged. Hope a fix will be pushed over the air soon.
Audio not available.
While switching between music apps, the audio all of a sudden became unavailable. I couldn't even use FM radio, Sirius XM, nada. Kept getting the message along the line of audio not available. As soon as I got home, I shut off and restarted the car, then everything was back to normal again. Weird bug.
Any other bugs anyone experienced?
AndroidAuto doesn't always connect successfully.
Have to unplug, wait for a few minutes, replug the phone a few times, or reboot the infotainment. There's an issue that neither Google nor Acura acknowledged. Hope a fix will be pushed over the air soon.
Audio not available.
While switching between music apps, the audio all of a sudden became unavailable. I couldn't even use FM radio, Sirius XM, nada. Kept getting the message along the line of audio not available. As soon as I got home, I shut off and restarted the car, then everything was back to normal again. Weird bug.
Any other bugs anyone experienced?
The following users liked this post:
MrmissmyTLX (12-03-2019)
#2
I have experienced the same issues you mentioned a few times. Somehow the AA connection has been more finicky in the last week or two. Since Android Auto happened to be updated around the same time, I think the issue is AA app related, and not purely from Acrua infotainment.
I did encountered once when the nagivation UI was stuck in the rerouting spinning circle.
I did encountered once when the nagivation UI was stuck in the rerouting spinning circle.
The following 2 users liked this post by russianDude:
jonarogers (11-25-2019),
MrmissmyTLX (12-03-2019)
#5
Yeah, I think the issue is with AA. When AA does work, it's wonderful, especially Google Assistant and Google Maps. Granted this is the first AA release on the RDX, hopeful future bug fixes will address these issues.
#6
No software is without bugs. Here are a couple bugs I experienced with D.1.2.1 update.
AndroidAuto doesn't always connect successfully.
Have to unplug, wait for a few minutes, replug the phone a few times, or reboot the infotainment. There's an issue that neither Google nor Acura acknowledged. Hope a fix will be pushed over the air soon.
AndroidAuto doesn't always connect successfully.
Have to unplug, wait for a few minutes, replug the phone a few times, or reboot the infotainment. There's an issue that neither Google nor Acura acknowledged. Hope a fix will be pushed over the air soon.
#7
Still having issues with Carplay disconnecting. Same phone and cable work fine in another car.Sometimes it works great for a day or 2, then it will disconnect several times for a day. It doesn't seem to matter when I plug it in. I've tried it before starting the car, after the infotainment boots up completely, or during boot up.
Trending Topics
#8
I use the USB for my music and have a new issue since the D.1.2.1 update. I've been playing with the music folders (even before the new update) and have found that with me anyway, that the system performs better without folders. I use the "Random" play all the time. Lets say I have 20 folders, one for each artist. Out of those 20 folders it would mostly play songs from about the same 5 or 6 folders all the time. So I decided to do away with the folders and just have all the songs on the USB stick and no folders. Random still seems to pick the same dozen or so songs with a different song every once in awhile. So now I just play them in alphabetical order.
Since the update, after awhile I would be playing down to the songs that start with the letter "D" and the next time I would start the car after 5-6 starts, the system would start from "A" again. The other day I was down to the "L" and sure enough got in the car and it started from "A" again. The USB stick was never removed at anytime.
Since the update, after awhile I would be playing down to the songs that start with the letter "D" and the next time I would start the car after 5-6 starts, the system would start from "A" again. The other day I was down to the "L" and sure enough got in the car and it started from "A" again. The USB stick was never removed at anytime.
The following users liked this post:
MrmissmyTLX (12-03-2019)
#9
Still having issues with Carplay disconnecting. Same phone and cable work fine in another car.Sometimes it works great for a day or 2, then it will disconnect several times for a day. It doesn't seem to matter when I plug it in. I've tried it before starting the car, after the infotainment boots up completely, or during boot up.
The following users liked this post:
MrmissmyTLX (12-04-2019)
#10
But it does get the job done...
The following users liked this post:
Padre Dave (12-12-2019)
#13
No software is without bugs. Here are a couple bugs I experienced with D.1.2.1 update.
AndroidAuto doesn't always connect successfully.
Have to unplug, wait for a few minutes, replug the phone a few times, or reboot the infotainment. There's an issue that neither Google nor Acura acknowledged. Hope a fix will be pushed over the air soon.
Audio not available.
While switching between music apps, the audio all of a sudden became unavailable. I couldn't even use FM radio, Sirius XM, nada. Kept getting the message along the line of audio not available. As soon as I got home, I shut off and restarted the car, then everything was back to normal again. Weird bug.
Any other bugs anyone experienced?
AndroidAuto doesn't always connect successfully.
Have to unplug, wait for a few minutes, replug the phone a few times, or reboot the infotainment. There's an issue that neither Google nor Acura acknowledged. Hope a fix will be pushed over the air soon.
Audio not available.
While switching between music apps, the audio all of a sudden became unavailable. I couldn't even use FM radio, Sirius XM, nada. Kept getting the message along the line of audio not available. As soon as I got home, I shut off and restarted the car, then everything was back to normal again. Weird bug.
Any other bugs anyone experienced?
#15
#16
Well I got my car back today and after talking with the techs at the dealer and Acura they could not find any hardware faults with the system. The techs could not find any obvious software issues. My service manager wants me to document every instance in detail again if I get the blue screen Network Comm Error again. He has listened to all my concerns and probable causes. While they had my car the loaner RDX they gave me got the same error and another customer also came in with it so Acura is very aware of the problem. They did not do a factory reset at all. At least I have no more Car Play disconnects. Me personally I thinks it’s the main harness for the USB causing the issue.
#18
Got the blue screen of frustration again today leaving work while using Car Play. Waze on the main screen as a rolling map and music from my iPhone playing on the secondary screen. System rebooted just like before and picked up where it left off. More of these????????????????????????????????????
#19
May be jinxing myself, but I haven't seen the bsof (blue screen of frustration) using AA. Though, AA connection does fail at times (old news by now). I have found yet another interim workaround, or rather an indication before plugging the phone in that seems to guarantee the connection will work. After the infotainment is started, without plugging the phone in first, if the secondary info screen (on the right) shows the AA logo instead of a black screen, plugging in the phone seems to work fine. When it's black, no AA logo, plugging in the phone would fail to connect 99% of the time. So, if I don't see the AA logo, I would restart the Infotainment.
#21
#24
Only problem is that when I drove out of the dealership, none of the behaviors changed! Still, after around 5 minutes into my trip my CarPlay goes dead and in another 4-5 minutes it comes on again. The dealer must have installed it in a different place than a OTA installation happens. In the system, under Updates, is a file called like “Update History” and my file is empty......Who knows what lurks in other sectors of the system.....
#25
When I saw that this was listed as a Recall on the Acura website, I decided to give my selling dealership another chance. This time excellent scheduling, much more competent Service Writer and was done in an hour!
Only problem is that when I drove out of the dealership, none of the behaviors changed! Still, after around 5 minutes into my trip my CarPlay goes dead and in another 4-5 minutes it comes on again. The dealer must have installed it in a different place than a OTA installation happens. In the system, under Updates, is a file called like “Update History” and my file is empty......Who knows what lurks in other sectors of the system.....
Only problem is that when I drove out of the dealership, none of the behaviors changed! Still, after around 5 minutes into my trip my CarPlay goes dead and in another 4-5 minutes it comes on again. The dealer must have installed it in a different place than a OTA installation happens. In the system, under Updates, is a file called like “Update History” and my file is empty......Who knows what lurks in other sectors of the system.....
I was told, if you connect to the dealership wifi and do the update there, the car might no longer update from your home wifi, till they fix something in their backend, which could take up to a couple days. So the sales rep told me not to connect to the dealer wifi at all and save the trouble.
I thought it was weird but who knows, what all they do in the backend in the name of ‘security’.
#26
This could be total misinformation as it came from the sales person;
I was told, if you connect to the dealership wifi and do the update there, the car might no longer update from your home wifi, till they fix something in their backend, which could take up to a couple days. So the sales rep told me not to connect to the dealer wifi at all and save the trouble.
I thought it was weird but who knows, what all they do in the backend in the name of ‘security’.
I was told, if you connect to the dealership wifi and do the update there, the car might no longer update from your home wifi, till they fix something in their backend, which could take up to a couple days. So the sales rep told me not to connect to the dealer wifi at all and save the trouble.
I thought it was weird but who knows, what all they do in the backend in the name of ‘security’.
Getting a knee replaced and the incision getting infected means I am driving to the surgeon’s office more often. In my round trip today (about 45 miles) the Apple CarPlay quit 3 times, and returned to service about 4-5 minutes later. Now I am getting aggravated......
#28
I finally have a date for the District Service Manager to reprogram my car with Acura so I can get updates. I was right....when they installed the replacement ECU Acura computer found a mismatch between my VIN and ECU so it wouldn’t recognize my car as one to update. My last visit to the dealer proved my point when the tech tried to manually install all of the updates and the Acura system wouldn’t let him. My car was apparently the first one like this, and the whole COVID-19 thing has prevented the DSM from traveling, but now he can. YEAH!
Thread
Thread Starter
Forum
Replies
Last Post
WHS_DarthVADERTL
4G TL Audio, Bluetooth, Electronics & Navigation
4
10-20-2012 06:37 PM