Ugh... no offense, man but if you are going to do this you really need to READ EVERYTHING. The thing that broke your BT was Android Auto. That is clearly documented
everywhere. "Installed a few things like Warnings"... no Android Auto is not a 'few things'. Try it again WITH OUT AA. Everything else works well. There's another step to enabling WiFi but I don't recommend that one either.
Removing Touch also lets you read your Text Messages while moving and eanbles all touch, you were right about that. Can even spin your radio dial.
.
Pagin_DrBurgos: there are a lot of reasons. The very least of which is the fact that very few cars lock you out of your touchscreen while driving. This alone drives me nuts. So, we have to assume if everyone can touch their screens they are going to crash? Come on. Don't nanny me, Mazda (raises fist to the sky). I am responsible enough not to kill myself when using a touch screen. And why should my passenger be locked out?
The disclaimer drives me nuts, too. I will have this car for at least 5 years. Must I see that thing every single time I start the car?
At the very least, read the FAQ:
https://mazdatweaks.com/faq/
Why are there 2 versions of Android Auto?
Android Auto is an ongoing development by many developers all around the world. At a certain point in its development the code was refactored to allow a better connection between the phone and the CMU, as a result a bug emerged that would drop every incoming call so a fix was developed to reroute phone calls back to the phone, this is now the less severe ‘Bluetooth-call bug’ that exists in AA ver.1.02.
Before this point calls could be made with the native Mazda Bluetooth calling interface and once a call was connected AA would display the connected call (and often freeze), so the Android Auto calling interface was never in a fully working state. AA v0.99 is the last version that AIO offered that allowed for calls to be made with the Mazda Bluetooth calling interface.
Although AA v1.02 contains the ‘Bluetooth-call bug’ it is overall much more stable than AA v0.99. In fact many bugs and issues were resolved more easily mostly due to the change that led to the bug being introduced in the first place. Developers are continuing to work on fixing the bug and ask that users don’t report issues and bugs from v0.99 as they have already been addressed.
Also, before giving up on connecting AA v0.99 try 3 or 4 times because it takes an average or 3 tries to get it started.
AA v1.02 will automatically start with no problem when a compatible phone with the Android Auto app installed is plugged in.