Timer callback stops all of a sudden in LG8000 | developer.brewmp.com Timer callback stops all of a sudden in LG8000 | developer.brewmp.com

Developer

Timer callback stops all of a sudden in LG8000

Forums:

I am not sure if anyone experienced the following problem.

My application timer callback suddenly stops after running my application for prolonged period of time (it could be after 3/4 hours, 5/6 hours or even after 12/13 hours). After certain number of hours all of a sudden BREW stops giving callback to my application. I have started seeing this problem in LG8000. I have certainly tried with different techniques, like ensuring that allowing BREW system gets at least 10+ milliseconds before next callback.

Initially I was using ISHELL_SetTimer when I have observed this problem. Then I have changed timer callback to ISHELL_SetTimerEx. After calling ISHELL_SetTimerEx I started to printout the "pfnCancel" pointer of AEECallback structure (that's what CALLBACK_IsQueued function does) and it seems to be fine.

Kind of strange behavior. By the way, handset does not hang. I can terminate the application using END key. I have started seeing this problem in LG8000.

wait 10-20 seconds, will the timer resume? if so, I think this is because the timer callback function is over work, however, I don't know how to prevent this from happening.

wait 10-20 seconds, will the timer resume? if so, I think this is because the timer callback function is over work, however, I don't know how to prevent this from happening.

I even tried with 30/40 milisecond timer interval, still same thing happens. What is interesting though is that, after timer stops my application still receives key events.
For testing purpose, I have hooked up "*" key event handler to stop the unresponsive timer, reinitialize AEECallback and call ISHELL_SetTimerEx, and start the timer. So in logger when I see that my application timer stops responding, if I press "*" key, application timer starts working again.

I even tried with 30/40 milisecond timer interval, still same thing happens. What is interesting though is that, after timer stops my application still receives key events.
For testing purpose, I have hooked up "*" key event handler to stop the unresponsive timer, reinitialize AEECallback and call ISHELL_SetTimerEx, and start the timer. So in logger when I see that my application timer stops responding, if I press "*" key, application timer starts working again.

Interesting! ISHELL_SetTimer or ISHELL_SetTimerEx, both displays the same problem.

Interesting! ISHELL_SetTimer or ISHELL_SetTimerEx, both displays the same problem.

Reuben,
Did you ever get a solution to this problem?
I'm experiencing a similar problem on the vx8000 - it is either IMedia releated or the tick has gone AWOL. I'd like to rule out the timer if possible.

Reuben,
Did you ever get a solution to this problem?
I'm experiencing a similar problem on the vx8000 - it is either IMedia releated or the tick has gone AWOL. I'd like to rule out the timer if possible.

Well... I was convinced that it was system problem. I have used the work around by resetting the timer and that worked.

Well... I was convinced that it was system problem. I have used the work around by resetting the timer and that worked.

Hmmm, the testers say the problem has now gone away - i modified the timer functions and the IMEDIA functions so i've no idea what fixed it.
There isnt anything odd about calling a ISHELL_SetTimer at the end of a function is there? Have now moved that to the start of the 'tick' function.

Hmmm, the testers say the problem has now gone away - i modified the timer functions and the IMEDIA functions so i've no idea what fixed it.
There isnt anything odd about calling a ISHELL_SetTimer at the end of a function is there? Have now moved that to the start of the 'tick' function.

This is due to LG's buggy implemtation of BREW timer. LG8000 has too many system bugs.

This is due to LG's buggy implemtation of BREW timer. LG8000 has too many system bugs.

i've actually started experiencing this also on the LG8000. haven't seen it on the 8100 though. ruben, if you don't mind my asking, what do you mean by resetting the timer?

i've actually started experiencing this also on the LG8000. haven't seen it on the 8100 though. ruben, if you don't mind my asking, what do you mean by resetting the timer?

ahhh maybe cancel the timer before setting it again? i'll try that out

ahhh maybe cancel the timer before setting it again? i'll try that out