[vinmontRD]

Originally Posted by ubizmo

No, I am able to edit profiles. That is very weird.

Ubizmo

Battery pull doesn't help. Wondering if I need to do a wipe and reinstall, although that has NEVER been necessary before, as all OS loads I've done have worked, completely replacing what was there before.

This really is annoying...

[vinmontRD]

Before resorting to a full wipe and reinstall, I decided to get a bit smarter about this and use the info readily available to me (after all, I've been developing software for more than half my life...should have been my first approach!).

I have QuickLaunch installed, and found that you can specify the Blackberry EventLog as an application for it to launch, making it VERY easy to try an action, then quickly switch to the eventlog to see what the Blackberry OS thought of this.

So:

I brought up the event log via quicklaunch and wiped the log. Then I attempted to edit the active profile (click profile icon, select advanced, click on active profile) -- and then immediately took another look at the event log. Lo and behold, the logged exception showed that there was a missing Facebook resource!

I checked options/advanced/applications, and found that both versions of Facebook were somehow installed on my 8900 at the same time -- both 1.5 and 1.6. I deleted 1.5 and rebooted the 8900. Still no joy. So -- I deleted 1.6 and rebooted....and...Success! I can now edit my profiles again.

On the theory that the combo of 1.5 and 1.6 somehow indicated a compromised install before, after making sure that there were no traces of 1.5 left on my 8900, I used App World to reinstall 1.6, and happily enough, I can still edit profiles properly.

Best guess now is that version 1.5 was still partially installed, and was still hooking the OS, indicating that there should be a link between the current profile and various Facebook resources (since profile options can respond to FB events as well as other events). But...the fact that 1.5 was only a partial install meant that a few files were missing, in my case these included the resource files needed to link FB to the OS's profile manager.

Suggestion for anyone who ever runs into weird behavior that seems inexplicable: use the EventLog -- it's an incredibly quick way to get some clues regarding which application is failing even when there are no visible signs in the user interface of your blackberry. Next best thing to a debugger if your not a developer...

[mubarik]

Nice info vinmontRD, thanks.

[ubizmo]

I have to say that this OS is quite prone to resets, especially when the browser is zoomed in and I'm attempting to scroll around; or if the browser is zoomed in and an email arrives. It doesn't always reset under these conditions, but it happens often enough for me to spot the pattern. I guess it's a moot point, since development is now all about the 5.x OS, but I just thought I'd mention it.

Ubizmo

[nickds]

Worth downgrading from 5.0 ?

[vinmontRD]

I had installed the various 4.6.1.x releases and got up to 4.6.1.250 and was sitting at that for a while. Then when 5.0.0.100 was leaked, I installed it, and had to give up in just 2 or 3 days -- way too buggy for me, so I reverted to 4.6.1.250. Then, when 5.0.0.130 was leaked, I loaded that, and used it for a week. I *really* liked the features, but the errors got to be more and more annoying, such as:
-- severe memory leaks (25MB in 24 hours)
-- "delete prior" would stop working within 24 to 36 hours after a battery pull
-- delete multiple (highlighting a few and hitting delete) would lock up the screen
-- missed incoming calls --> straight to voicemail even when I had a signal
-- inconsistent missed call indicator
-- inconsistent message waiting indicator
-- no spontaneous restarts, but I HAD to reboot the phone at least 2 or 3 times a day
-- UMA unusable for voice calls -- fluctuate in/out -- terrible despite all fixes

Despite loving the features in 5.0.0.130, it was just way too buggy to use on a phone that I need for business as well as personal use. So I reverted to 4.6.1.250 again.

250 is very stable, and about 95% of what I do on it works very well. I still find UMA less than stellar, as it occasionally drops a call for no apparent reason. But when connected, it's great. In general, 250 is very solid and works well. My primary complaint is simply that it doesn't have the features that 5.x.x.x has.

Looking forward to 5.0.0.140...