Search


Subscribe to AFM


Subscribe to AllFinancialMatters
by Email

All Financial Matters

Promote Your Page Too

The American's Creed

Site Sponsors

Books I Recommend


AFM in the Media


Money Magazine May 2008

Real Simple March 2008

Blogroll (Daily Reads)

« | Main | »

Annoying BlackBerry Torch Calendar Crash (‘Uncaught Exception’)

By JLP | October 25, 2010

I upgraded to the BlackBerry Torch 9800 on Friday. For the most part, I love this phone (except for the fact that BlackBerry decided not to supply a belt holster with the phone). It’s definitely a better phone than the Bold 9000 I was using. It has one very annoying glitch, though. When I open the calendar, if I click on the icon to view the month, the phone freezes up. The only way I can get it unfreeze is to power it down and back up again. Then, as soon as it’s powered up, I get the following error message:

Uncaught exception: Application net_rim_bb_calendar_app(285) is not responding; process terminated

What’s annoying is I’m not the only one experiencing this issue. This phone has been on the market for around two months and this issue still isn’t resolved. What’s up with that? I even updated my software but the glitch is still there. I searched BlackBerry’s support page and found nothing.

I guess I’ll have to head over to the AT&T store.

Topics: Miscellaneous | 4 Comments »


4 Responses to “Annoying BlackBerry Torch Calendar Crash (‘Uncaught Exception’)”

  1. BG Says:
    October 25th, 2010 at 11:52 am

    Problems like that with a new phone? If you can do it for free, switch the device for a different model (don’t get a new identical unit).

    Life is too short to deal with stuff like this.

  2. Bob M Says:
    October 25th, 2010 at 12:23 pm

    Check this out….

    http://www.blackberryforums.com/general-legacy-device-discussion/89218-uncaught-exception-application-net_rim_bb_calendar_app-563-error.html

  3. BG Says:
    October 25th, 2010 at 1:01 pm

    #2 Bob) That thread is from 2007…

  4. RR Says:
    January 2nd, 2011 at 12:08 am

    Any luck/updates on this issue? I too have just encountered the exact same problem.

Comments