|
|
BIO Message doesn't wake up application
| Thu, 2005-04-28 12:12 | |
|
Hi all, hope you can help me with this.
I'm trying use a SMS msg to wake up my application running on a 6600 and and a 6630. After looking through the Bioexample app I wrote my self * one BIF rss * one BIOParser, just took the BioExample's parser as said the Parse is the same as in BioExample (does nothing but setting the message flag to parsed) the bif file is very simple: Code: RESOURCE BIO_INFO_FILE { message_type_uid=0x10005BCA; // just an example uid for the message, same as my app id message_parser_uid=0x101F402B; // my reserved uid for the message parser message_app_uid=0x10005BCA; // the id of the app I want to wake up message_appctrl_uid=0x00000000; // no control in use description="BIOMSG"; icons_filename="bioexample.mbm"; icon_zoom_levels = {1}; ids= { ID { type=ENbs; confidence=EPossible; character_set=KCharSetDefault; text="BIOMSG"; } }; } Now when I send the phone a message with the body BIOMSG I'd expect the message to be caught straight away by the bif file, which would trigger my app to start. What's really happens is nothing until I select the message and opens it, then the parser kicks in (got some debug printout proving that) and then I get a: "General: System Error" error. if I change the message_app_uid in the bif file to KUidUseDefaultApp, then no error occurs. So I got two questions: 1. why isn't my sms triggering the bif file as soon as it arrives? I don't want users having to open the smns message in order to make app boot up. Have I misunderstood how BIO messaging works? 2. Any idea why my app wont be started by the bif file? I added a ProcessCommandParametersL() to my AppUi class as seen in BioExample, but it still fails, sometihng I missed? thanks for your help |
|
Did you find the solution?
Forum posts: 5
Did you find the solution?
Not really, What I figured out so far is that either you write yourself a little exe which would work as a daemon watching over the SMS inbox using the MMsvSessionObserver, adding the Start On Boot API might make it work nicely.
The other way to do it is to write a WAP push plugin, which would be called for your particular push msg. from this plugin you can start your app
Forum posts: 1379
Yep, fraid so. Thats how it's suppose to work. There are other ways of doing what you want though.
http://www3.symbian.com/faq.nsf/0/26311122AA6EFA3080256D2C002C1667?OpenDocument
thanks for your help
Couldn't say without seeing the code.
didster
Forum posts: 5
http://www3.symbian.com/faq.nsf/0/26311122AA6EFA3080256D2C002C1667?OpenDocument
Hi Didster, thanks for the reply and the link. yes got the symbian book. According to them i have to write a daemon-esque server of some kind, suppose I could just have a little exe using the Start On Boot API and then implement a subclass of the MvsSessionObserver and get the messages that way. Had a look at the framework, had problems getting it to work under the series 60 SDK (missing headers like gsmumsg.h, gsmubuf.h, gsmuset.h, etc, etc) plus the docs isn't very good regarding how to install and how it all hangs together.
Heard that one way of doing this would be to write a plugin for the wapbrowser and let a wap push message trigger the plugin, which would then start the app, haven't really been able to find any good example of how to write a plugin for the wap browser, if you could help me with this it would be greatly appreciated!
regards,
Fredrik