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.
03-01-2013 03:56 AM
03-01-2013 10:32 AM
Hi and Welcome to the Community!!
There's pretty much no diagnosing those -- they are the equivalent of the random errors in Windows for which tracing the root cause is fruitless. Basically, these are the last out in the programming code -- some event occurred for which there is no handler in the code. The fix is a code update that handles the event...but, again, knowing what the event is is pretty much impossible. So, there are a few things to try:
Sometimes, the code simply becomes corrupt and needs to be refreshed -- just like a reboot:
If it won't boot up cleanly, then you may need to try Safe Mode:
There might be an updated code set from the carrier -- check them via this portal:
The toughest possible cause is a badly behaving app. To find it, there are a couple of options. One is to see if you can read the log file:
Go to the home screen. Hold down the "alt" key and type 'lglg'. (You will not see anything while you type).This will bring up the log file. Scroll down (probably many pages) untill you see a line that says 'uncaught execption'. Click on this line. The name of the app will be in the info. Alternative methods for bringing up the logs are in this KB:
The other method is to remove apps one at a time, waiting a while in between (I usually recommend a week), until the problem ceases...thereby discovering the offending app. Still another method is to reload the BB OS cleanly, leaving some time between adding other apps onto the BB so as to be able to determine exactly which one is the cause.
Good luck and let us know!
03-03-2013 07:52 PM
03-04-2013 09:14 AM
Well I found something that was flagged as an error, but they are titled ' StringIndexOutOfBoundsException ' and ' Name: System
GUID: 97c9f5f641d25e5f ' the second is timed at...well...December 31st..1969.. what are those and how do I stop them?
"Found"? So is my guess that you found these in the error log correct? In any event, I have no way to know what that means. If it means nothing to you, then it means even less to me since I have no idea what you have installed to your BB. What you are looking for in the logs is some way to identify the app that is generating the errors. If you can't find it, then you have to try the other methods I gave you.