Returning from background

[fabiocberg]

Hi all,

I'm developping an application to S60, more specific Nokia N81.
I need the app can be able to run in background.
So, I did the methods like that:

public void minimize() {
    paused=true;
    display.setCurrent(null);
}

public void maximize() {
    paused=false;
    display.setCurrent(myCanvas);
}

The app calls maximize method like that:

protected void startApp() {
    if (paused) {
        maximize();
    } else {
        initApp();
    }
}

However, when the app is maximized again, my Canvas nevermore calls paint method.
Is the code above correct?

Thanks!

[grahamhughes]

Are you sure startApp() is being called when you think? Many devices call startApp() only once.

Graham.

[fabiocberg]

If your app is opened and you receives a sms or a call, the system calls pauseApp(). When you return to the app, the system calls startApp() again. As far as I know, this occurs in all devices.

But I don't know if this occur when the app returns from background.

That is my question.

[grahamhughes]

If your app is opened and you receives a sms or a call, the system calls pauseApp(). When you return to the app, the system calls startApp() again. As far as I know, this occurs in all devices.

I can offer you a 100% guarantee that this most certainly does not occur in many devices, including the majority of Nokia devices.

If I was you, I'd check my assumption...

[fabiocberg]

I can offer you a 100% guarantee that this most certainly does not occur in many devices, including the majority of Nokia devices.

If I was you, I'd check my assumption...

See this article by sun following:

The remaining methods directly affect the MIDlet's life-cycle. A paused MIDlet calls resumeRequest() to be reactivated. An active MIDlet calls notifyPaused() to be deactivated. A paused or active MIDlet calls notifyDestroyed() to be destroyed. Note that resumeRequest() merely asks the AMS to reactivate the MIDlet; the AMS decides whether and when to reactivate the MIDlet. Reactivation invokes the MIDlet's startApp() method. By contrast, notifyPaused() or notifyDestroyed() causes an immediate transition to the new state; as a consequence, neither pauseApp() nor destroyApp() is invoked.

From: http://developers.sun.com/mobility/m...ticles/models/

[grahamhughes]

I'm familiar with the specification. Nowhere does it require an implementation to call pauseApp() ever. Nor is there any requirement for specific processing in the case of an incoming call, SMS, or other external event causing the application to be pushed into the background.

Are you using notifyPaused() and resumeRequest() to switch your MIDlet back and forth?

Graham.