Tizen Developers

I would suggest you to place log print in app life cycle callbacks.

That would detect which state your application enters, when another app is re-activated from Recent Apps.

 

static void
app_pause(void *data)
{
    dlog_print(DLOG_INFO, LOG_TAG, "app_pause called");

}

static void
app_resume(void *data)
{
	dlog_print(DLOG_INFO, LOG_TAG, "app_resume called");

}

static void
app_terminate(void *data)
{
	dlog_print(DLOG_INFO, LOG_TAG, "app_terminate called");

}

 

Related documentation:

https://developer.tizen.org/development/guides/native-application/application-management/applications#state_change

Thanks for the suggestion. Actually I did. My app changes to Paused state when return to home. However, the callback will not be triggered anymore if an app (e.g. calculator) is resumed from Recent App. However, if I run calculator directly, the callback will be triggered and app_resume() is called as well.

Further tested.

 

1. Run my app with ecore timer added

2. Return to home; my app is PAUSED but timer still run

3. Run an app, e.g. calculator, and return to home; timer still run

4. Run another app, e.g. media browser, and return to home; timer STOP running

 

If reactivate my app from Recent Apps, it is RESUMED; timer resumes running.

:(