Archived:Custom FEP replaced with the default one at device startup (Known Issue)
Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.
Article Metadata
Compatibility
Platform(s): S60 3rd Edition
S60 3rd Edition, FP1
S60 3rd Edition, FP1
Article
Created: User:Technical writer 1
(29 Aug 2007)
Last edited: hamishwillee
(18 Jun 2012)
Description
When a custom FEP (Front End Processor) has been installed with CCoeEnv::InstallFepL() and the phone is restarted, the active FEP always get reverted to the default T9 (AknFep) implementation.
Solution
A workaround is to load the custom FEP at startup. To run an application automatically at phone startup, the Startup List Management API can be used. Note however, that:
- There is no control over the sequence in which the applications on the startup list are run
- Items on the startup list are launched at the end of the startup sequence
- If the requirement is to load the FEP before the PIN dialog, then there is currently no known solution for this
- The application should provide a possibility to select between a custom and the default S60 FEP
(no comments yet)