We’ve received word from one of our sources that Research In Motion is already working on a refresh for the BlackBerry Bold 9900. The reason for the refresh isn’t entirely clear just yet. However, our source tells us that the Bold 9900 refresh will only be for internal components and the form factor shouldn’t change.
Prior to the Bold 9900′s launch, we exclusively told you the reason the Bold 9900 was delayed was due to faulty circuit boards. Perhaps RIM is addressing this issue as well as adding auto-focus to the camera? Or, maybe the refresh is for an AT&T pushed change? That’s all we know for now. Keep it locked to N4BB while we gain more information as this story develops!
Let us know in the comments what you think RIM could be ‘refreshing’. What internal components are they adding or fixing? What could they possibly be changing in an already near perfect device? Sound off N4BB community.
You may also like:
Tags: BlackBerry 9900, Bold 9900, Research In Motion
About the Author
qnx bold
The Camera is my guess.
QNX BOLD BE SEXY
AT&T compatibility issue, I’d guess
))
hardware-connected battery life increase, I’d prefer
maybe for a better battery and why not autofocus !!!!
but if this info is real, i will be so disapointed and verry angry toward RIM, because i just get my 9900.
they should have thought about that before.
@DavidBensimon
is there a cdma version? a bit soon for a refresh but if there’s plan to bring forward a 9900 QNX bold, I’d be up for that considering all I’ve heard is a touch only device.
oops, the 9930
but yeah it could very be something specific on the AT&T network. something to do with NFC? and while they are at it, a better battery and camera wouldn’t go astray.
Oooo… 9900S!
I have had two instances of JVM Error 517, which is listed as a hardware error. I had to wipe the phone then reinstall. I made them send a new phone the first time. It happened again day before yesterday. I just wiped and reinstalled and am going to call it in. I suspect this may be part of the reason. Found that others have had the same problem, although luckily it isn’t rampant.
Hopefully it will solve the “JVM 517″ error.
Very interesting. Thanks a lot for sharing this. I really like your blog.