Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

As you know, BREW App starting is a async process, that is, after IShell_StartApplet be called, the new App will not immediately starting and became top-visable. actually, after several BREW Loops, it then go to top-visable.

And BREW only will put the new App in App stack and make it top visable after the App return TRUE for EVT_App_Start. before this point, any Key event also be sending to the current running App(current Top visable app).

Then Issue arised. pls refer to the below case:

1. App A is now top-visable, and now if Press Down key, will start App B from App A context.

2. press Down key the first time, then quickly press down key several times. If the Key press speed is enough fast, or the handset's performance is enough slow, then maybe happened as below:

down key press first time: App A call IShell_StartApplet, and the App B is starting Async.

down key press second time: if now App B still in Starting, and not be put in App stack, Then the event be sent to App A, and App A start App B again, And BREW try to create the second APP B instance(coz App B not in stack).

obviously, above case is not expected. And now Do happened in our handset, maye the handset's performance is slow.

Then, How to avoid this issue happen?? (from App layer or from OEM layer all is OK, actually i am OEM engineer) How to dis-allow key sending when the App is starting.

Thanks a lot

Please open an SR through qishelp.qualcomm.com so OEM Engineering can see your request. :)

Please open an SR through qishelp.qualcomm.com so OEM Engineering can see your request. :)

before I have submitt such-like question to QIS, even to QCT. But can not got answer, or can not got satisfied answer.
Actually, I found this forum is so efficient, and many my question is got resolved in this forum, not by SR.
So, I always like to ask questions in this Forum, instead of SR.
PS: this forum is so wonderful, But why not open a seperate forum, or album for OEM? I am expecting for it all the time.
Anyway: could you continue help answer this question in this thread??
Thanks a lot

before I have submitt such-like question to QIS, even to QCT. But can not got answer, or can not got satisfied answer.
Actually, I found this forum is so efficient, and many my question is got resolved in this forum, not by SR.
So, I always like to ask questions in this Forum, instead of SR.
PS: this forum is so wonderful, But why not open a seperate forum, or album for OEM? I am expecting for it all the time.
Anyway: could you continue help answer this question in this thread??
Thanks a lot

I'm not in OEM Engineering. ;)
I guess you could prevent key events from being sent to BREW between OEMNTF_APP_STARTING (OEMAS_START_TO_TOPVISIBLE) and OEMNTF_APP_CTXT_NEW, but I really have no clue if that would break anything. You should really check with OEM Engineering so they can see if there needs to be a change to BREW to accomodate your use case.

I'm not in OEM Engineering. ;)
I guess you could prevent key events from being sent to BREW between OEMNTF_APP_STARTING (OEMAS_START_TO_TOPVISIBLE) and OEMNTF_APP_CTXT_NEW, but I really have no clue if that would break anything. You should really check with OEM Engineering so they can see if there needs to be a change to BREW to accomodate your use case.