Quote:
Originally Posted by pyro451
Can you share what the problem was, and what you figured out about it?
|
Doh, I guess that'd help, sorry about that. Anyway, I posted about it over on the .297 thread
here. But to recap, I was receiving this message:
Quote:
|
Uncaught Exception: java.lang.IllegalStateException
|
Whenever I rebooted the phone (soft or with a battery pull, I didn't matter) and eventually found out it also occurred if I ever locked the device and let it sit for more than a few minutes. Plus, the longer I let it sit after a reboot or device lock, the more times the pop-up error would occur, requiring me to click through multiple "OK" messages - overnight, it would be 40 or 50 of them, very annoying.
After uninstalling what I thought was every single application that could be the culprit, I wiped the device and reinstalled the OS and the problem went away, only to recur after activating on our BES, but before installing any other applications. At that point (with .297) and after several days of trying things, I just gave up and went back to .282 (where I also had visual voicemail already working). I had just really liked .297 otherwise because it's memory footprint was much smaller, but the error message was just too annoying. One note, there were error messages in the device event log that showed the error occurring around the time of browser push activity, but I still couldn't find the problem.
So, when .301 came out, I gave it a shot to see if the problem went away, but it was still there after automatically reactivating on BES. However, I remember that our BES administrator had set up an "Emergency Contact List" for our team that gets pushed to our devices periodically and is cached and accessible via an icon. I then noticed that after a reboot, the icon for it wouldn't be there until I left the device unlocked for a period of time.
Long story short, it turns out to be some issue between "Content Protection" (a.k.a. device encryption) and browser push. After .297, if you have Content Protection turned on (we have it configured on our BES) and are also using Browser Push functionality, it fails and throws that error every time a push is attempted (don't recall the frequency, think it's every 15 minutes) whenever the device is in a locked state (following a reboot or after sitting idle for a period of time). We need to open a case with RIM about it and I'm not certain that it's all Browser Push or just what we're doing with our Emergency Contact List. But I verified the problem by terminating the net_rim_bb_browser_push process in the JVM processes using the engineering screens and the problem didn't recur following a device lock. Of course, it did come back after a device restart. So I went into Options --> Advanced Options --> Browser Push and just turned it off that way, and voila, the problem was gone.
you're a star mate x
