Release 1.12.0 (final testing)

Beta Testing Beta Releases
#1

Hello all. As we get all details of the new company sorted out, including the plugin shop, we are preparing the v1.12 final release as well.

This is a special pre-release in order to verify the shop works as intended.
We will release it as official/public next week after a small period of testing.
Users on the testers group (also known as “group 1”) get this update as usual.

For v1.12 vs v1.11 and before, please refer to the RC1 topic to read the changes made in 1.12:

A more in-depth changelog will be posted next week as well.

Here are the manual download links:
Duo: https://download.mod.audio/releases/testing/modduo-v1.12.0.2951.tar
Duo X: https://download.mod.audio/releases/testing/modduox-v1.12.0.2950.tar
Dwarf: https://download.mod.audio/releases/testing/moddwarf-v1.12.0.2949.tar

The upgrade procedure is explained at the top of our releases page, here:
http://wiki.moddevices.com/wiki/Releases

We hope you’re enjoying your MOD unit.
Let us know if you find any issues.

13 Likes
MOD Reboot: We made it!
#2
#3

Temporary limitations for purchasing plugins:

  • Discount codes are not applicable in the new checkout yet. But they remain valid and will work until the official release of 1.12
  • Some plugins are showing up as “TRIAL ONLY” (as long as not purchased before) because they are deactivated on purpose. We lack a new contractual agreement for those and are waiting for some partners to get back to us. Will be mostly sorted out until release.
  • PayPal is not available anymore but there are plenty of other payment options. We even would like to avoid it entirely, if acceptable for customers.

We did a lot of test purchases, but to finally validate, it’s now time for real deals. For those testing the new release and up for buying a plugin: Please let us know anything cumbersome in the overall experience. Be assured we keep an eye on the transactions. Goes without saying, that anything which is not working out will be fixed or refunded.

Hope you enjoy shopping plugins again!

PS: There are quite some additions for valuable commercial plugins to be released soon.

13 Likes
#4

I got up to the shop, so all links and forwards work.

Have almost bought all plugins already, but would like to wait with more until I get my vouchers …

ps; I’d hope at some point you can integrate with Stripe or other payment provider? quite inconvenient to have to go through either google pay or (what I can only assume) bank-transfer. Although I do get the hassle of having to deal with credit-card payments (and especially now as that would mean quite delayed cash-flow).

3 Likes
#5

Paypal has one of the most criminal spreads in the currency exchange market, almost as bad as those kiosks at airports. Not to mention their fees. I closed my account and fully support Mod to stop accepting them altogether.

Purchased a couple of long desired plugins with Google Pay and all went fine. Will test the release further.

7 Likes
#6

From another perspective, without PayPal I would not purchase anything from the store.

#7

These guys are shady as hell. Recently they had frozen 1.3M dollars of customer payments towards Flipper Inc without any reason. (another startup originated from the kickstart that sells unique device, quite popular and succesfull one) and therefore put the Flipper Inc into serious risk, as they needed that money for production. I would not wish MOD to have the same problems.

4 Likes
#8

I’ve bought Gaff and Shiro mk2 with no problems using google pay. Keys downloaded fine.
Nice.

8 Likes
#9

Yop,

I’ve tested successfully to buying a Phantom Zone plugin ! It works smoothly.

but the other things I’ve reported are still there :

This problem is in 1.11 too

Thoses 2 still here since 1.12 :

  • no bluetooth with 1.12. the current 1.11 makes my rtl8761 dongle work perfectly (as “bluetooth perfectly”, not “perfectly perfectly”
  • impossible to make the wpa-supplicant-wlan0 active with my mt7610u wifi dongle

I’ve put both drivers in /data/firmware
image

1 Like
#10

journalctl -xe shows me

Jan 01 00:00:01 moddwarf kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
Jan 01 00:00:01 moddwarf kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
Jan 01 00:00:01 moddwarf kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
Jan 01 00:00:01 moddwarf kernel: bluetooth hci0: Direct firmware load for rtl_bt/rtl8761bu_fw.bin failed with error -2
Jan 01 00:00:01 moddwarf kernel: Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8761bu_fw.bin not found

there is no folder rtl_bt and I can’t create it at the root. I’ve only put the
rtl8761bu_fw.bin file in /data/firmware.

1 Like
#11

you need to create /data/firmware/rtl_bt and put the bin files there.

2 Likes
#12

Same message with the /data/firmware/rtl_bt/rtl8761bu_fw.bin (after a reboot)

Why does it works without this straight out of the box with 1.11 and not with 1.12 ?

#13

Same here. Lost bluetooth after installing 1.12

1 Like
#15

Ok. Now it magiclally fixed itself. I just re-plugged the dongle (10th time :slight_smile:) without rebooting

1 Like
#16

Was able to reproduce the issue, fixed in make sure to not add the same virtual addressing more than once · moddevices/mod-ui@77a09ca · GitHub
Somehow you got 2 BPM related addressings for the same parameter, which is not allowed.
Fixed by refusing to load the 2nd one that created inconsistent state.
Will be part of the next (final final) build.

Regarding the bluetooth issue, I am quite sure that with the firmware in place the error message will be different.
We updated the kernel used in the dwarf in 1.12, seems the new one requires a firmware file to work.

4 Likes
#17

This Flipper story is really a nightmare! We don’t want to get there.

While I’m well aware, that PayPal is liked by many end customers, it seems hard to deal with for any other stakeholder. Even the insolvency admin said their orders based on court rule are respected straight by any bank but PayPal. We could not set up a new account for MOD Audio properly yet. While still trying that, our new accounting and tax advisor recommended to avoid it, as they have too many bookeeping issues related to Paypal with other clients. So it’s not just the MOD legacy making it difficult. We stay open to add PayPal to our shop if things change. Hope you understand we are picking more promising challenges meanwhile.

8 Likes
#18

this means the feature changes from officially supported and straightforward to hacky and experimental (unless you expect normal users to use ssh :wink: ) , worth mentioning in release notes and manual IMO.

I added the firmware file and played with BT a bit more. It only works after replugging the dongle, never from the start. Here’s the log:

Jan 01 00:02:52 moddwarf systemd[1]: Started Boot Operations.
Jan 01 00:02:52 moddwarf systemd[1]: Started bluetooth network.
Jan 01 00:02:52 moddwarf systemd[1]: Starting bluetooth network...
Jan 01 00:02:54 moddwarf cpu-freq-manager[246]: cpu-freq-manager run_loop heating up, temp:75384 freq:1200000
Jan 01 00:02:54 moddwarf net.bnep[3303]: Traceback (most recent call last):
Jan 01 00:02:54 moddwarf net.bnep[3303]: File "/usr/sbin/bt-pan", line 232, in <module>
Jan 01 00:02:54 moddwarf net.bnep[3303]: dev_local = find_adapter()
Jan 01 00:02:54 moddwarf net.bnep[3303]: File "/usr/sbin/bt-pan", line 65, in find_adapter
Jan 01 00:02:54 moddwarf net.bnep[3303]: return find_adapter_in_objects(get_manager().GetManagedObjects(), pattern)
Jan 01 00:02:54 moddwarf net.bnep[3303]: File "/usr/sbin/bt-pan", line 62, in find_adapter_in_objects
Jan 01 00:02:54 moddwarf net.bnep[3303]: raise BTError('Bluetooth adapter not found')
Jan 01 00:02:54 moddwarf net.bnep[3303]: __main__.BTError: Bluetooth adapter not found
Jan 01 00:02:55 moddwarf systemd[1]: bnep.service: main process exited, code=exited, status=1/FAILURE
Jan 01 00:02:55 moddwarf systemd[1]: Unit bnep.service entered failed state.
Jan 01 00:02:55 moddwarf systemd[1]: bnep.service failed.
Jan 01 00:02:55 moddwarf systemd[1]: bnep.service holdoff time over, scheduling restart.

The above repeats endlessly till adpater is replugged, and then:

Jan 01 00:04:53 moddwarf kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
Jan 01 00:04:53 moddwarf kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
Jan 01 00:04:53 moddwarf kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
Jan 01 00:04:53 moddwarf kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
Jan 01 00:04:53 moddwarf kernel: bluetooth hci0: Direct firmware load for rtl_bt/rtl8761bu_config.bin failed with error -2
Jan 01 00:04:53 moddwarf kernel: Bluetooth: hci0: RTL: cfg_sz -2, total sz 27808
Jan 01 00:04:53 moddwarf systemd[1]: Starting Data Partition Operations...
Jan 01 00:04:53 moddwarf systemd[1]: Starting Bluetooth service...
Jan 01 00:04:53 moddwarf bluetoothd[4877]: Bluetooth daemon 5.37
Jan 01 00:04:53 moddwarf bluetoothd[4877]: Starting SDP server
Jan 01 00:04:53 moddwarf systemd[1]: Started Bluetooth service.
Jan 01 00:04:53 moddwarf bluetoothd[4877]: Failed to open RFKILL control device
Jan 01 00:04:53 moddwarf bluetoothd[4877]: Bluetooth management interface 1.21 initialized
Jan 01 00:04:53 moddwarf kernel: Bluetooth: hci0: RTL: fw version 0x09a98a6b
Jan 01 00:04:53 moddwarf bluetoothd[4877]: Failed to obtain handles for "Service Changed" characteristic
Jan 01 00:04:54 moddwarf systemd[1]: Started Data Partition Operations.
Jan 01 00:04:54 moddwarf systemd[1]: Starting Boot Operations...
Jan 01 00:04:54 moddwarf cpu-freq-manager[246]: cpu-freq-manager run_loop heating up, temp:75384 freq:1200000
Jan 01 00:04:56 moddwarf boot-operations[4901]: Skipping restore of element with name 'LOOPBACK', as needed for MOD
Jan 01 00:04:56 moddwarf boot-operations[4901]: Skipping restore of element with name 'LOOPBACK', as needed for MOD
Jan 01 00:04:56 moddwarf boot-operations[4901]: ALSA: restored user settings
Jan 01 00:04:56 moddwarf systemd[1]: Started Boot Operations.
Jan 01 00:04:56 moddwarf systemd[1]: Started bluetooth network.
Jan 01 00:04:56 moddwarf systemd[1]: Starting bluetooth network...
Jan 01 00:04:56 moddwarf systemd[1]: Reached target Bluetooth.
Jan 01 00:04:56 moddwarf systemd[1]: Starting Bluetooth.

And then it works

1 Like
#19

oh… BT works again !
I quite not understand why since I haven’t change anything since I’ve move the rtl8761bu_fw.bin file in the /data/firmware/rtl_bt folder… maybe another reboot was necessary !?

Do you have a clue of what should I do for the mt7610u.bin file and make the wifi dongle work ?

2 Likes
#20

Actually it seems like I have got something strange with a firmware as well on my MDX. I’ve just powered on my MDX, but got no wifi connection. I’ve re-plugged wifi dongle and got connection raised in seconds after. dmesg output is in the end of the post.

Seems like first (on-boot) attempt failed with mt7601u 1-1.4:1.0: Direct firmware load for mt7601u.bin failed with error -2 during MDX startup. But after replugging the dongle it worked well. I’ve tried to replug the dongle for 10 more times, and seems to work fine every time.

After that I’ve removed the firmware file from the /data/firmware/mt7601u.bin, and got the same error message when reconnecting the dongle:

[  480.940288] usb 1-1.4: reset high-speed USB device number 13 using ehci-platform
[  481.028296] mt7601u 1-1.4:1.0: ASIC revision: 76010001 MAC revision: 76010500
[  481.029833] mt7601u 1-1.4:1.0: Direct firmware load for mt7601u.bin failed with error -2
[  481.030592] mt7601u: probe of 1-1.4:1.0 failed with error -2

It feels like a race condition of some sort is here. (reminds me of audiogadget issues, by the way) Error “-2” is the same for firmware being in place during startup as for firmware being absent at all. Therefore it looks like MDX is not able to find the firmware that is placed properly, and only during startup.

Is usb dongle processed earlier in some cases than partition is mounted? It explains the observations quite well, and could be related to audiogadget stuff as well.

dmesg for failed booting with usb dongle and successful replug after:

[    0.550256] systemd[1]: Started Remount Root and Kernel File Systems.
[    0.550483] systemd[1]: Started Create System Users.
[    0.551920] systemd[1]: Starting Create Static Device Nodes in /dev...
[    0.552738] systemd[1]: Started Journal Service.
[    0.608031] systemd-journald[135]: Received request to flush runtime journal from PID 1
[    0.766043] vendor storage:20160801 ret = 0
[    0.821289] usb 1-1.4: new high-speed USB device number 3 using ehci-platform
[    0.917762] usb 1-1.4: New USB device found, idVendor=148f, idProduct=7601
[    0.917775] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    0.917783] usb 1-1.4: Product: 802.11 n WLAN
[    0.917790] usb 1-1.4: Manufacturer: MediaTek
[    0.917796] usb 1-1.4: SerialNumber: 1.0
[    1.011296] usb 1-1.4: reset high-speed USB device number 3 using ehci-platform
[    1.100645] mt7601u 1-1.4:1.0: ASIC revision: 76010001 MAC revision: 76010500
[    1.102402] mt7601u 1-1.4:1.0: Direct firmware load for mt7601u.bin failed with error -2
[    1.103392] mt7601u: probe of 1-1.4:1.0 failed with error -2
[    1.103470] usbcore: registered new interface driver mt7601u
[    1.112245] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: nodelalloc,errors=remount-ro
[    1.665605] using random self ethernet address
[    1.665613] using random host ethernet address
[    1.666674] usb0: HOST MAC c6:d8:a5:3a:86:9b
[    1.666714] usb0: MAC e2:ec:a9:db:de:b6
[    1.666730] using random self ethernet address
[    1.666734] using random host ethernet address
[    1.666772] g_ether gadget: DuoX Ethernet, version: DuoX
[    1.666775] g_ether gadget: g_ether ready
[    2.760598] random: nonblocking pool is initialized
[   36.472746] usb 1-1.4: USB disconnect, device number 3
[   39.128277] usb 1-1.4: new high-speed USB device number 4 using ehci-platform
[   39.224764] usb 1-1.4: New USB device found, idVendor=148f, idProduct=7601
[   39.224772] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   39.224776] usb 1-1.4: Product: 802.11 n WLAN
[   39.224779] usb 1-1.4: Manufacturer: MediaTek
[   39.224782] usb 1-1.4: SerialNumber: 1.0
[   39.299277] usb 1-1.4: reset high-speed USB device number 4 using ehci-platform
[   39.387251] mt7601u 1-1.4:1.0: ASIC revision: 76010001 MAC revision: 76010500
[   39.389853] mt7601u 1-1.4:1.0: Firmware Version: 0.1.00 Build: 7640 Build time: 201302052146____
[   39.744003] mt7601u 1-1.4:1.0: EEPROM ver:0d fae:00
[   39.974716] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[   41.259091] wlan0: authenticate with e8:65:d4:4f:af:31
[   41.276014] wlan0: send auth to e8:65:d4:4f:af:31 (try 1/3)
[   41.277656] wlan0: authenticated
[   41.278276] wlan0: associate with e8:65:d4:4f:af:31 (try 1/3)
[   41.298657] wlan0: RX AssocResp from e8:65:d4:4f:af:31 (capab=0x411 status=0 aid=2)
[   41.331150] wlan0: associated

UPD:

just noticed, mount message comes after firmware loading failure, so looks like my assumption is correct, firmware is not loaded because partition with firmware is not mounted yet:


[    1.100645] mt7601u 1-1.4:1.0: ASIC revision: 76010001 MAC revision: 76010500
[    1.102402] mt7601u 1-1.4:1.0: Direct firmware load for mt7601u.bin failed with error -2
[    1.103392] mt7601u: probe of 1-1.4:1.0 failed with error -2
[    1.103470] usbcore: registered new interface driver mt7601u
[    1.112245] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: nodelalloc,errors=remount-ro
1 Like
#21

i have it in /data/firmware/mediatek/mt7610u.bin - seems to work.

1 Like