2004 to 2020 Mazda 3 Forum and Mazdaspeed 3 Forums banner

AIO - All-In-One tweaks

4.2M views 9.8K replies 2K participants last post by  dilen29.71  
In this github link is also mentioned "But the AIO version of AA is not working with FW 70.".

It is possible to downgrade at least from 70.00.021 and 70.00.100 to FW 59 - as far as 59.00.502. Downgrading from 70.00.335 is also possible, but some files remain .335 until a certain firmware downwards (some FW 59), as far as I remember - for details read the other threads from about 2-3 month ago - e.g. this one or the ID7v2 thread. Example: A downgrade from .335 to 59.00.545 does not restore the possibility to use the serial access for old ID7.
Hi Tristan, anderml1955, Albuyeh can you guys please clarify, from your experienced and expertise.

all upgrade and downgrade are using old usb+hub.

1. So currently im on fw59.00.502 ADR (old cable+hub) with no tweaks just id7 serial-ttl(version 1) working and if i update to fw v70.00.335 ADR my id7 (version 1) will be erase if i dont id7(version 2) during installation ended at acc reboot screen.

2. if i did serial-ttl in at the end of fw70.00.335 ADR upgrade before rebooting cmu (not pressing ACC) with ID7 (version 2) i can install aio tweaks? (login/pass cmu/jc works?) but Aio AA audio will not work.

3. If i want to downgrade back to fw 59.00.502 ADR it is possible, but i still can install aio tweaks because i installed ID7 (version 2) when i had fw70.00.335 ADR before? dont need to serial-ttl again? login/pass retained cmu/jci?

4. Or when i downgrade from fw70.00.335 ADR even with ID7 (version 2) installed, i still need to serial-ttl into cmu end of fw v59.00.502 ADR installation before rebooting cmu and install ID7 (version 2, version 1 do not work?) to able to install aio tweaks from old usb+hub again? and (login/pass cmu/jci for root access working?)

5. Or once upgraded to fw70.00.335 ADR. i must serial-ttl installed ID7 (version 2) from usb xx folder regardless of FW downgrade or upgrade to .335 again in the future before rebooting cmu which is at the end of each fw installation? because ID7 (version 1) is no longer possible ever again? And id7v2 gets deleted each time?

hope u can clear this up for me and everyone who is unsure or wanted to update or downgrading. Thank you.

*reason fw70.00.335 ADR runs/boot up faster/smoother better responsive less bugs, regardless if the car switch off over night or recently off 1hrs ago. fw59.00.. takes longer to boot and lags in those situations and when too many tweaks installed. fw70.00335 ADR cannot install too many tweaks? memory/space issue? because of official AA/ACP using up mem/space?
 
This version was working great, but is now prone to the crash issue. That is why I upgraded to AIO 2.8.5.
Hi, MZD2k16.
Do u have old usb hub or new usb? And are u saying the latest AIO v2.8.5 AA is working with sound etc with your fw70.00.100? No issues whatsoever? Can someone confirm if this it true for latest aio v2.8.5 Android auto on fw70 with old and new usb hub? Thanks.

@Tristan-cx5, can u confirm/test newer version of aio v2.8.5 Android auto on fw70.00.352 working for u with sound etc, no black screen, please according to Mzd2k16 says. Thank you.

@MZD2k16 Aio v2.8.5 Android auto v1.12 compatible with fw70 regardless of old or new usb hub?
 
Will v59.00.546 NA and aio AA work with the retrofit hub ?
Info from @MZD2k16 @turd till the turns "New USB hub is a requirement only for the official Mazda AA implementation. It was never a requirement for Aio, regardless of firmware version". His firmware version is 59.00.449, sounds working. Im guessing his using retrofit new usb hub.

Latest fix applied to AA version 1.12 mod(s). Due to pause/resume not working properly after audio focus switching.

https://easyupload.io/asarh6 v1.12 mod updated press end calls switch audio focus, hold it 2sec+ return to mazda main screen or hold back button down 2sec+ will also do the same thing. Fav* pause/resume AA audio.

Please test/give feedback. Thanks.
 
Hi, I tried the following:
  • Remove all AIO tweaks including AA.
  • Restart the CMU to factory reset.
  • Install AA from AIO 2.8.5.
  • Clean the AA cache on my smartphone.
The issue still appears. No matters if my phone is connected or not. The mazda menu shows the "can't connect" issue under the AA option. So I think it's an AIO problem with the 2.8.5 version.
Turn on developer mode on your Android phone in settings and enable developer mode in android auto app on your phone and then reconnect, make sure you use a good usb data cable.
 
I managed to run AA 1.12 with some issues and then ran AA1.12 Mod which is running well, one thing that I noticed on AA. 1.12 was the Google Map alert would be heard intermittently while listening to the FM radio, the audio would switch back and forth. But in the Mod version it wouldn't.

Also in the Mod version, pressing the end call button while in Bluetooth audio will switch to the radio but will not always switch back.
The v1.12 mod end calls button is only for switching to radio focus; that is its main purpose and ending during a call. it is never intended for switching back to Bluetooth audio. U must use *fav button to switch back to Bluetooth audio, pause & resume playback; which is what its programmed to do for this particular mod and its does an excellent job. The original v1.12 will not resume/paused Bluetooth playback after switching to radio focus audio, it will skip to the next song instead. This is the fix for it in the mod version.
 
I was trying the 1.12 mod version this morning. I think I used it correctly, but let me know if this is wrong. I compiled a new AIO with AA 1.12 and then copied over the files extracted from the 'trez_mod' zip file onto the USB drive. The install seemed to work. AA now launches quicker and seems to handle music and nav speech much better. However, I have the same jumpy blue arrow problem that I saw with the non mod 1.12 before applying the compass 180 degrees fix.
Is there a way to work that compass fix into the 1.12 mod install?
Just copy the single "headunit" file only in the trez mod.zip to your newly complied aio AA v1.12 with the 180 degrees compass fix and your issue should be solved for navigation.
 
Hello Guys
I have an big Problem with AIO.
I have installed AIO with some tweaks and a theme on my Mazda 6 with Version 59.00.544 EU (yes i have doing the SSH bringback via cable) for a while.

Today i want to recover everthing
to original. I have a Backup and compiled everything to USB Stick. But the Installer dont Start with my USB Stick (fat32). I have tried different Sticks and tried everything with AIO. I dont can get the USB Installation to start! I dont know what im doing wrong. The Radio Shows that the Stick is Connect and can read it. But the Installer dont Start. I have the AIO tweaks App installed, too.
If you have ssh access to the CMU, try erasing the content (all .bz2 files) in the folder "/tmp/mnt/data_persist/log/dumps/", and then re-execute again. The folder is full of log files with a total size of more than 400MB, preventing the system from executing any tweaks.
Run command:
Df -h
to see amount of data/space used in mmcblck0p2.

if you get an error on executing "rm -f /tmp/mnt/data_persist/log/dumps/*.bz2"

Try the following below 1st then re-run above command again:

rm -f /tmp/mnt/data_persist/log/dumps/core9*.bz2

rm -f /tmp/mnt/data_persist/log/dumps/core8*.bz2

rm -f /tmp/mnt/data_persist/log/dumps/core1*.bz2

rm -f /tmp/mnt/data_persist/log/dumps/core0*.bz2
Put your tweaks usb into the car again and it should works.
 
I've been having some issues with android auto recently. When I'm not using my phone for audio (listening to radio), it works alright. But whenever I start using the bluetooth on my phone (spotify, directions, etc), android auto gets into a weird bootloop for a while where it crashes over and over again, then it just stops. Any idea how I'd begin to troubleshoot?
@Tjololo
It Could be your Cmu insufficient memory/diskspace which causes mazda aio AA/tweaks to loop/freezes/crashes follow these steps Android Auto Won't Launch and hopefully your issue gets resolve.
 
+1

having update to 59 and using the 1.12 AA seems all OK, AA focus on calls is working OK.

My only comment is when listening FM radio and using waze, I no longer hear alerts when my route is recalculating. only when the audio is on AA y hear the alerts.

for the side patch did you change the file (headunit.json) using 2.8.5 before install?
@rquanleon
"My only comment is when listening FM radio and using waze, I no longer hear alerts when my route is recalculating. only when the audio is on AA I hear the alerts".
‐-----------------------------------------
Hopefully this mod version can fix your problem at hand. What's your FW version?

 
Been considering the Mazda hub upgrade but since it cannot do wireless, yet, anyway I'm thinking maybe adding the necessary AIO tweaks may be better.
  • What's the best Mazda F/W version to use? Currently I'm using 70.00.100 (been using AIO since I got my car back in late '16)
  • Can you do wireless AA
  • The interest would be to use AA so which versions of apps\tweaks would one need?
  • Or is it not good enough to bother with?
  • Any other helpful details would be great.
@SBMongoos hope this answer some of your questions.

  • Best fw70? Latest is fw70.00.352 NA. (Fw70 cannot do wifi, no touch for official mazda AA, no turn by turn on HUD. No extra convenience features. (I wouldn't bother until it supports those).
  • Best fw to use would be (fw55-59) for Aio AA + wifi with all the extras. If you're on fw70 are you able to test my latest AAv1.14 mod? Thanks.
  • Information wireless for aio AA Android Auto
Please give feedback so i know if it works.

 
Is anyone familiar with a method to continue using AA with the old hub, 2016 CX5?

I'm referring to specifically AA as I recall it not being nearly as stringent on the requirements of the USB interface it uses to communicate with the headunit. Also I'm certain that at one point, before the dealer decided to update my car to 70.00.100, I had an unmodified firmware running AA great for a while with the original hub. I've tried factory resetting but still can't even see anything related to AA in the menus anymore, I'm considering updating to 70.00.352, let me know if anyone has any ideas or if there's a way I can get AA working again without buying a new expensive hub.

BTW: I have plenty of USB TTL adapters and such but would prefer solutions that don't require modding the firmware first, as long as touch works in AA...
@limitlesscodes