Startup Management list API for unprotected uids

[mateen_maldar]

Hi All,

I used a Protected UId for Startup management list 0x6.. range and it worked fine ..

The interface defines rules and policies, which allows 3rd party application to make modification to the device's startup list during the installation/uninstallation process.
1. SW Installer UI acceptes the modification request to the startup list only from trusted software.
2. SW Installer UI allows 3rd party application to add/remove to/from the startup list only executables deliveres within their own installation package. 3. Startup list modification requests must be installed to SW Installer UI server import directory (c:\private\101F875A\import).
4. The modification requests are accepted if its name (file name) equals to the UID of the currently proceding installation package otherwise they are rejected.
5. The modification request must contain: Name of executable file, Exception Policy

Well know we are trying to release our app as a freeware for 3rd edition and startup management list doesn't work as per rule number 1. of the startup management list..

So i think i should use a recogniser as did in lower editions or any other alternative avaliable for using startup management list api's in unprotected uids...

Any pointers on this will be highly appriciated.....

Regards,
Mateen Maldar

[petrib]

Symbian Signed freeware is trusted, I should think, and thus gets an UID from the trusted range. Or am I mistaken?

https://www.symbiansigned.com/app/page/freewareFaq

[mateen_maldar]

hi petrib,

well i wanted to test the app launch on boot for unprotected uids..
as per ur guidence my app need to signed from the symbian signed to get a trusted freeware and then use the startup or reconginser can be used..

It will be a tedious process in development..

Regards,
Mateen Maldar

[Paul.Todd]

No, you need to go to www.symbiansigned.com and get a developer certificate and also request a range of UID's to be assigned to your application.

You can then test it before submitting it to freeware signing.

[mateen_maldar]

hi Todd,

You can then test it before submitting it to freeware signing.

Can u tell me how can i test it for the app launch on boot (on emulator or on real target)for unprotected uids..

coz it simply ignores it on the real device..

Thanks and Regards,
Mateen Maldar

[petrib]

Don't try to fight against the system by using an unprotected UID. Get a developer cert and request a protected UID from Symbian for your app. Problem solved.

[Paul.Todd]

As petrib says,

goto SymbianSigned.com, register.
Create a developer certificate and request protected UID's
Change the UID's in your application and sign it with your dev cert.

Problem solved.

[mateen_maldar]

hi,

i know the process of the signing for a protected uid from symbiansigned.com
and i worked on it successfully.. Well i was trying the same for unprotected uid ,coz i'm intrested in knowing the internal behaviour of the system and its programming..

Anyways thanks for the replies...

Thanks and Regards,
Mateen Maldar

[Paul.Todd]

When you apply to get it signed as freeware, your application is still required to use trusted UID's.

Your package file just needs to display a disclaimer at the front saying its freeware