04-15-2013 10:05 AM
Hi, every time I turn my phone (blackberry curve 8520) on the home screen comes up with a message "uncaught exception index 3>=3". It won't allow my to click on any options, and when I press ok nothing happens, but after a few seconds a white screen comes up with the message "app error 523 reset". I have tried a soft and hard reboot and have tried linking it up to my mac but nothing has changed. Please please help me!
04-15-2013 06:49 PM
Hi and Welcome to the Community!!
"uncaught exception index 3>=3".
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.
"app error 523 reset".
Here is a KB that discusses that error:
Hopefully it contains something useful! There also are multiple existing threads on this site that discuss that exact error...your review of those might prove useful, and a search of this site, using the error message, error code, or symptom, should reveal all applicable existing threads to you.
Good luck and let us know!