Friday, February 6, 2009

There's a Party in my Blackberry, No One Else is Invited

I've had a Blackberry Bold for a while now. I haven't blogged about it because the OS it was launched with became famous for instability. I upgraded twice looking for a stable platform. I'm also a developer for Blackberries, and there is nothing that can take the confidence away as fast as bricking your own Blackberry with the latest version of your own software.

I managed to beat down all the bugs except a pernicious and difficult to isolate one. Occasionally I would install a new version of my precious project. A reboot would be required, fine, no surprise. But, partway through the boot process it would halt at the dreaded white screen with tiny writing "App Err 200" and a "RESET" button. Some times resetting would result in a clean boot, often and more frequently as time passed, not. Finally I'd have to give up and wipe the device and re-install the OS. A good learning experience but once was enough. I eventually tried a removing the IT Policy. That worked by not really better than a re-install.

The event log was clear that the Application Manager (the program that displays the home screen and lets you launch other applications) detected too many processes, and just stops. I understand that a small device has limited resources, but stopping is perhaps a little drastic. Sometimes removing my, or other applications would result in a clean boot, often not. Frustration writ large.

Finding information on Blackberry errors is always a challenge, but when I found this knowledge base article I was a bit embarrassed. It claims to have been around since May 2006, I should have found it sooner. So Blackberries can only run 48 concurrent processes. That should be plenty no? Well apparently not. There are a lot of processes that run all the time in the background to do useful things. Over the past few months lots of user applications have been released for the Blackberry; Facebook, Flicker, Twitter, MySpace and a whole drawer full from Google. I don't run all of those, but some. Many need, or can be configured to run at startup. Most of my own applications also have to run at startup. So a routine reboot can turn into a process storm.

If RIM wants to keep pushing the social networking applications to broaden the appeal of the Blackberry beyond the boardroom they will have to come up with a more robust way of dealing with this situation. In the mean time their advice for developers building multiple auto starting applications is to have one seek out and run the others. And it works.

Yippie! Stability, it's a good thing.

No comments: