BREW directed SMS | developer.brewmp.com BREW directed SMS | developer.brewmp.com

Developer

BREW directed SMS

Forums:

my app is suppose to wake up when receiving the BREW directed SMS. it works on emulator, but not on LG VX8300, the BREW directed SMS was received as regular SMS, the app is never waken up...
I read some other thread mentioning not to log-in when sending the SMS thru vtext.com, and I didn't do the log-in, but still not working... in in-box, the msg received is "(UNVERIFIED SENDER)
//BREW:0x01012EF1
Nov 6, 3:11pm"
I suspect the "(UNVERIFED SENDER)" was added as part of the msg, that's why it's not recognized as BREW directed SMS? If that's the case, how do I get rid of this?

thanks!!!
Jean

though i found "UNVERIFED SENDER" is not a part of the message, its being shown as sender name.
Not sure what's the issue with the portal. But this surely does not happen if you send it from another device.
Try debugging into it, may be it helps:-
https://brewx.qualcomm.com/bws/websites/dx/en/brew31/ad/kb/running_apps/...
- BREW-directed SMS debug (Debug number 11 on BREW 3.1.0+)
thanks.

though i found "UNVERIFED SENDER" is not a part of the message, its being shown as sender name.
Not sure what's the issue with the portal. But this surely does not happen if you send it from another device.
Try debugging into it, may be it helps:-
https://brewx.qualcomm.com/bws/websites/dx/en/brew31/ad/kb/running_apps/...
- BREW-directed SMS debug (Debug number 11 on BREW 3.1.0+)
thanks.

thanks much for the debug info. I'll go find out what's really going on...
Thanks,
Jean

thanks much for the debug info. I'll go find out what's really going on...
Thanks,
Jean

I tried sending the BREW directed SMS from another cell phone (not VZW though), still my app didn't receive it, instead it's received as regular SMS...
I tried turning on the SMS test mode, doesn't help... the SMS never gets to the app ( in this way, any debug I have in the app won't help)...
and it works perfectly on the emulator...
I had this BREW directed SMS works on a different model couple of years ago, never had a problem...
could it be the device-related problem? I'm now using LG-VX8300, does anyone ever have luck sending BREW-directed SMS to this phone?
Many thanks,
Jean

I tried sending the BREW directed SMS from another cell phone (not VZW though), still my app didn't receive it, instead it's received as regular SMS...
I tried turning on the SMS test mode, doesn't help... the SMS never gets to the app ( in this way, any debug I have in the app won't help)...
and it works perfectly on the emulator...
I had this BREW directed SMS works on a different model couple of years ago, never had a problem...
could it be the device-related problem? I'm now using LG-VX8300, does anyone ever have luck sending BREW-directed SMS to this phone?
Many thanks,
Jean

i found it to be working fine on VX8300.
but i sent the sms from another VZN device.
there should be a colon after the classid of ur App
//BREW:0x0193837:this
didn't you get no help from the debug mode for BREW Debug sequences?
thanks.

i found it to be working fine on VX8300.
but i sent the sms from another VZN device.
there should be a colon after the classid of ur App
//BREW:0x0193837:this
didn't you get no help from the debug mode for BREW Debug sequences?
thanks.

thanks so so much for pointing this out: Quote:there should be a colon after the classid of ur App
it works now with the 2nd colon added in the SMS I sent from other handset (non-VZW).. also works when sending from vtext.com (with 2nd colon added) but the SMS debug (mode 11) needs to be on in order to ignore the "(" added at the very beginning of msg.
I was too lazy adding the text payload when testing the BREW-directed SMS, as it states in the Qualcomm online knowledge page https://brewx.qualcomm.com/bws/content/gi/common/appseng/en/knowledgebas... , the 2nd colon is not needed if there's no text payload. though I think it's wrong, at least not work with my case, can someone from Qualcomm please verify this, and do any necessary correction? *sigh* I've been wasting hours on this meaningless issue...
Thanks,
Jean

thanks so so much for pointing this out: Quote:there should be a colon after the classid of ur App
it works now with the 2nd colon added in the SMS I sent from other handset (non-VZW).. also works when sending from vtext.com (with 2nd colon added) but the SMS debug (mode 11) needs to be on in order to ignore the "(" added at the very beginning of msg.
I was too lazy adding the text payload when testing the BREW-directed SMS, as it states in the Qualcomm online knowledge page https://brewx.qualcomm.com/bws/content/gi/common/appseng/en/knowledgebas... , the 2nd colon is not needed if there's no text payload. though I think it's wrong, at least not work with my case, can someone from Qualcomm please verify this, and do any necessary correction? *sigh* I've been wasting hours on this meaningless issue...
Thanks,
Jean

"Some web-based methods of sending an SMS will prepend additional information in the message payload, such as callback number or other identification information, so it will be necessary to activate this debug mode in order to properly recognize the BREW-directed SMS message during application testing."
the above from BREW debug document helps when testing, though when the app goes commercial, does the user need to turn the debug mode on in order to properly recognize the BREW-directed message sent from a web-based mail server?
Thanks!
Jean

"Some web-based methods of sending an SMS will prepend additional information in the message payload, such as callback number or other identification information, so it will be necessary to activate this debug mode in order to properly recognize the BREW-directed SMS message during application testing."
the above from BREW debug document helps when testing, though when the app goes commercial, does the user need to turn the debug mode on in order to properly recognize the BREW-directed message sent from a web-based mail server?
Thanks!
Jean