AT&T yanks BlackBerry Bold visual voicemail software update
By Nilay Patel 
posted Sep 5th 2009 4:20PM
posted Sep 5th 2009 4:20PM
Update: AT&T just sent us their official word on the matter -- and they also told us it has nothing to do with MMS or 850. Check it out after the break.
--
This week, AT&T and RIM discovered an issue in the most recent software update for the BlackBerry Bold, only affecting a small number of customers in a handful of markets. The issue may create call performance problems that can be corrected. We encourage any customer who believes they are experiencing this problem after installing the most recent update to call customer care for help.
We are working to fix this problem as soon as possible. In the meantime, if a customer encounters issues with the software, they should contact customer care.
Customers who have the b508 Bold Maintenance Release who already have Visual Voicemail can continue to enjoy its benefits. Other interested customers will be able to get Visual Voicemail once the new software build becomes available.
don't you think this would be on RIM's shoulders...not at&t? i mean at&t isn't the one that makes the software...
I'm running the rogers .282 build with VVM on my AT&T Bold. Didn't bother to upgrade to the latest AT&T release.
The Rogers .282 works great
@ William,
RIM's official position on sporadic problems occurring on some, but not all, BB Bolds since their launch last year (random power cycles, vague java exception errors upon boot up, etc...) is that it is the carrier's fault. Per RIM, when they released the OS to the carriers so that it could be tweaked to each of their networks, the OS did not have these flaws. More than likely, this will also follow suit unless RIM/AT&T has identified a problem with something that was added to the newest build. However, given the explanation by AT&T of compatibility issues with network enhancements, I doubt that will be the case.
Thankfully, the above instances are not harmful. The device power cycling itself is only a frustration. The multiple java exception errors (and resultant inaccessibility of media card, icons missing from the home screen, etc...) seems to be caused by the OS not loading itself in the proper sequence, and can be corrected by simply taking the battery out for a couple seconds and reinserting it. There have not been any reports of lingering issues from either problem. Hopefully RIM/AT&T will get these problems resolved in a future OS build (5.0, maybe??).
I upgraded and now my pictures load very annoying slowly.