Ok, waiting for the new app with additional logs to send a new debug report.
What is strange is that I upgraded the firmware successfully several times in the past with older versions of the app, on the same phone. So the regression comes from a recent change in one of the last version.
In the meantime, is there a way to revert to the factory firmware?
… same here - upgraded my MM firmware to 1.07 using the previous app version (before the cadence versions) without problems - though obviously had all with other issues as described further up in the thread …
Dears, we have created a new version of the app, built to crash.
This is the least tested of the releases we’ve made so far, because the idea is to make it have better error reports, so do try and crash it please.
Latest versions of the app require firmware 1.1.1, which allows for the 32 MIDI messages per button action, enables the “on release” actions, and enables the MIDI Maestro Bluetooth MIDI communication. We then ask you to please crash the app however possible, so we can work on it as fast as possible and get the goodies into general availability.
Thank you guys for being here in the closed testing program. <3
1 Like
Hi @iajrz i @iajr,
Updated the MM app to cadence-6 & just sent you the crash log via the app.
Cheers,
Wolf
Thanks a lot, will be looking into it!
So I just updated. I tried to then update the firmware. After clicking yes, it immediately closes/crashes the app, without giving me the chance to send a report.
Hopefully the mechanism is robust enough that it’ll still show up.
1 Like
Crash report sent.
Ok,
I now have an Android device that I can use. I am having a problem with the next part function.
I have set up the button as a toggle. I am assuming that when I push the button it sends the cc command with a value of 127 which does work. I have configured the secondary command with a value of 0. However, the transition does not exit, it keeps going.
What am I doing wrong?
@Ian1946
Try the commands on separate buttons initially, once you are happy they work as intended, then you can start using toggle switch options.
So try CC113 value 127 on button 1 and CC113 value 0 on button 2. The transition will continue until button 2 is pressed. On MM you could send both these commands on the same button without needing the toggle function
1 Like
I can get it to work with separate buttons, but not on the same button. I can put 2 commands on the button but is does not work. Is there a rule, i.e alphabetic order etc for the order in which the commands are executed. I just want it to play thr transition and then go back to the main beat with a single, the same as beat buddy mode.
Furthermore, I am sure I have updated the firmware as it went through a lengthy upload progress but when i hit the update firmware button it says there is an update ready to download.
Hi, guys; there’s a new version with fewer crashes. Someone had an issue where they opened the app and it crashed immediately – it’s a bug in one of the features we added, we worked around some new facilities in the official Android software development kit which had bad compatibility with Android below 7.0 (and they shouldn’t – it’s a bug on their end).
The firmware update issue may be fixed. Our ability to predict is limited since we can’t reproduce the issue, but we’re doing our best to preempt any possible sources of crashes.
Again, thank you one and all for your help!
Hi, I’m afraid it still crashes on firmware update. On both Pixel and Tab. Have you tried disabling strict mode?
We haven’t enabled it to begin with. Will look at crash reports and see what else we can do.
Hi @iajrz,
I’m afraid - MM app still consistently crashing on firmware update - tried several times & always crashing as soon as I hit the firmware update button … sent a crash log just now.
MM app version: cadence-7
Phone: Samsung S6
OP: Android v7.0
Sorry guys, it’s still crashing for me in the same place.
cadence-7
SAMSUNG SM-G955U
Android Version 9
Still the same crash for me as well (report sent). Strange that you can’t reproduce on your end. Maybe it’s dependent from the current state of the MM device (like a half updated firmware). Currently my MM is not functional (EEPROM INVALID on top 3 screens).
While we wait for a resolution, is there a way to reset or install the firmware back (even an old one), e.g. use an older version of the app that was updating firmware seamlessly?
Or is there an alternative way to install the firmware without using the app (e.g. android emulator running on a PC or else)?
Hi @iajrz, just installed the latest MM app version (cadence-8) and I’m afraid it is still consistently crashing when trying to update the firmware - this immediately when I press the update button.
I sent a crash log already.
cadence-8
Samsung S6
Android 7 0
Cadence 9 now works with firmware update, let’s go bug hunting!
Yes the app is no more crashing on firmware upgrade. Thanks!
Just worth to mention that it needed 3 attempts, as the progress bar was not showing up on the first 2 tries.
I will now do a toy custom mode for the Line 6 HX stomp. I wonder if someone has tried it yet, and if so what are the main commands to start with.
1 Like