Consistent Android Auto and Bluetooth Issues
Thread Starter
AudiWorld Newcomer
Joined: Mar 2020
Posts: 1
Likes: 0
Consistent Android Auto and Bluetooth Issues
I have a 2018 A3 eTron and my wife has a 2019 Q5. We both have the same problem and Audi's response was just dumb.
We both use Android Auto. We connect the phone to the car using the Audi USB cable. Calls can happen and we can see the calls on the Android Auto screen, but we cannot hear the caller. Callers can hear us, but we cannot hear them. We have both tried starting the car and letting the car connect to BT first then to AA and also tried plugging in the phone prior to starting and allowing the car to connect to the phone during the AA boot-up sequence. When a call comes through I politely tell the caller I'm having BT issues and to call me back in two minutes. Unplug the phone disconnecting AA and reconnect the phone and allow AA to boot once again. Generally, this fixes the issue and the phone, BT, and AA all act as normal.
Wife brought her car to Audi to have them check it out and their response was "You have to turn off BT before you connect it to your car each time you start the car." Wait, what??? It gets better. Their explanation is MMI gets confused when connecting with the USB cable and tries to turn everything on all at once. If a system fails (In this case BT) it doesn't know it or understand it so it remains off. They cleared the memory in the MMI and had my wife delete the BT profile in her phone that matched to the car and had her connect to the car once again, this time with the BT off. The system connected and created a new BT profile on the phone and worked as normal.
Now we have to turn off BT each time we start our car if we want to use a feature that is advertised. I understand this isn't that big of an issue and it only takes a moment of my time, but I travel for work and always get a rental car that has AA. I have yet to find any other brand or model of car that exhibits the same issues. I am absolutely disgusted with Audi giving the service department scripts to go off of so Audi has no liability or responsibility to fix. This is 100% an Audi issue and they should fix it.
Does anyone have any remedies to this issue or any ideas on how to force Audi to fix it in a patch to MMI?
We both use Android Auto. We connect the phone to the car using the Audi USB cable. Calls can happen and we can see the calls on the Android Auto screen, but we cannot hear the caller. Callers can hear us, but we cannot hear them. We have both tried starting the car and letting the car connect to BT first then to AA and also tried plugging in the phone prior to starting and allowing the car to connect to the phone during the AA boot-up sequence. When a call comes through I politely tell the caller I'm having BT issues and to call me back in two minutes. Unplug the phone disconnecting AA and reconnect the phone and allow AA to boot once again. Generally, this fixes the issue and the phone, BT, and AA all act as normal.
Wife brought her car to Audi to have them check it out and their response was "You have to turn off BT before you connect it to your car each time you start the car." Wait, what??? It gets better. Their explanation is MMI gets confused when connecting with the USB cable and tries to turn everything on all at once. If a system fails (In this case BT) it doesn't know it or understand it so it remains off. They cleared the memory in the MMI and had my wife delete the BT profile in her phone that matched to the car and had her connect to the car once again, this time with the BT off. The system connected and created a new BT profile on the phone and worked as normal.
Now we have to turn off BT each time we start our car if we want to use a feature that is advertised. I understand this isn't that big of an issue and it only takes a moment of my time, but I travel for work and always get a rental car that has AA. I have yet to find any other brand or model of car that exhibits the same issues. I am absolutely disgusted with Audi giving the service department scripts to go off of so Audi has no liability or responsibility to fix. This is 100% an Audi issue and they should fix it.
Does anyone have any remedies to this issue or any ideas on how to force Audi to fix it in a patch to MMI?
Thread
Thread Starter
Forum
Replies
Last Post
82DMC12
Q5/SQ5 MKII Discussion
6
Oct 25, 2019 05:33 PM
