Yesterday I noticed too the different filter on the plug-in page (it seems that doesn’t work very well by the way), but I want to ask if the store is supposed to work with custom images or not; now is not working, but I don’t know if is blocked by design for security reasons.
If this is the case, it’s no big deal for me: I’ll just reflash the official build to buy a plugin and then reflash the Starless image, but for some people that could be a deal breaking.
Thanks
I’d also like to know if there’s anything I can do to enable it, or if it’s simply disabled for custom images.
@Abotte I managed to fix list parameters edit on the device, I’m near to another beta release
I’ve now had the chance to update my Mod Dwarf and am really impressed with this so far! So good to have on-device editing.
I’d like to try performance mode on an Android tablet connecting over USB but looking at other threads I get the impression that this doesn’t currently work - is that right? If so presumably the only option is is Bluetooth (if only I could find that dongle!)?
Hi! I’m using this firmware and the midi is working for me. I’ve got no promblems with a midi keyboard via midi usb and with a FCB1010 via midi in. 
Did you try mod-ui hotfix-1.13 branch? I think each firmware uses the same number hotfix for mod-ui and mod-host. Mod-desktop probably uses master branch.
But then some new functionalities like drag&drop plugins are lost…. Perhaps it could be better plugin-store branch?
Hi @jon,
can you be more specific about the mod labs in the plugin store?
Because I just reflashed to original firmware and I see mod labs there with it too:
From my understanding the switch is present if you check “show mod labs plugin in the store” in the advanced settings page:
Thank you!
Again :),
This is moslty a bug fix release, waiting for some new feature to became stable enough to be released.
Thanks as always to @Abotte and @jon
Download: Release aLabs version 3 (beta) · sejerpz/alabs-mod-custom-images · GitHub
Andrea, you’re right, the latest official release we can download has that layout.
But I’m sure that the one that was fetched OTG was different: the ability to visualize beta plugin was a filter similar to “Ïnstalled only” and was something like “Include beta plugins”.
Bye
Yep you are right, I remember the beta filter like you described.
Hey @AndreaDelSignore, from where did you install the image? From the one available in the wiki?
On the official image, which is called “show beta plugins”.
If you installed the image from the wiki and that stayed like that, it may be something else and I would suggest that you do a factory reset (with all the security backups) and see if that goes back to beta.
Anyway, I guess that with that image, the plugins that appear with the Labs switched on, are exactly the beta plugins…if I’m not wrong.
I think that I used the stock Open Image, when home I’ll try also with the last official signed release from the wiki.
Thanks
Can confirm, in the official signed release the beta plugins management is a little bit different:
I don’t think is important, but now we now that there are “some differences” between the code included in the released firmware and the open image.
Any news on the Store support for the custom images?
Hi Andrea,
I found some defective controls in the on board plug-in editor window:
Thanks!
Hi @AndreaDelSignore, I found another minor bug that I managed to confirm and it happens only with your image (not on the official one).
It is related to the System Upgrade. With your Starless version, the device keeps stuck on the “Starting Upgrade. Please Wait” screen when you do it either from the Device Settings menu or from the WebGUI settings.
The only way that I managed to do it was by booting the device while holding footswitch A + the left-most button.
Again, not a hardcore thing 
Thanks Jon I already notice that behaviour no idea why.
I already opened a issue: Start update mode from mod settings doesn't work · Issue #15 · sejerpz/alabs-mod-custom-images · GitHub
Thanks for confirming it
You’re welcome
I was thinking a bit about that yesterday. It may be related to the fact that you should not receive notifications on the WebGUI for a new (official) MOD OS release.
But I would say the “no notifications” can make some sense.
Hi,
yesterday I found the reason and it’s something totally unrelated to the mod-ui o dwarf-controller modifications.
It’s the way I unpacked and packed the tar file after applying my work.
I don’t use the -p parameter in the tar command, so executables with the “sticky” bit set (like /sbin/reboot) can only be used by root, instead the hmi program is logged on the system serial port with the hmi user so it can’t reboot the system in order to start the update process.
I patched my script and I’ve done some successful tests, I also fixed the bug signaled by @Abotte so this weekend I planned another beta release (hopefully the last one).
Thanks for your efforts and dedication: your work is greatly appreciated!!!
