AIO - All-In-One tweaks
7961 - 7980 of 9380 Posts
Joined
·
2,453 Posts
No need to downgrade, as you will have to do a serial access at both FW versions.
For .352 see the ID7v2 serial access: www.mazdatweaks.com/id7 (and as basic knowledge: www.mazdatweaks.com/serial). You most probably can install .352 over .352 again (as this worked at .335) and then do the ID7v2 serial access directly at/after the update.
For .352 see the ID7v2 serial access: www.mazdatweaks.com/id7 (and as basic knowledge: www.mazdatweaks.com/serial). You most probably can install .352 over .352 again (as this worked at .335) and then do the ID7v2 serial access directly at/after the update.
Any chance of another Android Auto update coming? The latest version works well, but the following issues persists:
1. Most of my phone calls cause AA to lose video focus and go to the Mazda call screen instead.
2. Switching from radio to Spotify on AA is very hit or miss. Sometimes I am able to switch audio focus by simply pressing the star to start music or holding it to switch focus, but sometimes it won't switch over.
1. Most of my phone calls cause AA to lose video focus and go to the Mazda call screen instead.
2. Switching from radio to Spotify on AA is very hit or miss. Sometimes I am able to switch audio focus by simply pressing the star to start music or holding it to switch focus, but sometimes it won't switch over.
I´m using 1.12, for case # 1 I long press home button to return AA focus.
For case # 2, long press and release * button.
My thoughts is that 1.12 is more stable with the audio, with 1.11 listening radio and waze somethings audio didn´t return to radio audio.
My only issue I found on 1.12 are the missing directions in the HUD, something thats was working 99% of the time on 1.11
Hi Mr. Tristan-cx5
According to link you shared "For .352 see the ID7v2 serial access", did you try it?
I read but I don't understand what is the “update.up” file which mentioned in the post.
Can you help to explain it more?
Thank you fo your time.
According to link you shared "For .352 see the ID7v2 serial access", did you try it?
I read but I don't understand what is the “update.up” file which mentioned in the post.
Can you help to explain it more?
Thank you fo your time.
Joined
·
2,453 Posts
No, I did not try it, as .352 so far is only available for NA region (north america), but not ADR (asia) and not for EU (europe). And as I live in the EU region, I do not want to install NA version. I just assume that the serial access of .352 works the same way, as it did with .335 (which I successfully tried/did).
Up to/including FW 70.00.100 there were 2 files you had to update for a FW update. From then onwards (.335 and .352) there is only one file you have to put to the usb stick to update the FW, which is a file called "version_and_region_number_update.up" this files is mentioned with "update.up" file. You can find the latest FW files in their region folders here. But remember to stick to the word to the update manual (PDF), as otherwise you could brick your CMU. And Mazda did not intend to let customers update their CMU, but only the dealers - thus its all on your own risk. If you have doubts, do not do it yourself.
Up to/including FW 70.00.100 there were 2 files you had to update for a FW update. From then onwards (.335 and .352) there is only one file you have to put to the usb stick to update the FW, which is a file called "version_and_region_number_update.up" this files is mentioned with "update.up" file. You can find the latest FW files in their region folders here. But remember to stick to the word to the update manual (PDF), as otherwise you could brick your CMU. And Mazda did not intend to let customers update their CMU, but only the dealers - thus its all on your own risk. If you have doubts, do not do it yourself.
Hi Tristan-cx5. Thank you so much for explanation and I fully understand your reply.
I did upgrade FW several times before (not for v70.xxx).
Sorry, I come up with another question.
==> The last sentence of the post "If it does not work, keep the serial console open and try to login with cmu/jci and run sh /mnt/data_persist/dev/bin/autorun." How to run sh? I do not know about it.
Again, thank you for your time.
I did upgrade FW several times before (not for v70.xxx).
Sorry, I come up with another question.
==> The last sentence of the post "If it does not work, keep the serial console open and try to login with cmu/jci and run sh /mnt/data_persist/dev/bin/autorun." How to run sh? I do not know about it.
Again, thank you for your time.
Joined
·
2,453 Posts
To enter the sh command lines you could use the software Putty. I assume more details are mentioned at www.mazdatweaks.com/serial at the manual for the (old) serial access, which only works below 70.00.335. But this website is a good knowledge base for doing the ID7v2 mentioned at www.mazdatweaks.com/id7
Joined
·
2,453 Posts
Correct, this seems to be a picture from Putty showing a successfull serial access, due to the blue and green lines.
About a year ago, I translated the instructions to Hebrew, you can read them here.
I noticed the Windows download has an expired certificate from Startcom, which has not been trusted by most browsers for some time.
I'm reluctant to go ahead with the install because of this - is anyone aware of plans for a new cert to be applied, or if the packaged is hosted on some other mirrors somewhere else?
I'm reluctant to go ahead with the install because of this - is anyone aware of plans for a new cert to be applied, or if the packaged is hosted on some other mirrors somewhere else?
Joined
·
316 Posts
Yes.
I'm on Windows 10 Pro, v 1909, build 18363.592 and downloaded via Chrome, v 79.0.3945.130, though I don't think those specs are the issue - I also tried on another Win10 PC with different specs without success.
Same issue on both the windows downloads (dl.mazdatweaks.win and dl32.mazdatweaks.win).
My installation of AA seems to be out of whack. My 2016 Miata has
MZD version 59.00.441 NA with ID7 v2 loaded, and the latest Tweak.
AA wireless has an awkward start up routine: I need to turn on phone's hotspot whenever I get in car, then navigate to MZD Settings/Devices/WiFi and select checkbox; about 30 sec later, check box unchecks itself, and I have to check it again. Then about 10 sec later, AA starts up.
The AA display intermittently cuts back to MZD screen, then returns to previous AA screen, such as Waze. Waze then pops up with no active route, then in a couple of seconds, the Waze route come back on the display.
I have observed the wifi connection status on MZD and I don't see it disconnect after the initial startup weirdness. Is there something I can do to make this more stable (other than a wired connection)?
MZD version 59.00.441 NA with ID7 v2 loaded, and the latest Tweak.
AA wireless has an awkward start up routine: I need to turn on phone's hotspot whenever I get in car, then navigate to MZD Settings/Devices/WiFi and select checkbox; about 30 sec later, check box unchecks itself, and I have to check it again. Then about 10 sec later, AA starts up.
The AA display intermittently cuts back to MZD screen, then returns to previous AA screen, such as Waze. Waze then pops up with no active route, then in a couple of seconds, the Waze route come back on the display.
I have observed the wifi connection status on MZD and I don't see it disconnect after the initial startup weirdness. Is there something I can do to make this more stable (other than a wired connection)?
Joined
·
2,453 Posts
Ideas/just guesses:
- Use a cable connection (faster setup/more stable)
- Install ID7 from AIO, update to 59.00.545 NA and install WiFi tweak
- Install latest AA 1.12 - or some older version (AIO 2.8.4 includes AA 1.11 and at the github even older AIO/AA versions are available)
7961 - 7980 of 9380 Posts
Join the discussion
