There had been some discussion on this topic in the past, but that was a couple of years ago and I didn't quite get my question answered, so I thought I'd post a new thread. What I'm looking for is an absolute statement by Qualcomm as to exactly which events are guaranteed to be posted to background applications when a handset is being powered down. Other threads indicated that EVT_APP_TERMINATE will be posted in every case. We coded our app accordingly, but are now finding that that event is not being posted on certain handsets (some Kyocera, INQ1 etc). Conversations with the OEMs make me think that posting EVT_APP_TERMINATE is optional. What I'd like to know is if that's true, then what events *must* be posted by the platform? Thanks and apologies if this thread is viewed as a duplicate.

while powering down your background App should get events as below:

EVT_EXIT
EVT_APP_STOP
(if your App refuses to close on EVT_APP_STOP, then a forceful close event is sent)-
EVT_APP_TERMINATE

thanks.

EVT_APP_TERMINATE forcefully terminates apps. Eg. when app is dead.
EVT_EXIT is sent to any loaded apps when BREW terminates.

Just for your reference:
Terminating a background application poses a greater challenge. As they are unable to receive key events directly, it is necessary for
the background application to either terminate itself upon successful completion of a designated task or listen to events generated by a
separate façade application. The application may be terminated through three methods:
1. Another application sends an event (with eCode >= EVT_USER) signaling the background application to terminate through
ISHELL_SendEvent() or ISHELL_PostEvent()
2. Background application terminates itself with ISHELL_CloseApplet() upon completion of a specific task. Note that
according to the API references, calling ISHELL_CloseApplet(pIShell, TRUE) from the active application will
close all other executing applications and return to the idle screen; however, when called by the active application this
operation will not affect other programs not in the application stack
3. Background application activates itself by calling ISHELL_StartApplet(), at which point it may receive user events

__________________
Atul