Push Registry Midlet in Blackberry

We have developed a Midlet (SMS Send, Receive) implementing Push Registry (Dynamic Registeration). The Midlet needs to open/run, once the SMS is received on that particular port. The Midlet is working fine in Nokia, Sony Ericson and other leading devices.

I have installed the Midlet (Jar file) in Blackberry 8100. (I haven't converted the same into .cod)

On Blackberry 8100, the Midlet receives the SMS in the port if the Application is open and running. If the Application is in the closed state it displays the message "Complete" whenever a message comes on that respective Port, but doesn't opens the Application.

I want the Applicaton(Midlet) to open up once the Message is received.

Re: Push Registry Midlet in Blackberry

i have the same problem with my midlet on my 8310 device. i implemented the dynamic auto start as given in the documents you postet. but the application will only receive sms when it is already running.

when starting the application manually, it asks 3 times for permission to access javax.io.connector.sms (2 times) and javax.wireless.messaging.sms.receive. when a new message arrives, the running application asks a forth time to allow sms.receive before it will receive the message. i have set all application permissions to "allow".

the application has been installed as a cod/alx file from pc.

i build the app with sun wireless toolkit and then convert it into a cod file with rapc.

will signing the application help to avoid all the asking for permisson?

is there any difference in behavior if i install the application ota? (i just learned that static push registry will cause the application not to receive sms when startet manually)

do i have to set any permission options in the wtk before compiling? i tried all the options but found no difference in behavior

Re: Push Registry Midlet in Blackberry

so it seems like the promts for connector.sms and sms.receive are operator specific, because there ist no option to remember the setting nor do the application security settings have any influence on the app behaviour.

do i have to sign my app with the blackberry certificate or with a verisign/thawte to get rid of these operator prompts?

now i have rebuild the app with a static push registry and have the folloing strange behaviour:

Re: Push Registry Midlet in Blackberry

It is expected that the dynamic push registry sample does not auto start (this sample is not designed to).

There is an issue that can prevent auto start PushRegistry clients from receiving notifications after the application has been opened. This has been fixed in BlackBerry handheld software version 4.5.0. The work around is to merge the two samples together. Meaning that you create an application based on the auto start sample that also dynamically registers the same URL when it is opened.

Mark SohmBlackBerry Development Advisor

Please refrain from posting new questions in solved threads.Problem solved? Click the Accept As Solution button.Found a bug? Report it using Issue Tracker

I have a midlet (A) which registers another midlet (B) before closing using registerAarm to start it after 30 min. This works fine in the J2ME tool kit simulator. but when i deploy the application on 8100 this does not start the second midlet

Below is the code used for registering

long time = PushRegistry.registerAlarm("PushAlarm", new Date().getTime() +30*60*1000);

If I push the same midlet (A) to be invoked after 30 min, that works fine. But i want to start the another Midlet "B" instead