Originally Posted by ah-
The problem with that is that with the current method of loading the plugin it's not possible to get code executed automatically at boot. This would require finding another way to load the plugin, which requires be quite a bit of work.
Out of curiosity, how does it get loaded? I am familiar with embedded Linux development so get technical on me if that helps.
The plugin just seems to overwrite a shared library with one that has the tweaks, and which requires the Library setting to be selected to activate them. Rather than this, could you not also provide some extra logic in the boot script (/etc/init.d/rcS) or a script called at the end of the boot script
to check to see if the plug-in is set to autostart, and if so backup and then overwrite the stock shared library with a tweaked shared library that doesn't require the library button being pressed?