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.

Revision as of 14:23, 25 May 2014 by lpvalente (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Difference in SMS and PushRegistry behavior in Series 40 and S60

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

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


This article explains the differences between SMS and PushRegistry behaviour in Series 40 and Symbian.

Article Metadata
Code ExampleTested with
Devices(s): Nokia 6600, Nokia N90, Nokia 6101
CompatibilityArticle
Created: User:Technical writer 2 (24 Aug 2006)
Last edited: lpvalente (25 May 2014)

Description

When a MIDlet registers SMS connections with PushRegistry, the behaviour is different in Series 40 and S60.

The problem can reproduced by using the Nokia Developer example MIDP 2.0: Wireless Messaging API Example.

It is possible to initiate a MIDlet (WMAExample.zip in this case) with an SMS and retrieve its contents in many phone models, such as the Nokia 6101 (Series 40) and many other MIDP 2.0 models, but the same application cannot retrieve the SMS content if you try to run it on an S60 device (such as the Nokia 6600 and the Nokia N90) .

Using PushRegistry.listConnections() prior to the call to the listen() method solves the problem. This should be the correct behaviour, as this kind of code is the standard method for all types of PushRegistry-activated MIDlets to check the way they were started.

Series 40 may have a different implementation behaviour as it is a different operating system; some significant differences are known, especially for the PushRegistry.

In Series 40, notifyIncomingMessage method is called when the MIDlet starts up, so the developer can retrieve the content of the message within this method. In S60, this method is not called, and the MIDlet has to use PushRegistry.listConnections(true) within startApp() method in order to perform the same operation.

WMAExample.zip is an Eclipse project with an updated WMAExample.java, adding to the startApp() method the needed check for connections and messages that may be pending in the PushRegistry.

This page was last modified on 25 May 2014, at 14:23.
68 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.

×