08-14-2010 02:40 AM
A few days ago I was running the VZW official .713 OS. Then, I think I installed the latest BBM. After about 12 hours of that, I started experiencing random crashes triggered by actions (not particular actions). I add a contact, it crashes. I boot back up and add again, it doesn't crash - something like that with various other actions like me locking the phone using the left lock button, or snapping a picture, etc.
I didn't attribute this to BBM and so figured to hell with the official OS and installed a hybrid (Yes, I'm aware that it's not a supported OS bla bla, but it started with the official .713 so there is merit to this). And upgraded to the new BBM. Installed apps, etc.
Battery was draining by 2-5% every 30-45 minutes. Crashes were happening and I wouldn't know till I had to use the phone again, at which point it starts the boot process.
I uninstalled the latest BBM and downgraded to the previous stable 188.8.131.52 and it is still going on.
I'm running out of options here.
I checked the event log for the time it crashed and encountered only one fatal error:
Name: IllegalArgumentException GUID: 9c3cd62e3320b498 Time: Aug 14, 2010 12:35:28 No detail message net_rim_cldc-10(4C010A3F) RadioInfo getNetworkId 0x768E net_rim_cldc-10(4C010A3F) RadioInfo getMCC 0x7836 net_rim_bb_autotz(4C011090) AutoTimeZone networkTimeUpdated 0x97 net_rim_cldc-23(4C010A3F) Events dispatchRealtimeClockEvent 0x3A8A net_rim_cldc-8(4C010A3F) Application <private> 0x2385 net_rim_cldc-8(4C010A3F) Application processNextMessage 0x1AEF net_rim_cldc-8(4C010A3F) Application enterEventDispatcher 0x1A2C net_rim_services_impl(4C010AC2) ServiceStartup <private> 0x465B net_rim_services_impl(4C010AC2) ServiceStartup main 0x4598
Any help would be appreciated as I don't know what else to do except for installing the old BBM and no other applications. In which case, no point of the phone. I've been using the phone for the past 2 months with no problems..
If someone wants me to email this to someone at RIM, that's fine too as I don't know how else to go to them.
08-15-2010 04:32 PM
I'm having the same problem. It all started after the latest update (i have not installed another OS though). Unit will randomly reset, sometimes multiple times. Also, battery will go from 75% to empty, immediately. It's almost like it's emptying when 2 things happen at once (on phone and email is recieved for example). It's a nightmare. Or, perhaps battery is fried?
I'm WAY open to suggestions. As it is the phone is severly not dependable, cannot complete a phone call or email or anything without it restarting...
08-15-2010 09:18 PM
I don't think it's about a faulty battery - cuz I've seen lotsa threads where new batteries didn't help. Also, it simply doesn't make sense that a battery suddenly starts exhibiting dying behavior after upgrading BBM.
Mine is not as bad as yours in terms of rebooting after every action, but annoying as hell nonetheless. I downgraded to 184.108.40.2067 about 7 hours ago. Let's see how it goes. All I did is restore my data backup, but other than that no applications. Not even BBM.
Will be patiently waiting for some RIM official to look at my trace and recommend something.
08-15-2010 10:29 PM
Ok, I've tried 220.127.116.113, .607 and a hybrid based off of .713.
Been using .713 since I got the phone a couple months ago, and no problems. Installed latest BBM, and I started getting:
08-17-2010 11:33 PM
Been a few days now and the SLA on this website states 24 hours BlackBerry Tech response time. No one helped.
Fortunately for me, mikelpn from bbhybrids.net was kind enough to tell me it sounds like a corrupt database. I've been evaluating which database is bad for the past few days, and things are looking better.
amorgan: I would suggest you wiping, and installing a new OS. After that, do not restore any of your data backups. Instead, wait 6-24 hrs to see if you experience any crashes, or battery problems. If not, restore your address book. Reboot. If you see the battery is shaving off 10-25% battery after the batt pull, your address book is at fault. Repeat this procedure with the important backups of yours that you absolutely need.
Having said this I would still like a blackberry tech to answer me.