Namespaces

Variants
Actions

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 over the next few weeks. Thanks for all your past and future contributions.

UID standby phone

From Wiki
Jump to: navigation, search
Article Metadata
Article
Created: amitkankani (27 Oct 2008)
Last edited: hamishwillee (30 May 2013)

The phone screen or standby screen UID in different versions of s60:

The standby screen UID is different for different S60 versions, and different for different Feature Packs too.

The UID of standby screen (the process is called Phone) on 2nd edition is: 0x100058b3

The UID of standby screen (the process is called Phone) on 3rd edition is: 0x100058b3

The UID of standby screen (the process is called Standby Mode) on 3rd edition and 3rd edition FP1 is: 0x101fd64c

The UID of standby screen (the process is called Standby Mode) on 3rd edition FP2 is: 0x102750F0

The UID of standby screen (the process is called Home screen) on 5th edition is: 0x102750F0

So now if anyone wants to use the UID of standby screen, then one needs to define these with appropriate macros and use them. May be something like this:

#ifdef __SERIES60_3X__
const TUid KUidStandBy = { 0x101fd64c }; // For 3rd Edition
const TUid KUidStandBy_FP2 = { 0x102750F0 }; // For 3rd edition Emulator, FP2 and 5th edition devices
#else // #ifdef __SERIES60_3X__
const TUid KUidStandBy = { 0x100058b3 }; // For 2nd Edition
#endif // #ifdef __SERIES60_3X__

and then use it...

UIDs of running applications can be found using Y-Task.

On S^3 it looks like the UID is again 0x100058b3 at least it is so on my E7.

This page was last modified on 30 May 2013, at 04:36.
54 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×