Joe

BBGeekcast: September 18, 2009 – Episode 82

Posted by Joe on September 18, 2009 | 1 comment | Filed under : BlackBerry Podcasts

Some weeks we get a little bit of big news. Other weeks we get a lot of little news. This is one of the latter. We did see some Storm 2 pictures stay on the Internet for more than a few hours, a sign that it’s probably coming soon. Not that we didn’t already know that. It’s just nice to have assurances.

So click on over here to hear the BBGeekcast (9 min, 5 sec)

And don’t forget to subscribe to the podcast so you won’t miss future episodes!

You can also subscribe to the BBGeekcast in iTunes.

Highlights include:

The Storm 2 is the future, and the way a current issue is going, the Tour might be the past. There appears to be a widespread trackball issue with the device, causing people to exchange the device left and right. What is Verizon going to do about it? I’ve heard they’re not exchanging the devices any more. That’s a shame. Sorry to anyone who’s stuck with a faulty trackball.

There are other tidbits too, like OS 5.0 coming out some time this year — we hope. RIM said so. Can we take their word for it?

Oh yeah, and the U2 mobile album. That seems to be a big deal. I don’t care for the band, but the concept is solid. Mobile is an excellent platform on which to distribute supplemental material with an album.

BlackBerry Accessories

1 Scott Spillers September 23, 2009 at 2:17 pm

FYI, the BlackBerry Tour 9630 trackball issue was resolved and is no longer present in Tours manufactured after August 3, 2009.

After RIM tech support shared this bit of information with me, I contacted Sprint and they allowed me to exchange my Tour for a new one manufactured on August 11, 2009. The trackball on the new Tour is perfect.

It is still unclear what cause of the trackball issue is. The newer Tours are running the very same OS version 4.7.1.40, but some Verizon Tour owners have reported that upgrading to OS version 4.7.1.53 has corrected the trackball issue.

Leave a Reply

(required)
(will not be published) (required)
(opitional)
 

Previous post:

Next post:

ss_blog_claim=3a8d22f82df901ea5614ea99ae1f131f