You Are Here:

Community: Wiki

This page was last modified on 20 October 2008, at 16:36.

KIJ000768 - Wireless Messaging API with Push registry behaves inconsistently when receiving several SMSs in S60

From Forum Nokia Wiki



ID KIJ000768 Creation date October 19, 2007, updated February 6, 2008
Platform S60 2nd Edition, S60 3rd Edition, S60 3rd Edition, FP1 Devices All S60 2nd and 3rd Edition devices
Category Java ME Subcategory Wireless Messaging API


Keywords (APIs, classes, methods, functions):

Overview

When sending several SMSs between two S60 devices, WMA with PushRegistry behaves inconsistently in the receiver device.

Description

When sending several SMS messages (5-10 or more), the unsigned receiver WMA MIDlet using PushRegistry will perform inconsistently when launching it, for example, resulting in slow queuing of received SMSs or SymbianOSError messages. Sometimes, especially when receiving 10 or more SMSs, launching fails and the receiver application crashes without error messages or exceptions.

How to reproduce

Download the WMAExample MIDlet and install the unsigned application on two S60 devices. By using the other device’s MIDlet, send 5 to 10 SMSs to the other device. After sending all the SMSs, launch the MIDlet on the receiver phone.

Solution

Signing the MIDlet with the Identified Third Party Protection Domain certificate solves the problem and allows the MIDlet to launch automatically. After signing, you need to change the Autostart application security setting to "always allowed".

Related Wiki Articles

No related wiki articles found

Rate This

 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZidentifierQSxhttpE3aE2fE2fwikiE2eforumE2enokiaE2ecomE2findeE78E2ephpE2fKIJ000768E5fE2dE5fWirelessE5fMessagingE5fAPIE5fwithE5fPushE5fregistryE5fbehavesE5finconsistentlyE5fwhenE5freceivingE5fseveralE5fSMSsE5finE5fS60X qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfntypeZCommunityContentQ qdcZtypeQUqfntypeZKnowledgeBaseContentQ qdcZtypeQUqfntypeZKnownIssueQ qdcZtypeQUqfntypeZE52esourceQ qdcZtypeQUqfntypeZWebpageQ qdcZtypeQUqfntypeZWikiContentQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qfnZtopicQUqfnTopicZmessagingQ qfnZtopicQUqfnTopicZsmsQ qfnZtypeQUqfntypeZCommunityContentQ qfnZtypeQUqfntypeZKnowledgeBaseContentQ qfnZtypeQUqfntypeZKnownIssueQ qfnZtypeQUqfntypeZE52esourceQ qfnZtypeQUqfntypeZWebpageQ qfnZtypeQUqfntypeZWikiContentQ qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfntypeZCommunityContentQ qrdfZtypeQUqfntypeZKnowledgeBaseContentQ qrdfZtypeQUqfntypeZKnownIssueQ qrdfZtypeQUqfntypeZE52esourceQ qrdfZtypeQUqfntypeZWebpageQ qrdfZtypeQUqfntypeZWikiContentQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ