[mmspearl]

i'm on tmobile and none of the apps that require wap.voicestream.com in APN are working. they act like the field is left blank. jivetalk gives an "open tunnel failure" and opera "could not establish connection"

tcp down or possibly new apn setting we dont know of?

[CaptSwerve]

I'm having problems with my T-Mobile as well. The BB specialist I talked to said something about problems with data in Atlanta and something about the East coast. Good news is that she's talking about getting me a new phone.

[dankarlinski]

Wirelessly posted (8100 pearl: Mozilla/4.8 [en] (Windows NT 5.0; U) BlackBerry8100/4.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/100)

Tmobile service will be periodically up and down due to upgrading their radios for their 3G release early next year. I have talked to them and they are trying to operate on the radios in the night time to reduce disturbance. But it will also be down from time to time.

Its normal. Don't panic

[Korexz]

Did you upgrade to .107?

Basically I have found that NONE of the APN settings work with .107.

[TheBigNewt]

Originally Posted by Korexz

Did you upgrade to .107?

Basically I have found that NONE of the APN settings work with .107.

I have .107. MiniOpera works for me, at least it did last weekend.

[Jasper101]

I have .107 & T-Mobile also, I was using Opera Mini around 5 minuets ago and its working perfectly. I am using Opera mini 4 Beta 2.

Gawd I love Opera Mini!

[mmspearl]

Did you upgrade to .107?

Basically I have found that NONE of the APN settings work with .107.

i had .107 and any 3rd party apps that required use of an APN was conflicting with MMS messages. it was either one or the other until a battery pull. so i downgraded.

[ezrunner]

Wirelessly posted (BlackBerry8700/4.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/100)

I have had no problem with .107 and third party apps

[mmspearl]

i have the 8100. maybe thats why?

[mmspearl]

i'm really curious if what i experienced was with JUST my phone. can you conduct a small test for me please?

this only applies to those who either use jivetalk (with TCP chosen for connectivity) and operamini browsers. or any other 3rd party app that requires "wap.voicestream.com" to be entered under APN settings.

open up operamini and let it load any site, once completed, go to your pictures and try sending one to yourself. does it send or do you get the red X?

another test, send yourself a pic text first then try loading a website/webpage with operamini. does it say could not establish connection?

if youre using jivetalk with TCP as connection in preferences and its running in the background. try sending a pic to yourself, again do you get the red X when trying to?

thanks guys

[richardrblc]

Wirelessly posted (BlackBerry8100/4.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/100)

Mine sent

[John Clark]

Ezrunner has an 8100, as well. I had no problems with the 8100, .107 and third party apps either.

[mmspearl]

That's so disturbing. Why would I be the only person with that problem?

[joginder]

I just talked to TMO and they are havin issue for this whole week and I am rebooting the dev 2-3 times a day

[mmspearl]

anyone else?

[TroyDBrown]

I have .107 on my 8100 with no problems with the above mentioned apps.

[blakeatl]

I had to resend my service books in order to get my main browser to work earlier in the day. Opera, bbweather and bbtoday can't connect using the apn settings.

[camaro322hp]

Originally Posted by mmspearl

open up operamini and let it load any site, once completed, go to your pictures and try sending one to yourself. does it send or do you get the red X?

I get a red X. So then I did a soft reset and tried to send an MMS first, and I still get the red X. Not sure if my test is valid as it looks like I can't send MMS at all.

Guess it's time to call TMo.

[CaptSwerve]

I loaded a page in Opera and got the red X when sending a picture.

[mmspearl]

which ones were people using and had no problems with?

i've been on cingular .71 with desired results with the exception of opera 4 beta 2 giving an uncaught;exception java error.

so i was curious to see if anyone was running a different version besides the new t-mobile .107 where opera 4 beta 2 worked fine.