starting the application on startup

The reccomended approach to do this is:

1) write a server application (.exe) to do the monitoring etc.
2) write a client application (.app) to talk to the server and display a user interface
3) write a recogniser to start the server on boot-up.

To find out how to do 1 and 2 above, read "Symbian OS C++ for Mobile Phones" by Richard Harrison, it has a complete working example and lots of hints and advise.  To write a recognisr, check out the EzBoot example on this site (http://www.newlc.com/EzBoot.html).

I use the following code in my recogniser to ensure the device is in a stable state...

  TRequestStatus status(KRequestPending);
  RSystemAgent agent;
  agent.Connect();

  RTimer timer;
  timer.CreateLocal();
  TTimeIntervalMicroSeconds32 time(5000000);
  TInt trycount = 0;
      
  while ((agent.GetState(KUidSIMStatus) != ESASimOk) && (trycount++ < KMaxTries))   
  {
    timer.After(status,time);
    User::WaitForRequest(status);
  }
  timer.Close();
  agent.Close();

It seems to work fine for Nokia devices, Sony Ericsson devices never return ESASimOk, so that's why the KMaxTries is there.

Hi petxolobo,

My recognizer is indeed come after my app in the pkg file. The recognizer works well and actually, on a different 6600 phone, I don't need to put the timeout in the it. The same is true for a 6630 phone.
So, I'm guessing that on the problematic 6600 phone, some resources are not loaded when the recognizer launch my app and this causes my application to quit.
Problem is I don't know what those resources are.

Imzadi

Hi Marwa_fci,

I think that there is some confusion here.

I see many people asking the question "how can i start my app at install and device boot?"  and the answer comes swiftly back "use a recogniser"

this has lead to FALSE belief that recognisers are for starting apps at install and device boot.

What recognisers are REALLY designed for is detecting the use of a file of a particular MIME type and launching the appropriate application to deal with it.  an example of this that will be familar to all would be that there is a recogniser that detects the use of the proprietory .sis file format and launches the installer. 

Now, in order for a recogniser to do it's job it must be run by the system at boot time. Here we can take advantage of this to "mis-use" the recogniser concept to launch our app when the recogniser gets booted.

So basically what you do is write a dummy recogniser that isn't really looking for any meaningfull MIME type but that runs your app when it, the recogniser, is constructed.

there is a health warnings here:

things like recognisers, notifiers etc are all run up by the system, you don't control them.  So if they panic or behave badly you can have all sorts of rather nasty problems.  be carefull.

Happily there is a easy route, you could try using ezBoot.  this is a kind of configurable recogniser that has been created for the purpose of booting apps. 

http://www.newlc.com/EzBoot.html?var_recherche=ezboot

Best regards

PL

Hi marwa_fci,

If you liked the EzBoot idea, why not have a look at the source code? here http://www.newlc.com/Writing-a-recognizer-The-EZBoot.html
Imzadi