Just a short time ago, we heard about RIM’s upcoming BlackBerry 7 lineup that will be storming onto shelves in the near future. As exciting as those devices are, we’re still waiting on the QNX-powered phones that we know RIM is going to be delivering in the future. Well, according to BGR, RIM’s first QNX-based handset will be dubbed the BlackBerry Colt.
That name, of course, is a codename so it likely won’t be called that when it hits shelves. Speaking of shelves, RIM apparently has a target release date of Q1 2012 for this thing which means that you’re only going to be able to buy BlackBerry 7-powered devices in 2011. That of course all depends on how testing goes so it’s possible that we might see it slip even further than that if difficulties are encountered.
Details are murky but the report states that currently, the device only sports a single-core processor. As you know, RIM has yet to release a phone with a dual-core processor leaving it in the dust of its competitors. It’s still possible that the BlackBerry Colt could arrive with a dual-core chip but right now, it’s operating with a single-core.
Pretty irritating considering quad-core processors are on the way.
RIM’s first QNX phone will also apparently launch without support for current BlackBerry Enterprise Servers. The phone will instead support Microsoft ActiveSync out of the box.The reason? If you recall, RIM’s BlackBerry PlayBook tablet launched without BlackBerry Enterprise Server support and RIM has had to rewrite code for it to work.That has not been easy and it seems that RIM is working on a QNX-specific BlackBerry Enterprise Server.
I have a feeling it’s going to be hard to wait until 2012 for this phone.
<!– 300×600 SIDEBAR –>
4 Reasons Not to Install iOS 13.2.3 & 11 Reasons You Should
The iOS 13.2.3 update is a small maintenance release, but it could have a huge impact on your iPhone’s performance. While some...
MacBook Pro 16 Keyboard: 5 Things You Need to Know
Apple finally fixed the MacBook Pro keyboard with the 2019 MacBook Pro 16-inch model. This is what you need to...