Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

We are testing an application that receives SMS messages. When we send the SMS within the emulator, the applet is started and the application works fine. However when we use the telephone, the applet does not get started when the SMS arrives. It works fine if the applet is up and running when we send the SMS.

The telephone we are using is an AUDIOVOX CDM9500.
Is there something that could cause the applet not to be started?

Thanks

Does your text payload have spaces in it?
With BREW 1.1, if the BREW SMS text payload has spaces in it then the SMS will not be delivered to the BREW applet . Eg:
//BREW:0x11223344:A Space
will not be delivered. This is a bug with the BREW libraries and is fixed in 2.0.

Does your text payload have spaces in it?
With BREW 1.1, if the BREW SMS text payload has spaces in it then the SMS will not be delivered to the BREW applet . Eg:
//BREW:0x11223344:A Space
will not be delivered. This is a bug with the BREW libraries and is fixed in 2.0.

Thanks Loui,
My message has no spaces in it.
Basically the message gets delivered only if the application is already running.

Thanks Loui,
My message has no spaces in it.
Basically the message gets delivered only if the application is already running.

Can you post an example of your BREW SMS. Other things that can break it are omitting the "0x" in the classID, other non alpha-numeric characters etc.

Can you post an example of your BREW SMS. Other things that can break it are omitting the "0x" in the classID, other non alpha-numeric characters etc.

This is the message I am sending:
//BREW:0x010123ff:>QAT;SOURCE=xxx;ID=AUDIOVOX<
Thanks again

This is the message I am sending:
//BREW:0x010123ff:>QAT;SOURCE=xxx;ID=AUDIOVOX<
Thanks again

Which carrier/operator are you using? When I talked to someone from Verizon recently he indicated that their Network still does not support SMS wakeup of brew applications.
I have not yet been able to test this because our application has not yet reached that stage.
Also, I am intrigued about how you tested SMS wake up under the emulator!
Regards
Vasanth

Which carrier/operator are you using? When I talked to someone from Verizon recently he indicated that their Network still does not support SMS wakeup of brew applications.
I have not yet been able to test this because our application has not yet reached that stage.
Also, I am intrigued about how you tested SMS wake up under the emulator!
Regards
Vasanth

Hi Vasanth,
In order to test SMS within the emulator use the Tools|TAPI|Send SMS option.
We are using Verizon's network, however as far as I understand this has nothing to do with the carrier but BREW.
One thing we notice is that it worked fine in BREW 2.0 emulator but it didn't work using the 1.1 emulator.
We were receiving the EVT_APP_MESSAGE, but in the emulator you can do some work without having to call ISHELL_StartApplet.
What we notices is that when using the 1.1 emulator (or phone) it is necessary to call ISHELL_StartApplet before doing something else.
Thanks
Sandra

Hi Vasanth,
In order to test SMS within the emulator use the Tools|TAPI|Send SMS option.
We are using Verizon's network, however as far as I understand this has nothing to do with the carrier but BREW.
One thing we notice is that it worked fine in BREW 2.0 emulator but it didn't work using the 1.1 emulator.
We were receiving the EVT_APP_MESSAGE, but in the emulator you can do some work without having to call ISHELL_StartApplet.
What we notices is that when using the 1.1 emulator (or phone) it is necessary to call ISHELL_StartApplet before doing something else.
Thanks
Sandra

Have you tried with a simple message, eg:
//BREW:0x010123ff:Test

Have you tried with a simple message, eg:
//BREW:0x010123ff:Test

Can you post the code that you have written in APP_EVT_MESSAGE?
Regards
Arun Bangari

Can you post the code that you have written in APP_EVT_MESSAGE?
Regards
Arun Bangari

Here it is
case EVT_APP_MESSAGE:
{
if (pMe->m_AutoStartApplet == CST_YES)
{
ISHELL_StartApplet(pMe->a.m_pIShell, AEECLSID_MYAPP);

pMe->m_ComOption->ParseAppReceivedData( (char *)dwParam, STRLEN((char *)dwParam) );
return TRUE;

According to the tests in the emulator EVT_APP_START does not get called when the SMS is received and the application is not running. We set the AutoStartApplet flag to NO in EVT_APP_START, we do that in order to call StartApplet only if the Application is not running.
A later test on the phone has shown that sms is not sent to the application if the phone is closed but it is if the phone is open (no matter if the application is running or not).
Sandra

Here it is
case EVT_APP_MESSAGE:
{
if (pMe->m_AutoStartApplet == CST_YES)
{
ISHELL_StartApplet(pMe->a.m_pIShell, AEECLSID_MYAPP);

pMe->m_ComOption->ParseAppReceivedData( (char *)dwParam, STRLEN((char *)dwParam) );
return TRUE;

According to the tests in the emulator EVT_APP_START does not get called when the SMS is received and the application is not running. We set the AutoStartApplet flag to NO in EVT_APP_START, we do that in order to call StartApplet only if the Application is not running.
A later test on the phone has shown that sms is not sent to the application if the phone is closed but it is if the phone is open (no matter if the application is running or not).
Sandra

I wonder, were you able to solve this issue after all?:confused:

I wonder, were you able to solve this issue after all?:confused:

Yes, it was a problem with that kind of phone only, so it was solved by the manufacturer.
The sms is not sent to the phone when the clam shell is shut but there is no problem if the clam shell is open.
-------------------------------------------------------------------------
This is what BREW support told me:
What an application can and can't do when the clamshell is closed is OEM dependent. Future versions of the Porting Kit that Qualcomm supplies to OEMs will help to standardize OEM porting for clamshell-related functions (events to send when opened/closed, whether BREW should be suspended or not) such that the behavior will the similar across devices. We expect that, in future BREW devices, BREW not be suspended on closing the clamshell and that BREW apps can be started when the clamshell is closed. OEMs may prevent apps from writing to the primary display when the clamshell is shut.
The behavior on the CDM-9500 is that ISHELL_StartApplet cannot be called when the clamshell is shut. The SMS message can be written to a file in EVT_APP_MESSAGE processing, but I have not had success with playing a sound via ISHELL_Beep.

Yes, it was a problem with that kind of phone only, so it was solved by the manufacturer.
The sms is not sent to the phone when the clam shell is shut but there is no problem if the clam shell is open.
-------------------------------------------------------------------------
This is what BREW support told me:
What an application can and can't do when the clamshell is closed is OEM dependent. Future versions of the Porting Kit that Qualcomm supplies to OEMs will help to standardize OEM porting for clamshell-related functions (events to send when opened/closed, whether BREW should be suspended or not) such that the behavior will the similar across devices. We expect that, in future BREW devices, BREW not be suspended on closing the clamshell and that BREW apps can be started when the clamshell is closed. OEMs may prevent apps from writing to the primary display when the clamshell is shut.
The behavior on the CDM-9500 is that ISHELL_StartApplet cannot be called when the clamshell is shut. The SMS message can be written to a file in EVT_APP_MESSAGE processing, but I have not had success with playing a sound via ISHELL_Beep.

Hi,
did you encounter the same problem on any of the other handsets? In my experience 9500 behaves exactly as you described and SCH-530 treats BREW-directed SMS as normal SMS text messages, T720 does not play sounds only vibrates with clamshell closed. Any other handset problems?
I appreciate you sharing your experience,
Thanks,
Nick

Hi,
did you encounter the same problem on any of the other handsets? In my experience 9500 behaves exactly as you described and SCH-530 treats BREW-directed SMS as normal SMS text messages, T720 does not play sounds only vibrates with clamshell closed. Any other handset problems?
I appreciate you sharing your experience,
Thanks,
Nick

Theoretically, application directed SMS shouldn't going to regular SMS inbox, however OEMs often implement SMS feature in their own way without much thought, causing grief to developers.
ruben

Theoretically, application directed SMS shouldn't going to regular SMS inbox, however OEMs often implement SMS feature in their own way without much thought, causing grief to developers.
ruben

sperona wrote:This is the message I am sending:
//BREW:0x010123ff:>QAT;SOURCE=xxx;ID=AUDIOVOX<
Thanks again
Can you let me know how did you get ">QAT;SOURCE=xxx;ID=AUDIOVOX<" from the SMS message?
Thanks.

sperona wrote:This is the message I am sending:
//BREW:0x010123ff:>QAT;SOURCE=xxx;ID=AUDIOVOX<
Thanks again
Can you let me know how did you get ">QAT;SOURCE=xxx;ID=AUDIOVOX<" from the SMS message?
Thanks.