AA Startup Issues

[J Wadle]

I'm using Android Auto with my VW MIB II system.

Having problems with two startup scenarios as follows:

If phone is not docked when starting car (i.e. not connected to MIB II), phone connects via BT automatically. Then, once docked, it switches off BT and starts AA, but does not go to AA Home screen. I must go to Menu-AppConnect to select AA.

If phone is already docked when starting car, MIB II asks if phone is to be connected via Bluetooth and requires confirmation on phone (even though it is already paired). AA does not start automatically. I have to go to AppConnect and select phone from devices list to connect phone and start AA.

Can anyone help? Possibly settings in MIB II or AA on phone?

 

[itinj6]

Same going on with my Audi, which is essentially the same as VW. Most annoying part is if I shut my car off while it is docked and connected to AA, next time I want to use Bluetooth, I have to give it permission again to access my messages and redo the trusted devices. Don't know of any way to fix these. Think it's​ just the way VAG is.

 

[Pedrore]

There is no auto launch of AA with the MIB-II unit in my experience with a Nexus 5X and 2016 VW Golf, except if I turn off the car and leave the phone plugged in until the next startup - then it auto launches AA and carries on with whatever navigation I had going.

The request for access to your phone's text messages is coming from the MIB-II unit, not AA and for some reason the phone won't remember your answer which is annoying.

 

[Peppino158]

Hi there, so I've had the same issue with my car and found that if you keep your MIB II system in any interface but the android home screen before connecting your phone you shouldn't have any issues. Not sure why, to be honest, but it works every time! Hope this helps out

 

[J Wadle]

By "shouldn't have any issues", do you mean that the MIB II system goes to the AA home screen automatically when the phone is plugged in, or do you still have to press Menu and select AA?

 

[Peppino158]

Sorry, let me clarify myself. The menu button followed by the AA tab would need to be pressed to get it going. I found that plugging in the phone with the AA boot screen preselected leads to various connection failures. Also try switching on your usb debugging mode found in the developers opts

 

[jwboulder]

I agree. I have the same behavior with my car. I've resigned myself to having to press Menu and AA to get to AA. Right now I'm focused on inconsistent responses to voice request to play music. I've posted a separate thread on that issue.