04-19-2011 02:45 PM
My GF's phone is giving us the message "Uncaught exception: index 16 >= 16" after we do a battery pull. She is no longer able to send or receive txt's. This phone is just over a year old and now its pretty much useless to her. I have searched the forums and have had no luck finding a solution. What can we do to fix this phone?
Former BB owner and now current Android owner.
04-19-2011 02:53 PM
If you get this error as soon as you open your messaging folder. You can browse to the last contact you know who sent you a sms and delete that sms from your contact list. Once you remove that SMS the error should be waived.
If not it is kind of a guessing game to find the correct SMS causing the error but once you've done so you will be rid of it.
If not the last solution is to Backup the BlackBerry, Master Wipe the BlackBerry and finally restore the BlackBerry.
Hope that helps,
08-03-2011 08:21 AM
Hi I a have problem with Blackberry curve 8520:
When I reboot my mobile the following message appears "Uncaught Exception:index 16>=16" after that a clear screen appears with "App Error 523 Reset" when I reset the mobile the same scenario happens. Please help me to find a solution
01-07-2013 04:54 AM
Hi even I am having the same problem with Blackberry curve 8520:
When I reboot my mobile the following message appears "Uncaught Exception:index 16>=16" after that a clear screen appears with "App Error 523 Reset" when I reset the mobile the same scenario happens. Please help me to find a solution too..
01-07-2013 11:02 AM
Hi and Welcome to the Community!
Here is a KB that discusses the 523 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.
Regarding the uncaught exception error, 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!