[dadtheimpaler]

So upon further investigation and the help of @Scholli04 I have found that the app list issue isn't with the app list patch but lies in the json file that contains the names of the additional apps. If this file is not in proper json format then the apps will not be added so the solution if anyone is having this issue is to uninstall all the apps (speedometer, videoplayer, and AA) then try reinstalling them possibly one at a time. I don't know exactly what is causing this because the method that adds apps to the json file has never changed but I'm guessing it takes a certain combination of tweaks on the same install to do it then once that json file is improperly formatted the only way to fix it other than manually is to uninstall all the apps so you delete that file then reinstall them to recreate it. If you have done that and are still having issues let me know.
We also found that I was right about the caching thing I'm pretty sure effecting FW v59.00.400-500 the apps sometimes won't appear right away then randomly appear later. The good news with that is after a few clean shutdowns the new list will be cached and the apps will show up in the list all the time..

Based on this, I put the AIO 'fullrestore' on a USB, then installed AA 0.99 and "No More Disclaimer". This returned Android Auto to the Applications menu, although launching it (with my phone connected or disconnected) resulted in the splash screen and then a black screen.
I then attempted to upgrade AA to 1.02 and added a few other tweaks (no other applications - I haven't added videoplayer or speedometer). On the initial reboot, AA was missing. I rebooted again, and AA was there. AA doesn't launch when I connect my phone, and if I try to launch it from the menu, I get an error at the bottom of the splash screen about not being able to connect to the head unit. Will 'fullrestore' again and go straight to AA 1.02.
Running version 441NA, btw.

 

[restrepogoez]

https://drive.google.com/open?id=0B6lM3ZL0_MwIQ01EOVFVN3RONjg

The connection as always
115200 8n1 by putty from windows

version cmu150_EU_59.00.502A

USB TO TTL chip

 

[MechaBouncer]

Based on this, I put the AIO 'fullrestore' on a USB, then installed AA 0.99 and "No More Disclaimer". This returned Android Auto to the Applications menu, although launching it (with my phone connected or disconnected) resulted in the splash screen and then a black screen.
I then attempted to upgrade AA to 1.02 and added a few other tweaks (no other applications - I haven't added videoplayer or speedometer). On the initial reboot, AA was missing. I rebooted again, and AA was there. AA doesn't launch when I connect my phone, and if I try to launch it from the menu, I get an error at the bottom of the splash screen about not being able to connect to the head unit. Will 'fullrestore' again and go straight to AA 1.02.
Running version 441NA, btw.

AA 0.99 added the option to the Apps menu while AA 1.02 was supposed to auto-launch (so I'm not sure if it added the menu option). The fact that you got the blank screen sounds like it installed, but you may be missing settings on your phone to allow it to run.

I know that I'm going to regret asking, but do you have the "Developer options" menu enabled on your phone or "USB debugging" enabled? Do you have "Verify apps over USB" disabled? From our previous conversation, I'm suspecting that these are not set.

 

[dadtheimpaler]

AA 0.99 added the option to the Apps menu while AA 1.02 was supposed to auto-launch (so I'm not sure if it added the menu option). The fact that you got the blank screen sounds like it installed, but you may be missing settings on your phone to allow it to run.

I know that I'm going to regret asking, but do you have the "Developer options" menu enabled on your phone or "USB debugging" enabled? Do you have "Verify apps over USB" disabled? From our previous conversation, I'm suspecting that these are not set.

For my initial AIO 2.5.6 install, I didn't have any of those settings enabled/disabled on my phone, and AA installed successfully and auto-launched. I got rid of it because of the Bluetooth bug, however.
I've just tried a fresh restore/install of AA 1.02 via AIO 2.6.1 with my phone set as recommended, with AA running on my phone, and the head unit still can't launch in AA.

 

[arathol]

Just read on Miata.net that the download buttons on the AIO page for 2.6 are not working. Tried it and...they don't do anything. ????

 

[Diginix]

Go directly to the target URL and the download will appear:
Win http://dl.mazdatweaks.win
MAC http://mac.mazdatweaks.win
Linux http://deb.mazdatweaks.win

 

[Achilles97]

Smaller Font?

Pardon my ignorance. Is there a tweak to apply smaller font to the display, specifically the song name, radio station, etc ? I've searched and I find results that seem to imply this possibility but I cannot find that particular feature in my 2.6 installer. I appreciate the assistance.

 

[Diginix]

Never heard of such tweak. It is definitely possible to change every font size, but you have to find out what css selectors / classes and so on. Means work to build such tweak. As long as you are the only one that really complains it, no dev will create it. Except you will do it.

 

[MechaBouncer]

For my initial AIO 2.5.6 install, I didn't have any of those settings enabled/disabled on my phone, and AA installed successfully and auto-launched. I got rid of it because of the Bluetooth bug, however.
I've just tried a fresh restore/install of AA 1.02 via AIO 2.6.1 with my phone set as recommended, with AA running on my phone, and the head unit still can't launch in AA.

In Android Auto under Settings -> Connected cars does "Mazda Connect" show up and do you have "Add new cars to Android Auto" enabled? And when you connected your USB cable to the car and got the black screen the first time, did anything show up on the phone asking you to authorize the car?

Also under the phone's settings under Developer options you may want to try clicking the "Revoke USB debugging authorizations" in case it was somehow blocked for USB debugging. There's a separate message that should come up for that with a checkbox to always allow the device to connect.

 

[id7]

Serial access on 59.502

Id7, This method also does not work with 502...
I checked on version 443, I see the system log, you are prompted for a password and given a few seconds to enter it, you can not manage 443 versions in this way ... version 502 does not display anything at all...

That connection to 502, has done or in teroria should work.

By serial connection logs all the log or an active debug preventing user input and password, we actually blocked access from all sides.

Can you elaborate on how you tested this? I'm not asking about how you connected your USB TTL serial cable. I assume you have a working cable and connected it correctly. I want to understand what you have done.

You say you checked on version 443 and that it doesn't work. Then you say version 502 doesn't as well. I see in previous posts you stated you updated to version 502. Everyone has reported you cannot downgrade so do you have access to multiple cars or an extra CMU lying around? Did you test it before you updated to version 502? Have you successfully accessed the serial console before in previous versions or have you only tried with versions 443 and 502?

Also, how did you create your SPI flash dumps? I see you posted them in a previous post. Were you using functionality in the dataRetrieval files? Or were you using something like a bus pirate and reading the flash chip itself manually?



How did you enable the fail-safe mode? Manually with a bus pirate and writing the flash chip? Some other way? What happens when you enable the fail-safe? Does it prompt for a USB drive to reinstall? Or does it just auto-reinstall as if it was using locally saved files? That's how I'm reading what you said.

Let me know if you have any questions; I'm hoping not too much gets lost in translation. Thanks.

I test it today and works
You can see logs on serial
press enter
you see CMU Login:
enter username and press ENTER
after that enter password and ENTER
meantime you see logs BUT what you type is work
I enter "reboot"+ENTER and works

bellow you can see the serial console (with bold that is interesting)
at the end of logs you can see the boot-up process of cmu and the version of it (with bold at line 00:00:07.838 )

00:08:28.264 BDS[1236] Info (bds_bluegoservicemanager.c:1099 BDS_Xlator_ServiceManagerCommand) [BDS]BLUEGO_ServiceConnect Call
00:08:28.264 BLUEGO[1236] Info (bluego.c:980 BLUEGO_ServiceConnectEx) id.service=BLUEGO_SERVICE_MEDIA_AUDIO
00:08:28.264 BLUEGO[1236] Info (bluego.c:984 BLUEGO_ServiceConnectEx) pRemoteDevice->addr[60:af:6d:81:ff:8e]
00:08:28.267 BDS[1236] Info (bds_servicemanager.c:1484 serviceStateDisconnected) Audio Sink: Disconnected->Connecting

[B]cmu login: [/B]00:08:30.640 VWM[2020] Info (vwm_hmi_interface.c:3403 VWM_HMI_SendMaintenanceLatestData) sched mnt remaining Dist = 9761
00:08:30.643 MMUI_SCHEDMAINT[1002] Info (uia_schedmaint_dbus.c:421 schedMaintDistanceCB) schedMaintDistanceCB 9761 1
00:08:30.669 VWM[2020] Info (vwm_vbs_interface.c:5499 VWM_VBS_SendShortestRemTime) Value of l_ShortestShedTime = 0 successfully sent
00:08:30.669 GUI_SCHEDMAINT[568] Info (schedmaintApp.js:1009 ) In _schedMaintDueMSgHandler and this._schedmaintDueData 4 and status is false
[B]jci
Password: [/B]00:08:32.302 TDS[561] Info (tds_tmc.c:64 TDS_TMC_HandleTMCMessage) TotalLength = 70, tcmBlockCount=8
00:08:32.302 TDS[561] Info (tds_tmc.c:76 TDS_TMC_HandleTMCMessage) TMC length validated
00:08:32.661 GUICORE[1002] Info (guiifm_net.c:335 GUIIFM_SendDataToGUI) Sending 122 bytes to GUI: "{"msgType":"msg","uiaId":"syssettings","msgId":"SendCurrentTimeEpoch","params":{"payload":{"u32TimestampSec":1498240140}}}"

00:08:33.021 login[12345] Info (: ) root login on 'console'
[B]/tmp/root #[/B] 00:08:33.387 BDS[1236] Info (bds_bluego.c:268 bluegoEventHandler) [BDS]Evt:8,Serv:4,Fn:10
00:08:33.387 BDS[1236] Info (bds_bluegoservicemanager.c:437 BDS_BluegoServiceManager_Event) BDS status: Not Found (4)
00:08:33.396 BCA[1736] Info (bca_state_machine.c:4268 bca_AllProfileAutoConnectState_EventHandler) stopping inconn timer
00:08:33.397 BCA[1736] Info (bca_timer.c:84 BCA_startIncomingConnTimer) Incoming Connection Wait timer started with timeout 5000 milli sec
[B]rebo[/B]00:08:35.892 TDS[561] Info (tds_tmc.c:64 TDS_TMC_HandleTMCMessage) TotalLength = 70, tcmBlockCount=8
00:08:35.892 TDS[561] Info (tds_tmc.c:76 TDS_TMC_HandleTMCMessage) TMC length validated
00:08:35.892 TDS[561] Info (tds_tmc.c:110 TDS_TMC_HandleTMCMessage) Block 1 of 8 :::: tmcBlock1_info=[E25D] (57949), tmcBlock2_info=[8008] (32776), tmcBlock3_info=[0847] (2119), tmcBlock4_info=[94E9] (38121)
00:08:35.894 TDS[561] Info (tds_tmc.c:110 TDS_TMC_HandleTMCMessage) Block 7 of 8 :::: tmcBlock1_info=[E25D] (57949), tmcBlock2_info=[8008] (32776), tmcBlock3_info=[4848] (18504), tmcBlock4_info=[9729] (38697)
00:08:35.894 TDS[561] Info (tds_tmc.c:110 TDS_TMC_HandleTMCMessage) Block 8 of 8 :::: tmcBlock1_info=[E25D] (57949), tmcBlock2_info=[8008] (32776), tmcBlock3_info=[4848] (18504), tmcBlock4_info=[9729] (38697)
[B]ot[/B]
shutdown request for reboot, from pid:12870
/tmp/root # cat: can't open '/proc/12870/cmdline': No such file or directory
sending SIGKILL
unmounting file systems
unable to unmount /dev/mqueue: Device or resource busy
Unloading ffxblk driver now!
UnlïIBC embedded bootloader 1.68.17
(c) 2012 XS Embedded GmbH
Uncompressing Linux... done, booting the kernel.
00:00:01.247 LVDS[61] (Defaulting) Visteon Display.
00:00:01.247 LVDS[61] HdcpModeStatus = 0.
00:00:01.288 LVDS[61] HdcpModeStatus = 0.
00:00:01.308 LVDS[61] (Defaulting) Visteon Display.
00:00:01.309 LVDS[61] NormalModeResp = 1.
00:00:01.320 LVDS[61] Tuning values: 0, 0, 1, 1.
00:00:01.436 LVDS[61] HdcpModeStatus = 1.
00:00:01.465 LVDS[61] BrightNessLevel = 150.
00:00:02.423 LVDS[61] BrightNessLevel = 150.

FGSN: *****************
cmu login: j00:00:07.779 kernel[] Warn (: ) [    1.121087] m25p80 spi0.0: found mx25l6405d, expected s25fl064p
00:00:07.779 kernel[] Warn (: ) [    1.514405] flashfx: module license 'Copyright (c) 1993-2012 Datalight, Inc.  All Rights Reserved Worldwide.' taints kernel.
00:00:07.779 kernel[] Warn (: ) [    1.514427] Disabling lock debugging due to kernel taint
00:00:07.779 kernel[] Error (: ) [    1.839597] usb 2-1: Device is not authorized for usage
00:00:07.779 kernel[] Warn (: ) [    2.826334] mmc0: card claims to support voltages below the defined range. These will be ignored.
00:00:07.779 kernel[] Warn (: ) [    2.859512] mmc0: queuing unknown CIS tuple 0x91 (3 bytes)
00:00:07.779 kernel[] Error (: ) [    6.134486] usb 2-1.1: Device is not authorized for usage
00:00:07.779 Std[] Info (: ) TDE_TRIG_NORMAL_BOOT
00:00:07.779 Std[] Info (: ) [CORE_MAZ] NVRAM_Block_getValue return the currentCameraType = 2
00:00:07.779 Std[] Info (: ) NNG configuration file found, no changed required.
00:00:07.779 Std[] Info (: ) Usage /jci/scripts/set_nng_debug.sh off|on [create|load [path|file]]
00:00:07.779 Std[] Info (: )    Options:
00:00:07.779 Std[] Info (: )            off                     Turn NNG DEBUGGING Off
00:00:07.779 Std[] Info (: )            on
00:00:07.779 Std[] Info (: )                    no arg          Turn NNG DEBUGGING On and output to /data/save/
00:00:07.779 Std[] Info (: )                    create <path>   Turn NNG DEBUGGING On and output to <path>
00:00:07.779 Std[] Info (: )                    load <ini>      Turn NNG DEBUGGING On load ini file
00:00:07.779 SM[259] Info (sm.cpp:4280 SM_SetProcessPriority) Service with pid (259) launched with policy SCHED_OTHER nice value -5
00:00:07.779 SM[259] Info (sm.cpp:1479 main) SM initialized!
00:00:07.779 SM[259] Info (sm.cpp:1493 main) SM Starting!
00:00:07.779 SM[259] Info (Watchdog.hpp:99 onFilter)   Original WatchDog thread priority[0] and policy[0]
00:00:07.779 SM[259] Info (Watchdog.hpp:112 onFilter) Set WatchDog thread priority[60] from sm.conf
00:00:07.779 SM[259] Info (Watchdog.hpp:117 onFilter) Set policy = SCHED_RR 
00:00:07.779 SM[259] Info (sm.cpp:1507 main) SM monitoring...
00:00:07.688 syslog-ng[263] Note (: ) syslog-ng starting up; version='3.3.5'
00:00:07.779 syslog-ng[263] Warn (: ) WARNING: you are using the pipe driver, underlying file is not a FIFO, it should be used by file(); filename='/dev/console'
00:00:07.838 Std[] Info (: )    Examples:
00:00:07.838 Std[] Info (: )            set_nng_debug.sh off
00:00:07.838 Std[] Info (: )            set_nng_debug.sh on
00:00:07.838 Std[] Info (: )            set_nng_debug.sh on create /tmp/mnt/sda1
00:00:07.838 Std[] Info (: )            set_nng_debug.sh on load /tmp/mnt/sda1/sys.ini
00:00:07.838 Std[] Info (: ) =============== MAZ_CMU-150_[B]59.00.502A[/B]  Flavor cmu150_EU ===============
00:00:07.924 SM[259] Info (sm.cpp:976 sm_ActionsForStoppedService) Svc audio_config stopped! [pid:280][idx:36][exec:/jci/am/audioconfigupdate.sh]
00:00:07.924 SM[259] Warn (sm.cpp:1059 sm_ActionsForStoppedService) Unlinking file ptr->ready_flag /var/run/audio_config
00:00:07.924 SM[259] Info (sm.cpp:976 sm_ActionsForStoppedService) Svc dsp_config stopped! [pid:283][idx:35][exec:/jci/scripts/dsp-config.sh]

 

[enslen]

I test it today and works
You can see logs on serial
press enter
you see CMU Login:
enter username and press ENTER
after that enter password and ENTER
meantime you see logs BUT what you type is work
I enter "reboot"+ENTER and works

bellow you can see the serial console (with bold that is interesting)
at the end of logs you can see the boot-up process of cmu and the version of it (with bold at line 00:00:07.838 )

Thank you for testing this. I'm glad this still works. Having this confirmed after the previous reports, I will definitely be updating soon. I will post a full write up with pictures, videos, scripts and links (to relevant threads, posts, sites, etc.) on how to do the update and still retain access to the CMU; assuming someone doesn't beat me to it. I probably won't be able to get to it for at least 2 weeks; I'm just really busy at home right now.

Thanks again.

 

[dadtheimpaler]

In Android Auto under Settings -> Connected cars does "Mazda Connect" show up and do you have "Add new cars to Android Auto" enabled? And when you connected your USB cable to the car and got the black screen the first time, did anything show up on the phone asking you to authorize the car?

Also under the phone's settings under Developer options you may want to try clicking the "Revoke USB debugging authorizations" in case it was somehow blocked for USB debugging. There's a separate message that should come up for that with a checkbox to always allow the device to connect.

Yes, "Add new cars" is enabled, and I have "Mazda Connect" listed under "Accepted cars". Of course, that could be there from the early days when I got it to work but had the Bluetooth bug.
Perhaps I should wipe it out of there and let it get re-discovered.

When I got the black screen (that was with AA 0.99) there was no acknowledgement of any kind on my phone that anything had happened.

Update: I ran into trouble re-pairing my phone via Bluetooth (phone and car seem to get out of sync with pin code) but that could be because of the Android Beta OS I was running. Tried it with another, more vanilla phone. Ran into the same kind of AA issues, though. Paired with Bluetooth no problem, installed AA 0.99 and "No More Disclaimer" with AIO 2.6.10, but AA on the phone never seems to acknowledge a vehicle, and AA on the car just goes to a black screen after the splash screen.

I also found, after my most recent install, that AA wouldn't show up in the applications menu until after a few reboots. Went back to the car an hour later, and it's missing again. I'm guessing I could get it to show up again if I rebooted a few times.

I almost wish I'd just left it alone after I got it working with AIO 2.5.6 and AA 1.02, and just lived with the Bluetooth issue.

 

[vondiesel]

Yes this does look legit thanks but the real issue lies in the fact that they removed the part of that process that we use to trigger and run the tweaks installer. There is also quite a bit different with the dataRetrieval file in the system that calls on these files but I did notice that there is now a cli (command line interface) written into the new dataRetrieval file leading me to believe there is still some way execute command line actions.

OK, so the data retrieval can work again, but the line added to the config file (CMD_LINE=sh /mnt/sd*/tweaks.sh) is no longer functional due to a change within the firmware such that the command no longer runs. Gotcha.

 

[surfrider]

I'm having trouble getting video player to install. I have the latest 2.6.1 AIO and .441NA firmware. The installation looks like it completes okay, but Video Player isn't showing up on the apps menu. I've tried several times, but no luck.

 

[surfrider]

You can also get around it by right-clicking and open link in new tab.

 

[surfrider]

Just read on Miata.net that the download buttons on the AIO page for 2.6 are not working. Tried it and...they don't do anything. ????

You can get around it by right-clicking the button and then selecting 'open in new tab'.

 

[arathol]

You can get around it by right-clicking the button and then selecting 'open in new tab'.

I understand all this. The problem is that the link that goes to that page is being posted now on all the other Mazda forums (and elsewhere), and the page doesn't work like it is supposed to. The download buttons are there (I would presume) to actually download the software with one click. It doesn't work like it used to since the upgrade to 2.6. "Getting around it" isn't the point. The not working part is.

 

[id7]

OK, so the data retrieval can work again, but the line added to the config file (CMD_LINE=sh /mnt/sd*/tweaks.sh) is no longer functional due to a change within the firmware such that the command no longer runs. Gotcha.

for 59.502 I solve this problem with a trigger setup via udev

if you create a file in /etc/udev/rules.d/ with the following content

ACTION=="add",KERNEL=="sd?", RUN+="/bin/sh PathToScriptToBeExecuted %k"

This script will be executed when a usb storage was inserted to CMU
In execute time of this script the storage device is not mounted !!!

from that script you need to run in background another script and return for CMU finish mounting of new storage.
that background executed script need to wait 2sec for usb storage to be mounted.
after that, can search for dataRetrieval_config.txt and search in it for CMD_LINE option

with this solution we can use all old usb solution

One problem I can't resolve:
if we execute tweaks.sh with this solution jci-dialog not work.
I don't have time to analyze. Probably missing some environment variable or something like that

You can find this script and others in my original post http://mazda3revolution.com/forums/...zda-3-skyactiv-audio-electronics/122458-aio-all-one-tweaks-399.html#post2072794

BEFORE upgrade to 59.502 you need to install this scripts

 

[vitas]

for 59.502 I solve this problem with a trigger setup via udev

if you create a file in /etc/udev/rules.d/ with the following content

ACTION=="add",KERNEL=="sd?", RUN+="/bin/sh PathToScriptToBeExecuted %k"

This script will be executed when a usb storage was inserted to CMU
In execute time of this script the storage device is not mounted !!!

from that script you need to run in background another script and return for CMU finish mounting of new storage.
that background executed script need to wait 2sec for usb storage to be mounted.
after that, can search for dataRetrieval_config.txt and search in it for CMD_LINE option

with this solution we can use all old usb solution

One problem I can't resolve:
if we execute tweaks.sh with this solution jci-dialog not work.
I don't have time to analyze. Probably missing some environment variable or something like that

You can find this script and others in my original post http://mazda3revolution.com/forums/...zda-3-skyactiv-audio-electronics/122458-aio-all-one-tweaks-399.html#post2072794

BEFORE upgrade to 59.502 you need to install this scripts

Thank you for help, i read you orinal post, its hard for ordinary people) but i very want to return tweaks on my car) and I would like to ask you create litle instruction, such as this in attach, I think everyone will be grateful to you, especially in Russia)))

 

[danobe]

Hi everyone,
I read that di latest version of AIO is the 2.6.2, that's right?
If yes, please, can someone give me the link? In AIO official page still appear the 2.6.0 version.

And with this latest version is now possible to interact with the firmware 59.00.502, it is true?

Thank you.