Is RIM Crippling BlackBerry Bluetooth?

Comments

BluetoothThis comes by way of friend and fellow blogger Alex King. You may remember that Alex organized the bounty for a “BlackBerry as a modem” solution for Mac OS X. This bounty resulted in the product Pulse, which turns your BlackBerry into a Bluetooth modem for both Macs and PCs.

Here’s where it gets interesting.

The Pulse solution doesn’t run as fast as it should. Brain Murmurs (the company that made Pulse) set about working with users and doing tests to discover the problem. What did they find? That Bluetooth speeds for BlackBerrys have been crippled by each subsequent RIM OS upgrade.

The question now becomes why this has happened and what RIM is going to do to fix it? It should be noted that the BlackBerry Pearl (running on OS 4.2) is not affected, which most likely indicates that the 4.2 OS development broke off before the problem was introduced into 4.1. Whatever the reason, this news sucks for non-Pearl BlackBerry Bluetooth users.

Post a comment and let us know if you think this is a RIM goof or intentional.

  • Krad

    Interesting—-

    some key points….

    - Battery Life
    - DOD/ Government regulations
    - RIAA/MPAA??
    - NTP / RIM cutover fix?

    seems that rim is cutting on some powerful features to conserve battery power… especially the auto-dim option on the pearl.

  • Krad

    Interesting—-

    some key points….

    - Battery Life
    - DOD/ Government regulations
    - RIAA/MPAA??
    - NTP / RIM cutover fix?

    seems that rim is cutting on some powerful features to conserve battery power… especially the auto-dim option on the pearl.

  • dp

    What I’m ticked off on with blackberry and pearl is when I play music or a video I can’t listen with my Jabra Bluetooth headset…any idea why? Is there a fix for this? Am I doing something wrong?

  • dp

    What I’m ticked off on with blackberry and pearl is when I play music or a video I can’t listen with my Jabra Bluetooth headset…any idea why? Is there a fix for this? Am I doing something wrong?