Archived:Wrong screen color depth returned in compatibility mode on S60 2nd Edition FP2 (Known Issue)

Comments

(no comments yet)

Log in or Join to leave comments.

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}}.

The article is believed to be still valid for the original topic scope.

Article Metadata

---

Tested with

Devices(s): Nokia N70, Nokia N90

---

Compatibility

Platform(s): S60 2nd Edition, FP3

---

Article

Created: User:Technical writer 1 (13 Oct 2005)

Last edited: hamishwillee (21 Jun 2012)

Overview

Wrong screen color depth is returned for applications running in compatibility mode on S60 2nd Edition, Feature Pack 3 devices.

Description

S60 2nd Edition, FP3 devices with a 256K (18-bit) color screen have a compatibility mode for running legacy applications that do not support UI scalability. The resolution in compatibility mode is fixed to 176x208 and the effective color depth is 64K (16-bit).
When the color depth is queried from the screen device (CWsScreenDevice), it always returns EColor16MU even if the application is currently in compatibility mode, for which the effective value would be EColor64K.

How to reproduce

In an application running in compatibility mode, check the return value (TDisplayMode) of
CCoeEnv::ScreenDevice()->DisplayMode();

Solution

No solution exists.