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. Thanks for all your past and future contributions.

Developing applications for secondary display

From Wiki
Jump to: navigation, search
Article Metadata
Created: visrini (25 Sep 2007)
Last edited: hamishwillee (27 Jul 2012)

To develop an application that shows up on the secondary display, as you mentioned you have to set the "default_screen_number = 1" in your application's _reg.rss

For ex:

default_screen_number = 1;// 0 for main display
hidden = KAppIsHidden;
launch = KAppLaunchInBackground;

All applications for secondary screen should explicitly set the secondary display orientation when gaining foreground:

CMySecApp::HandleForegroundEventL( TBool aForeground )
if( aForeground )

The key mappings for the keys in secondary display are:

  • Left soft key (rewind) - EKeyCBA1 (EKeyDevice0)
  • Middle soft key (play/pause) - EKeyOK (EKeyDevice3)
  • Right soft key (forward) - EKeyCBA2 (EKeyDevice1)
  • Volume up key - EKeyUpArrow
  • Volume down key - EKeyDownArrow
  • Mode key - EKeyF10
  • Camera key - EKeyCamera

However there is a problem with drawing the standard Avkon conrols. Symbian / Avkon controls or the default Symbian application UI do not scale well or at all to the small screen. The resolution mismatch is a known problem in Avkon implementation. The only way to have a proper application would be to write your own custom UI controls to draw on the secondary screen. There isn't much that can be done besides hard coding the correct display size. Moreover Symbian global UI does not work on secondary screen. This includes parts of the standard status pane content, like network status.

This page was last modified on 27 July 2012, at 05:59.
37 page views in the last 30 days.