Archived:Custom FEP replaced with the default one at device startup (Known Issue)
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.
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