Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
09-13-2009 11:12 PM
09-13-2009 11:18 PM
This message means that your application is doing something in the event thread that it should not be doing. This is not a cosmetic issue - you need to fix the code.
Some common causes:
* performing blocking IO, like HTTP or sockets
* getting a GPS fix
* performing time-consuming operations like lengthy calculations in a loop
09-13-2009 11:45 PM - edited 09-13-2009 11:47 PM
In most case it works fine unless leave it there for long without user interaction, like over the night. So wonder if there any way to chagne the error message from device settings?
09-14-2009 01:00 AM
If you are getting that error message, then you really need to track down what is causing your application to not respond.. The fact that it doesn't happen to you very frequently is irrelevant, because if you deploy the code to many people it will happen more and more frequently and annoy the people who are using your application, you really are serving yourself by tracking down the root cause instead of trying to hide the problem.
Irrespective of the fact that your code has a pretty serious flaw that should be addressed, there is no way to change that particular error message or catch the exception and handle it because that message is by definition only displayed when your application is NOT responding to system and hence would not respond to any notification that the message is about to be displayed.
RegDoug has provided some pretty good common causes of the issue, the solution is to use a thread to do anything that MIGHT take some time.. Any expensive computations should not be executed on the event thread.
09-14-2009 07:50 AM