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.

Archived:Unintentional application switch to background when key blocking is disabled (Known Issue)

From Wiki
Jump to: navigation, search

Archived.pngArchived: 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
Tested with
Devices(s): Nokia 6630, Nokia 6680
Nokia N70, Nokia N90
Nokia N73, Nokia N80
Platform(s): S60 2nd Edition, FP2
S60 2nd Edition, FP3
S60 3rd Edition
S60 2nd Edition FP3
S60 2nd Edition FP2
S60 2nd Edition (initial release)
Created: User:Technical writer 1 (November 10, 2005, updated June 18, 2008)
Last edited: hamishwillee (21 Jun 2012)



After disabling the key blocking with CAknAppUi::SetKeyBlockMode(), certain key combinations cause the application to unintentionally switch to background.


Most S60 games set the key-blocking mode off to allow multiple simultaneous key presses. This can be done in the application UI (CAknAppUi) implementation by calling
On S60 2nd Ed, FP2 or newer devices, the following combinations of keys pressed simultaneously are known to cause the application to switch to background when in non-blocking mode:

  • '7' + '8' + '0' + '*'
  • '9' + '0' + '#'

This problem exists also on a number of S60 3rd Edition (3.0) devices, but cannot be reproduced on devices compatible with S60 3rd Edition, Feature Pack 1 and onwards.

How to reproduce

(See detailed description)


No solution exists. Key mapping in games should be designed so that the player does not accidentally press the above combinations.

Note that this issue does not affect S60 3rd Edition, FP1 or FP2 devices.

This page was last modified on 21 June 2012, at 00:51.
70 page views in the last 30 days.