Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

Capabilities (Symbian Signed)/ProtServ Capability

From Wiki
Jump to: navigation, search
Article Metadata
Created: hamishwillee (16 Dec 2010)
Last edited: hamishwillee (20 Jul 2012)

The ProtServ (protected server) capability is required to register a protected server name (one beginning with the ! character). Processes without this capability have their thread priorities capped - they cannot run at higher priority than important system servers.

This capability can be used with developer certificates and Symbian Signed tested applications, and by using open signed online for testing.


Many system servers in Symbian OS are transient - that is, they shut down when not in use to save memory. A protected name prevents an untrusted process from spoofing or unintentionally clashing with a system server, while still allowing the client/server framework to be used by all. A thread running at very high priority can starve the system of CPU and cause the device to "lock up" because the window server has no chance to refresh the screen.


The kernel checks this priority when a process registers a server, or changes its thread priorities.


ProtServ is needed by any plugin to a system server.

Licence icon cc-by-sa 3.0-88x31.png© 2010 Symbian Foundation Limited. This document is licensed under the Creative Commons Attribution-Share Alike 2.0 license. See for the full terms of the license.
Note that this content was originally hosted on the Symbian Foundation developer wiki.

This page was last modified on 20 July 2012, at 09:31.
25 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.


Thank you!

We appreciate your feedback.