Hi All,

Sorry to start a new topic on this...

I am really struggling to get to the bottom of this.

As I understand it - my 2020 Superb has an MIB3 unit. I have updated it to version 330 with the help of @travs and others. It seems that my unit does NOT support wireless Android Auto (WAA), as it is too early to do so, however, when starting my car with my phone paired, the phone says "wireless android auto available, continue on your car screen". I can't seem to invoke WAA from the car side or the phone side, it simply says that it is available. Do we know if this is something that can be enabled with a further software update? Or some sort of setting with VCS? Native Wireless AA would be preferable... Am I right in saying that later models DO have WAA?

As a separate issue - I also have 2 AAwireless units (a "1" and a "2+"). When plugging these in and pairing with them, they work when plugged in for the first time, but at the end of the journey and at the start of the next, they both fail to connect. I have managed to get around this by going into my phone's android auto settings and selecting "Forget all vehicles" in the "connected vehicles" section - but this is a bit dull... as this needs to be done before each drive, and even if doing so - it still fails to connect sometimes.... I got in touch with AAwireless about this, they say that they can't offer any support as the car "falsely advertises wireless android auto"...

I have also got a Motorola MA1, but this behaviour also seems to be the same with this adapter... To be clear, I am not trying to use any of these adapters together, they are all being individually plugged in etc.

I'm wondering if this has something to do with the constantly powered USB sockets - maybe the various wireless units are expecting a power cycle between connections?

Has anyone else had these issues and overcome them? If so, how!?

I know I could just plug in which works fine when the car is stationary, but as soon as I start driving - it becomes incredibly unstable and just constantly disconnects and reconnects... I'm getting a bit frustrated as I had perfect WAA in my old mk2 Superb with an aftermarket Sony head unit and a AAWireless dongle..

Any help would be very much appreciated.

Many thanks,

G.

You’d think that everything would be simple but there may be crossover issues. There’s plenty of examples of facelift 0.5 models where some things are upgraded and others aren’t.

I had an Audi B5 S4 which was known as a 1999.5 model - most facelifted items but still has an analogue clock in the dash - they obviously had a surplus to use up.

I was hoping to have my Haldex tuned for permanent 50:50 but it turns out my Haldex controller is a revised part that can’t be written to (or written to yet).

AAWireless are talking rubbish. It’s none of their business what the car advertises or doesn’t. It’s a bull**** line to fob you but you might as well take it, they’re not going to help. My bet is they’ know they’ll not be able to help but don’t want the narrative to be that they weren’t competent.

I’d say the power cycle thing is possible for one unit but the chance it’s written into the code of two completely different units when they should just be able to hot plug (connect when on) would be much rarer. I think. But also you might get around it by unplugging them and plugging them in each journey. That would simulate a power cycle? Bit of a faff but less than going into phone settings menus.

Is the wired connection bad on both the USBC and the USBA in the armrest? If not the latter, perhaps try using that and leave the USB-C for occasional power? Or does it lose power connection as well as data connection?

Thanks for your response @travs, yeah, I agree. It's nonsense from AAwireless...

Yep, wired connection is bad through both ports, I'm going to try and get skoda to look into this when they see it later this month...

Interestingly, I just went out to the car to mess with this a bit more... When I hit the info button on the Android Auto/carplay/miracast page, it says the following in the Android auto section:

Clearly states that Android Auto wireless is available but that it has to be invoked from a wired connection first... (I have tried this... It doesn't work).. gah, inconsistencies everywhere!

5 hours ago, gr0m1t said:

Yep, wired connection is bad through both ports, I'm going to try and get skoda to look into this when they see it later this month...

If ur wired connection is sketchy, then don't blame AAWireless!

As u said - it worked fine with ur MK2 Superb before.

U need to sort out ur USB ports and/or MIB3 unit.

I'll screenshot the settings of my AAWireless and share that with u.

That's a fair point @JR RS, however I will note that when the AAwireless adapter is connected it is rock solid...

I suppose that the other variable here is my phone... I don't have a spare phone to test with though...

My '22 model has wireless AA, I didn't know it did when I bought it last year but after pairing my phone to the car via BT it popped up the option to wirelessly connect to AA. Now and then it does fail to connect to my phone and needs a reboot, maybe you could try that? Hold the power button down on the HU for about 10 seconds until it reboots with the skoda logo.

Re AAWireless wired issues. I've had AAWireless since the original KickStarter release (my old car and partners car), wired issues are usually a bad cable.

Edited 31 July, 202531 Jul by Dave77

3 hours ago, Dave77 said:

My '22 model has wireless AA, I didn't know it did when I bought it last year but after pairing my phone to the car via BT it popped up the option to wirelessly connect to AA. Now and then it does fail to connect to my phone and needs a reboot, maybe you could try that? Hold the power button down on the HU for about 10 seconds until it reboots with the skoda logo.

Re AAWireless wired issues. I've had AAWireless since the original KickStarter release (my old car and partners car), wired issues are usually a bad cable.

Hey @Dave77 thanks for that. I have also had AAwireless since the original indegogo... I've still got the original cable, but have tried many over the last week or so with this issue...

Jealous of your '22 car just working!

@gr0m1t - here r screenshots of my AAWireless settings.

My phone is a Google Pixel 5.

I have a MY17 Superb with the Columbus MIB2.5 infotainment.

Thanks @JR RS, I'll emulate those on my unit and let you know what happens!

Thanks 😊

Had a go with this today @JR RS, unfortunately no joy... It won't connect at all now...

I get the feeling that there is some sort of conflict on the phone because the phone insists that wireless android auto exists.. but the car doesn't want to play ball. I suspect you are having success in your 2.5MIB because there is not any kind of wireless option and thus the AAwireless works for you... Where as on MIB3 there is wireless somewhere in the chain so a conflict appears...

This is just a guess mind you, I could be completely wrong...

Humour me... I just asked chatGPT about this issue and about the issue I am having with setting the primary user in my vehicle... Gpt said this:

"The root cause is likely:

A MIB3 software bug (332 is known to have intermittent issues with wireless projection and user binding)

A locked Primary User state, limiting certain wireless functions

Possibly an unstable Wi-Fi module handshake, which gets fixed in later MIB software"

Later it states this again with this line:

"MIB3 vehicles often limit wireless projection, profiles, or cloud services until a Primary User is successfully assigned.

You’re currently in “Guest” or “limited” mode."

The entry about a locked or guest user state has grabbed my attention... Is this a thing that anyone knows of? Or is it gpt going off at a tangent?

It feels to me like the two issues are linked, but I don't want to draw lines where there are no dots!

Edited 3 August, 20253 Aug by gr0m1t
Clarity

It’s not going off on a tangent as such, it’s using accurate technical terminology to sound like it knows what it’s talking about.

Problem is, as far as we know there isn’t a later software than v332.

If you told it you were on 332, it’s likely it’s just told you later software has a fix for it because that’s an obvious thing to say.

Would be good to find that’s the issue but nothing to corroborate at the mo…

Edited 4 August, 20254 Aug by travs

I have seen numerous discussions about peeps (with MIB3) struggling with setting up Primary Users, so ur finding is quite possible that it is in turn messing up ur built-in wireless.

I wonder if there is a way to disable native wireless on the MIB3 unit, so it stops causing confusion with Android Auto.

9 hours ago, gr0m1t said:

"MIB3 vehicles often limit wireless projection, profiles, or cloud services until a Primary User is successfully assigned.

I said in one of your other threads that without Primary User setup weird things happen.

It's booked in to Skoda Winchester on the 21st, so hopefully they can get to the bottom of it... Software on cars... 🙄

Thanks for your help, both 🙂

50 minutes ago, logiclee said:

I said in one of your other threads that without Primary User setup weird things happen.

That you did @logiclee!

19 hours ago, gr0m1t said:

A MIB3 software bug (332 is known to have intermittent issues with wireless projection and user binding)

I have 332, wireless AA is fine with it. Have you not got a Primary User setup?

I would start from scratch, delete all connections from your phone, eg Skoda BT/AAWireless, delete all BT connections from the car. Then pair your phone to the car via BT and see if you get the option to connect wirelessly to AA when going to the SmartLink screen. Make sure AAWireless is not plugged in!

What phone do you have?

Edited 4 August, 20254 Aug by Dave77

9 hours ago, gr0m1t said:

It's booked in to Skoda Winchester on the 21st, so hopefully they can get to the bottom of it... Software on cars... 🙄

Thanks for your help, both 🙂

Brockenhurst Skoda (Meadens) are very good - I'd rather go to them than Winchester or anywhere Richmond related.

3 hours ago, Dave77 said:

I have 332, wireless AA is fine with it. Have you not got a Primary User setup?

I would start from scratch, delete all connections from your phone, eg Skoda BT/AAWireless, delete all BT connections from the car. Then pair your phone to the car via BT and see if you get the option to connect wirelessly to AA when going to the SmartLink screen. Make sure AAWireless is not plugged in!

What phone do you have?

Hey @Dave77, thanks for this. Yeah, done this process multiple times.. unfortunately the wireless option just never appears... I have given up on AAwireless, it's long unplugged! I have a pixel 6, I have also tried with my wife's pixel 9 and my next-door neighbours One Plus Nord CE. I haven't tried an iPhone, but that's fairly pointless anyway, I don't really care if carplay works, I'm not switching to iPhone!

Yeah, I can't set my user (or any user for that matter) as primary user, it just fails... I have tried multiple (10x +) times, the car just doesn't ever progress beyond the loading screen. I have used several locations, combinations of different keys, all sorts...! Very open to suggestions though!

@OccyVRS thanks for the Meadens suggestion, I'm based near Oxford and it's already a fair trek to Winchester, I think I'll give them a crack, and then see what happens... If they fail, I'll give Meadens a call! Thanks for the tip!

Odd, mine works currently with a Pixel 9 and worked with a Pixel 6 last year. Hopefully the dealer can sort it out

I had a Pixel 5 before, now I have a Pixel 8 - both play nicely with AAWireless.

@Dave77 & @JR RS Looks like pixel+superb is a popular combination!

@OccyVRS I called Meadens, they were incredibly helpful but only had an appointment in mid September, I've booked that in case Winchester can't sort it... Hopefully they can!

I think priority needs to be

1. Assign primary user.

2. Do the ports work and wired Android Auto

3. Does the car have wireless Android Auto or not.

4. Play with wireless dongles.

28 minutes ago, gr0m1t said:

@Dave77 & @JR RS Looks like pixel+superb is a popular combination!

@OccyVRS I called Meadens, they were incredibly helpful but only had an appointment in mid September, I've booked that in case Winchester can't sort it... Hopefully they can!

I only go to Indies, but if I ever need a dealer I'm genuinely not sure where I'll go. I've moved home from university now, and while my local dealer at home is the one that sold me the car, they also sold me the crash damaged Leon before it and lied to me, numerous times, about multiple things.

Meadens Brockenhurst are the only main dealer I've ever had a positive experience with and I've dealt with quite a few. Their wait times are probably so long because they've only got a small workshop (full of horses, lol) and they've got a good reputation.

I agree with @logiclee - very logical. Delete everything that's currently paired, reset the entire system (make a note of any settings you have) and try again.

As an aside, I've got fed up with the cable in my car and have just bought a Quadlock CarPlay/AA adapter - it's worked flawlessly itself, although my infotainment system (MIB2.5) did freeze entirely last night. These systems are just crap - when using a cable, mine would disconnect every few days, for no reason at all. My Leon used to freeze when it was cold, literally. Often the cold weather would trigger the TPMS warning (no idea why) and I would have to wait until the screen had thawed before I could reset it.

The Quadlock adapter is really small, so it plugs into the USB port by the shifter, with no need for a cable - I'm not sure what the Superb layout is, but it was the only adapter I could find that would fit nicely and wouldn't catch fire.

Edited 5 August, 20255 Aug by OccyVRS