We have an application that needs a lot of manufacturer-approved capabilities. It also need to start up on boot. So we figured we could use another sis that has the signed application as an embedded sis and adds a few files with the additional parameters. But then we found that auto-start doesn't work for embedded sis files.
Does this mean we'll have to send the application to be signed again every time we want to change some of these parameters (and this will probably be necessary for every different operator we deploy with)? Is there any way to circumvent this problem?
With Java apps, these parameters would go in the jad file, so we could change them as often as we like without having to send the app to certification again. But Symbian doesn't have jad files.