[Matthew53]

I see that Engineering Tool added option to activate Android Auto for MGU, but I found no more informations about that. Is this working as good as carplay activation on EVO?
 Is this possible to activate it on cars with and without telematic?

[dasi]

I see that Engineering Tool added option to activate Android Auto for MGU, but I found no more informations about that. Is this working as good as carplay activation on EVO?
 Is this possible to activate it on cars with and without telematic?

the only thing that it does it changes ANDROIDAUTO_SWT to aktiv

[pcp1234]

there are notes whats required and what software. I did few cars

[brag288]

there are notes whats required and what software. I did few cars

can you please share latest patchnotes?(just curious if its worth paying for the update or not)

[atomantmk]

2022.12.06

- add connected/online job to apply fix for CarPlay connect
issue with EVO X/Y software update

2022.9.12

- add disable DVD in adjust block function job

2022.8.15

- EntryNav2 CarPlay activation now requires long vin

[Matthew53]

This Android Auto activation require OEM 1CA, so basically this is as @dasi said - they added function that only activate AndroidAuto_swt to aktiv if you already imported OEM FSC. So I wonder what is the sense to add such functionality if you can code it in esys in 2 minutes? I was exepcting custom FSC like in the carplay. And now it looks like just a "catch" for potential ET buyers, because there isn't an information that it require OEM FSC, only MGU VIM / Android Auto.

[pshoey]

shame you didn't read the onscreen notes and instead decided to criticize - oh well!


screenshot attached!!

[Matthew53]

Yes so this is what I refer to. I don't criticize.
I just say that it should be clearly informed at the bimmercene or ET offer, because with information " MGU VIM / Android Auto" many people may think that this is the same activation method as carplay for EVO, so that it doesn't require any OEM FSC code.

When I read "MGU VIM / Android Auto" then I was sure that this is how it works, so that it use custom 1CA fsc to activate Android Auto, the same as with Carplay.


With just "MGU VIM / Android Auto" potential buyers may think "Ok, I activated many carplay EVO with that tool, it works fine, so I'm convinced to buy the tool, because now they also added option for Android Auto.

Do you now understand my point?

[dasi]

This option was added long time ago

[DayvG]

Yes so this is what I refer to. I don't criticize.
I just say that it should be clearly informed at the bimmercene or ET offer, because with information " MGU VIM / Android Auto" many people may think that this is the same activation method as carplay for EVO, so that it doesn't require any OEM FSC code.

When I read "MGU VIM / Android Auto" then I was sure that this is how it works, so that it use custom 1CA fsc to activate Android Auto, the same as with Carplay.


With just "MGU VIM / Android Auto" potential buyers may think "Ok, I activated many carplay EVO with that tool, it works fine, so I'm convinced to buy the tool, because now they also added option for Android Auto.

Do you now understand my point?

I think your misunderstanding is the issue here. If the MGU had been cracked and patched so easily with a quick feature code I think the "Hype" would have been a little greater. The job in HUET merely says "Code Android Auto" and is then elaborated on in the side window. At no point is the word "Activate" or "Enable" used. I don't see it is a catch, its merely an alternative way or coding in AA much like VIM on the MGU. If potential buyers purchase the tool thinking this without doing their own research, more fool them.