[seattlekate]

My goal: to use a Twitter app I like (Twibble or TinyTwitter) on my new flip pearl with T-Mobile. They worked fine on my regular pearl.

I'm posting it in this forum because the problem occurs with EVERY third-party app I've tried that uses a direct TCP connection. (I've tested with Twibble, TinyTwitter, TwitterBerry, and Beyond411.) When connected via the mobile network, I get an error like "tunnel failed". When connected via wi-fi, I get an error like "DNS Error".

I've confirmed with T-Mo that my APN is set correctly (to wap.voicestream.com). I've set the TLS to Handheld.

I have spent hours combing through forums on this site and others, searching for the various error messages I got from the apps and the Blackberry's event log (which varies; one example is net.rim.device.cldc.io.dns.DNS Exception:DNS Error) with no useful results.

I exhausted both the T-Mobile and RIM tech support groups, who try to give a bit of help but beg off pretty soon with the excuse that they can't help with a third-party app (even though I'm fairly certain the problem is NOT with any specific app).

Now I need to determine if the problem is with only my device, something with my connection to T-Mo, or something new with OS 4.6. Have any of you fellow 8220 owners tried these apps I mention above? I'm desperate for help - if you can shed any light on this, I'd be very appreciative.

I'm happy to give details of any of my troubleshooting if needed. Thanks in advance.

[makedonce]

I have similar problem with my 8320 but only after I install OS 4.5. Tried upgrading the OS 3 times so far and every time i upgrade the direct TCP doesn't work. When i downgrade to 4.2 its all good.
I would be very curious to know the solution if u manage to solve the problem.

[Nextel User]

curious........i have in unlocked 8220 on ATT and until i put the att APN settings in, TCP did not work. now it works fine.

i used Berry411 for the test.

[seattlekate]

Thanks, Nextel User. My suspicion is that something is wrong in the T-Mobile network somewhere (like a DNS server), but their tech support people have little to no understanding of Blackberry and won't go far enough with me to do any useful troubleshooting. Any T-Mo users having the same problem? Or any T-Mo users who are able to get a direct TCP connection?

[Fonz0]

I have a new BB curve on Tmobile and have the same error. Twibble and Twitpic do not work. Spent yesterday on the phone with TMO and RIM. RIM pointed me to a work around by testing MMS. MMS on TMO requires you to login to myTmobile and accept usage rules. Once I did that at least I could MMS to Twitpic. I want to avoid using MMS though to avoid charges.

[Fonz0]

New 8320 on TMO and have the same issue. Only workaround is sending MMS to Twitpic. Even that was fun as TMO does not allow MMS UNTIL you visit mytmobile and accept usage rules, but they don't tell you that. Still hoping for a non MMS solution to avoid charges.

[seattlekate]

The problem is now fixed! What seemed to do it was upgrading to the latest (T-Mo) OS, 4.6.0.180. I got it from the T-Mobile site. I can't post URLs, but if you put bbupgrade after t-mobile's domain, you'll get there.

[thelung187]

Originally Posted by seattlekate

The problem is now fixed! What seemed to do it was upgrading to the latest (T-Mo) OS, 4.6.0.180. I got it from the T-Mobile site. I can't post URLs, but if you put bbupgrade after t-mobile's domain, you'll get there.

I created an account on this forum just to say THANK YOU SOOOOO MUCH!!! I have been wracking my brain (as well as Google's servers) for the past 2 weeks to find an answer to this, and the OS update worked out brilliantly!