BlackBerry Torch 2 Features 1.2GHz Processor

So you’ve heard all about the BlackBerry Dakota and while it’s a nice phone, it’s not quite what you’ve been hoping for. You see, you quite liked the BlackBerry Torch slider that RIM just recently released; you just thought it fell short in the specs department.

Well, perhaps this tidbit from BGR will keep you on the Torch-wagon for a little longer. Along with its exclusive details on the BlackBerry Dakota, Boy Genius Report got some exclusive information about the upcoming Torch 2. 

Packing a beefier 1.2 GHz CPU, the Torch 2 will also boast a higher screen resolution than the original Torch, going from 480x360 to 640x480. Check the full specs below for an idea of how the Torch 2 is shaping up. According to BGR, we can expect the Torch 2 to be available in Q3 of this year.

  • 1.2GHz processor
  • Quad-band GSM/GPRS/EDGE
  • Tri-band HSPA 14.4Mbps
  • 3.2-inch VGA 640 x 480 capacitive display
  • 8GB built-in memory
  • 512MB RAM
  • Bluetooth 2.1
  • GPS
  • NFC
  • 5-megapixel camera with flash
  • Magnetometer
  • Accelerometer
  • Proximity sensor
  • 1300 mAh battery
  • BlackBerry OS 6.1
  • OpenGL ES
  • 14.6mm thin

Oh, and if you’re thinking all of this sounds a little familiar, you’d be right. RIM released the BlackBerry Storm, which lacked WiFi and disappointed users, in 2008. A year later, the BlackBerry Storm 2 was launched and it brought with it features users had been demanding since the launch of the original Storm.

Create a new thread in the Streaming Video & TVs forum about this subject
This thread is closed for comments
Comment from the forums
    Your comment
  • dogman_1234
  • firemachine69
    Where's my N wifi?
  • razor512
    only problem is other than opening some apps faster, you wont notice the added speed since all apps were designed for some of the slowest devices.

    it is like upgrading from a core 2 to a core i7 and expecting a game of pong to run smoother.

    it is great they they are catching up in hardware but the software has not caught up yet.
    then it also opens the whole system requirement problem where when new apps come out designed for the new device, it will have the whole windows mobile problem where all apps will have a long list of system requirements when they are slightly demanding.