AVK_END Key Handle Issues for CDM-8900 and CDM-8910 | developer.brewmp.com AVK_END Key Handle Issues for CDM-8900 and CDM-8910 | developer.brewmp.com

Developer

AVK_END Key Handle Issues for CDM-8900 and CDM-8910

Forums:

Hi,
NSTL reported the following problem during sending SMS from CDM-8900 and CDM-8910 . If user exit from application by pressing the END key immediately after sending an SMS message, then the handset power cycles after the user is given the following error message, “Please wait, user data is being restore…. [7]”.This problem is not occurring on other devices like LGVX6000.

Please help me out form the above issue :)

Thanx's
webdev

LG 6000 is quite robust handset..........so udont consider it even though ur app run well on it......always try app on other phones.........
can u give some snippet of sms sending
its sure that ur doing some illegal operation while ending ur application........
check ur freeapp function..............

LG 6000 is quite robust handset..........so udont consider it even though ur app run well on it......always try app on other phones.........
can u give some snippet of sms sending
its sure that ur doing some illegal operation while ending ur application........
check ur freeapp function..............

Hello ,
I have tried using the SMSNotify route. But the SMSNotify callback isn't being invoked at all on the 8910/8900 phones.
-Webdev

Hello ,
I have tried using the SMSNotify route. But the SMSNotify callback isn't being invoked at all on the 8910/8900 phones.
-Webdev

Hi Aiyengar,
In response to your post quoted below:
aiyengar wrote:ITAPI_SendSMS() is an asynchronous function.
You are releasing ITAPI even before your SMSStatusNotifiy function is being called.
I am having a similar problem where I am being failed by NSTL on only one phone (the Samsung A670).
I don't release my ITAPI until termination time, so I generally have no problems. But in the case where the user closes the phone or hits the "hangup" button while the callback is pending, the Samsung A670 reboots. All other phones are okay (some 20+ devices made it through NSTL testing just fine).
Is there any way to unregister for this callback at shutdown time so that we don't crash? I don't see such a mechanism in the API.
Alternately can I spin wait or something lame like that in the EVT_APP_STOP callback, waiting for the callback to happen? Is it even possible for the callback to happen while my main thread is executing?
I'd love a solution to this problem that doesn't involve ignoring the callback in the ITAPI_SendSMS() function since it works nicely on all other devices.
Is there a way to get an exception for this device in NSTL testing, since the average user isn't going to hang up immediately while my screen is telling them that the message is being sent. Or at least he/she won't do it twice once they realize that it reboots their phone.
Thanks,
Paul

Hi Aiyengar,
In response to your post quoted below:
aiyengar wrote:ITAPI_SendSMS() is an asynchronous function.
You are releasing ITAPI even before your SMSStatusNotifiy function is being called.
I am having a similar problem where I am being failed by NSTL on only one phone (the Samsung A670).
I don't release my ITAPI until termination time, so I generally have no problems. But in the case where the user closes the phone or hits the "hangup" button while the callback is pending, the Samsung A670 reboots. All other phones are okay (some 20+ devices made it through NSTL testing just fine).
Is there any way to unregister for this callback at shutdown time so that we don't crash? I don't see such a mechanism in the API.
Alternately can I spin wait or something lame like that in the EVT_APP_STOP callback, waiting for the callback to happen? Is it even possible for the callback to happen while my main thread is executing?
I'd love a solution to this problem that doesn't involve ignoring the callback in the ITAPI_SendSMS() function since it works nicely on all other devices.
Is there a way to get an exception for this device in NSTL testing, since the average user isn't going to hang up immediately while my screen is telling them that the message is being sent. Or at least he/she won't do it twice once they realize that it reboots their phone.
Thanks,
Paul

Im getting a similar issue but it relates to IWEB. If i hit the end key while a download is going on, the handset reboots. The first time it just gave me that weird error, wait while cleaning user data stuff. In any other situation, the end key works like a charm.
Saludos,

Im getting a similar issue but it relates to IWEB. If i hit the end key while a download is going on, the handset reboots. The first time it just gave me that weird error, wait while cleaning user data stuff. In any other situation, the end key works like a charm.
Saludos,

This is a published known issue for the Samsung A670, so you just need to send NSTL an email with the known issue pasted in. For future submissions,also include this known issue in the App Spec. The same goes for the Audiovox 8900 / 8910, although it is not published as a known issue. QIS support has acknowledged that this is an OEM handset issue however, so I also included this information in the App Spec and NSTL passed it.

This is a published known issue for the Samsung A670, so you just need to send NSTL an email with the known issue pasted in. For future submissions,also include this known issue in the App Spec. The same goes for the Audiovox 8900 / 8910, although it is not published as a known issue. QIS support has acknowledged that this is an OEM handset issue however, so I also included this information in the App Spec and NSTL passed it.