virtuous rom problem - G2 and Desire Z General

So i never noticed this till today... i can NOT send mms msg's or pic msgs etc... I can still receive them, but not send.
I could before i upgraded to this rom...
suggestions?

I find out in the last five minutes I have been having the same problem
Sent from my HTC Vision using XDA App

Its going to be hard to help you, if you are cross posting and jumping around. That's one reason why cross/multiple posting is a bad idea (in addition to clogging up the forums needlessly).
http://forum.xda-developers.com/showpost.php?p=12416660&postcount=5116
In the other thread, you replied to my suggestion:
kneedraggin101 said:
Im new to this, so where do I find that information, and where do I find and enter it in the phone?
Click to expand...
Click to collapse
The APN settings are under Menu>Settings>Wireless & networks>Mobile networks>Access point names
Under there, you should see the name of your carrier, press it and look at the settings (or pick the one that is currently selected, there is probably only one choice). Verify the settings are correct. I'm guessing they are not, and the MMS fields in particular need to be corrected.
I just found the Bell APN settings by Googling for it:
Name: Bell Internet
APN: pda.bell.ca
Proxy: web.wireless.bell.ca
Port: 80
MMSC: http://mms.bell.ca/mms/wapenc
MMS proxy: web.wireless.bell.ca
MMS port: 80
MCC: 302
MNC: 610
APN type: Internet + mms
Authentication Type: none
If any of the info is not correct, modify it to read exactly as shown above (except for "Name", which can be whatever you want). You may need to reboot for the settings to take effect. Not a fast boot, a real reboot by holding the power button until the Power Options show, and pick Restart.

I actually had 2 spots to choose, both were identical, but i changed the info, and now i only have one....
but do i have to keep the space between APN type : Internet + mms... or can it be Internet+mms?
also in looking around
* Name: Bell
* APN: pda.bell.ca
* Proxy: web.wireless.bell.ca
* Port: 80
* Username: <Not set>
* Password: <Not set>
* Server: <Not set>
* MMSC: http://mms.bell.ca/mms/wapenc
* MMS proxy: web.wireless.bell.ca
* MMS port: 80
* MMS protocol: WAP 2.0
* MCC : 302
* MNC : 610
* APN type : <Not set>
this is from bell's site... but it says for a HTC Desire.... but it shows the APN type as not set, and you showed me it as internet + mms
so which is correct?

I think <Not set> is fine for APN type.
I've seen the same for my carrier (some list <Not set>, some say something else), and I think putting either works.
BTW, you can easily test if MMS is working by sending one to yourself.

i can send it to my self, not anyone else...
any other options?
cause in notifications, it says unable to send message after multiple attempts
Service denied...
but again i can send them to my self, but thats the msg i get when i try to send to anyone else

Did you need to fix any of the APN settings? If so, did you do a "real" reboot as I mentioned?
You might also check if the size of the media you are sending exceeds the network's limit. I don't know what the limit on Bell is. But you might try the lowest setting possible on Virtuous for starters (600kb). The settings is found in the Messages app in Menu>Settings>Maximum message size.

Hi, sorry if this is not the right thread but I have this problem with Virtuous ROM:
After some time my icons are over-sized that i cannot see them and in some cases my settings won't work (text turns to black "blocks", and i'm guessing that all images with transparent parts turn black?)...

i had the same problem on virtuous quattro. you should go into bootloader (or rom manager) and do a fix permission. i did this way and i solved

Tried it but happened again i'll couple more times but i doubt it
Sent from my HTC Desire Z using XDA

Related

Rogers MMS with Nexus One

The nexus one came set up with data working. I had to manually add the apn settings for MMS though to get it working. For anyone wanting to set it up:
settings->wireless&networks->mobile networks->access point names
add new apn
Name: Rogers MMS
APN: media.com
Username: media
Password: mda01
Server: 172.25.0.107
MMSC: h t t p ://mms.gprs.rogers.com (minus spaces)
MMS Proxy: 10.128.1.69
MMS Port: 80
MCC: 302 (should already be filled in)
MNC: either 720 or 72 depending on your SIM card (should already be filled in)
APN Type: mms
Leave all other settings blank.
I had to reset the phone after making these changes to get my mms messages.
Hey thanks a tonne man, my sick boolean search skills turned this up in the top few hits. Really appreciate it!
Thank you for the info when my N1 arrives this week i will give it a go thanks.

Working T-Mobile US MMS APN Settings.

Mods - I know this is a question asked in most android builds "how do i get mms to send?" so i took some time and tried to work out a bug.
Devs - Ill be testing on all available builds tonight and post the results here.
Mods, Devs, and [Ref] Thread holders - want to use it ? go ahead.
Everyone else -
I cant believe that I have my CCNA (Cisco Certified Network Associate) i did not notice this.
IP address octets cannot have a octet begin with a 0
So. having said that. use these settings and have a great time sending messages.
NAME: T-Mobile US
APN: epc.tmobile.com
PROXY: Blank
PORT: Blank
USERNAME: Blank
PASSWORD: Blank
SERVER: wap.voicestream.com
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS PROXY: 216.155.165.50 <--------- THE .50 is the major change i found.
MMS PORT: Blank
MCC: 310
MNC: 260
AUTH TYPE: NONE <--this is another changed setting. do not leave blank.
APN TYPE: default,supl,mms <-- This also seems to be important.
Make sure after editing that you press the windows key and click save.
Initial test Winmo - Android setup: Miri 17.6, Radio 2.10.50.28_2 / Android; ShubCraft
_______________________________________________________________________________
Another test. This time with Miri 17.6 Radio 2.10.50.28_2 / Android MATTC
Settings from first boot allow me to send MMS. However, Serious degradation not seen in first test.
Settings are:
APN; epc.tmobile.com
prox blank
port none
user none
password none
server none
mmsc mms.msg.eng.t-mobile.com/mms/wapenc
MMS protocol wap 2.0
mcc 310
mnc 260
auth none
type not set
eosrider said:
Mods - I know this is a question asked in most android builds "how do i get mms to send?" so i took some time and tried to work out a bug.
Devs - Ill be testing on all available builds tonight and post the results here.
Mods, Devs, and [Ref] Thread holders - want to use it ? go ahead.
Everyone else -
I cant believe that I have my CCNA (Cisco Certified Network Associate) i did not notice this.
IP address octets cannot have a octet begin with a 0
So. having said that. use these settings and have a great time sending messages.
NAME: T-Mobile US
APN: epc.tmobile.com
PROXY: Blank
PORT: Blank
USERNAME: Blank
PASSWORD: Blank
SERVER: wap.voicestream.com
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS PROXY: 216.155.165.50 <--------- THE .50 is the major change i found.
MMS PORT: Blank
MCC: 310
MNC: 260
AUTH TYPE: NONE <--this is another changed setting. do not leave blank.
APN TYPE: default,supl,mms <-- This also seems to be important.
Make sure after editing that you press the windows key and click save.
Initial test Winmo - Android setup: Miri 17.6, Radio 2.10.50.28_2 / Android; ShubCraft
Click to expand...
Click to collapse
just tried with same set up.... minus the miri rom... running the chucky droid rom... these settings do not work for me....
NONE OF THE POSTED SETTINGS WORK FOR ME... CRAZY thing is i was able to send one last night. ONE! thats it????????????????
tesing multiple message sending now. with initial settings.
Multiple mms on initial settings works. have sent 4 different pictures to multiple numbers. all confirmed working.
just tried it to no avail, running nrg's glass wm, 2.12 radio and dan's froyo v1 with the latest zimage.
how long are you guys letting it run for before deleting the message?
I can confirm these settings work for US T-Mobile just sent one to myself
Using mattc froyo 1.4
Latest zImage
Miri 17.6
Radio 2.12.50
Tmous 1024
Sent from my HTC Desire using XDA App
hmm... benicia... im in Santa rosa. i wonder if these settings might be regional.
eosrider said:
how long are you guys letting it run for before deleting the message?
Click to expand...
Click to collapse
15 min... also if you long press one the sending picture and go to details the size is only 1KB
Now we need to fix the sending size, the pic I sent got so degraded an only 14k from a 250k pic
Sent from my HTC Desire using XDA App
Got it to send one MMS to myself. It took about 15 minutes. Had to disable WiFi. Can't get any more to send.
Using DarkStone froyo
Latest zImage (8/3)
Miri 17.6
Radio 2.12.50
Tmous 1024
Honolulu, HI
i can receive them now, which i couldn't consistently before. still no luck getting them out however.
i should add that it shows the correct file size when i send it as far as i know, none of them have popped up as being 1kb.
If the message details show 1kb you have not sent a message out
working diligently right now.
I beginning to think Miri's ROM is the factor that is allow those to be able to send. Cause i sent 3, and not a single one worked for over 15 min had the logo, wifi, no wifi, and different radios.
Tried 2 other roms and 2 other android builds per winmo rom. nothing worked.
Did not try experimenting with radio tonight but after all was said and done. went back to the first setup ( Android; Shub / Miri 17.6
ok... something really weird is going on. With different builds i sent all different pictures of random items ( lighters, coins, water bottles ). now those builds that failed my testing were all taken off. SD card was formated between builds. I ended up going back to the setup I had when i started this thread, because it works.
Now i have the people who's picture i sent randomly saying that they are getting their pictures. 3 different pictures and people. Keep in mind that this is AFTER I formatted and went back to the working setup. so i didnt have the same pictures on the sd card.
Thoughts?
I think the problem is the windows rom. I tried many different android builds none of them allowed me to send mms. I was only able to receive them.
the serve is not epc.tmobile.com!
Its wap.voicestream.com
stop thinking its epc. Its not. Thats bs it doesnt work very well!
S3BAZ10 said:
the serve is not epc.tmobile.com!
Its wap.voicestream.com
stop thinking its epc. Its not. Thats bs it doesnt work very well!
Click to expand...
Click to collapse
i use epc.tmobile.com on my 2g iphone to send/recieve mms...
so why are you saying it doesn't work?
eosrider said:
Mods - I know this is a question asked in most android builds "how do i get mms to send?" so i took some time and tried to work out a bug.
Devs - Ill be testing on all available builds tonight and post the results here.
Mods, Devs, and [Ref] Thread holders - want to use it ? go ahead.
Everyone else -
I cant believe that I have my CCNA (Cisco Certified Network Associate) i did not notice this.
IP address octets cannot have a octet begin with a 0
So. having said that. use these settings and have a great time sending messages.
NAME: T-Mobile US
APN: epc.tmobile.com
PROXY: Blank
PORT: Blank
USERNAME: Blank
PASSWORD: Blank
SERVER: wap.voicestream.com
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS PROXY: 216.155.165.50 <--------- THE .50 is the major change i found.
MMS PORT: Blank
MCC: 310
MNC: 260
AUTH TYPE: NONE <--this is another changed setting. do not leave blank.
APN TYPE: default,supl,mms <-- This also seems to be important.
Make sure after editing that you press the windows key and click save.
Initial test Winmo - Android setup: Miri 17.6, Radio 2.10.50.28_2 / Android; ShubCraft
_______________________________________________________________________________
Another test. This time with Miri 17.6 Radio 2.10.50.28_2 / Android MATTC
Settings from first boot allow me to send MMS. However, Serious degradation not seen in first test.
Settings are:
APN; epc.tmobile.com
prox blank
port none
user none
password none
server none
mmsc mms.msg.eng.t-mobile.com/mms/wapenc
MMS protocol wap 2.0
mcc 310
mnc 260
auth none
type not set
Click to expand...
Click to collapse
This setting work for me send and recive! Thank in a million!
..... I said this once already.
ROM's with no SenseUI and stock Messaging App should work without error as long as APN is correctly Set. Stock/Non-Sense UI Rom's APN:
Code:
NAME: T-Mobile US
APN: epc.tmobile.com
PROXY: <Not Set>
PORT: <Not Set>
USERNAME: <Not Set>
PASSWORD: <Not Set>
SERVER: <Not Set>
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS PROXY: <Not Set>
MMS PORT: <Not Set>
MMS Protocol: WAP 2.0
MCC: 310
MNC: 260
AUTH TYPE: None
APN TYPE: default,supl,mms
ROM's WITH SenseUI all have the same issue/bugs if you are on T-Mobile in the US (even with the correct APN's set).
MMS pictures are shrunk to tiny tiny 2kb images when receiving with that HTC Messaging App, this is because Sense sends in the user-agent string for MMS found in: /system/customize/MNS/default.xml
T-Mobile's MMS server's doesn't recognize the "HTC Desire" user-agent string therefore when receiving MMS, you get a tiny tiny thumbnail pic. I think you can set it to "NexusOne" Or was it "Nexus One/Build FRFxx". Forgot if it was one or the latter. (OH.. this is only for TMOUS People, I don't think this affects european peeps, since the Desire Rom was made for that region.) Problem with this is, I think those settings are loaded with the initial setup (first boot, and I'm not sure where it's stored afterwards. If you modify now and save it, it seems to have no effect. Also, customized SenseUI seems to ignore the file altogether?)
Those with incorrect, or missing APN's using any ROM with SenseUI. If you are on T-Mobile, your settings should be as follows (This will allow you to send and receive, but theres the file size restriction):
Code:
NAME: T-Mobile Data
APN: epc.tmobile.com
PROXY: <Not Set>
PORT: <Not Set>
USERNAME: <Not Set>
PASSWORD: <Not Set>
SERVER: <Not Set>
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS PROXY: <Not Set>
MMS PORT: <Not Set>
MMS Protocol: WAP 2.0
MCC: 310
MNC: 260
AUTH TYPE: None
APN TYPE: default,supl,mms
Actually, ignore this one, its apparently used for Firmware Over-The-Air updates.
Code:
NAME: T-Mobile FOTA
APN: epc.tmobile.com
PROXY: <Not Set>
PORT: <Not Set>
USERNAME: <Not Set>
PASSWORD: <Not Set>
SERVER: <Not Set>
MMSC: <Not Set>
MMS PROXY: <Not Set>
MMS PORT: <Not Set>
MMS Protocol: WAP 2.0
MCC: 310
MNC: 260
AUTH TYPE: None
APN TYPE: hipri

Does MMS work on hd2 with android froyo?

hello all
i recently changed from the windows os to the android os on my T-mobile US Htc HD2.
i need help with one minor problem i have been having; i cannot send or recieve mms while on android on the HD2.
i am running the android froyo 2.2 by dan1j3l (or however its spelled ) and i have had no problems at all, except this. Oh, and i noticed that the volume(sound:ringtones, speakerphone in calls..) is lower than when running windows mobile. but to make things clear, i do have sound on my HD2 when on android froyo.
those are the only two minor problems i have had on the phone.
please help me
im not sure what other information may be needed in order to help me solve my problem, but it would be much appreciated!
thank you,
Vic_Gar
most everyone IS having trouble with the mms... i can recieve as i've heard others can as well but few can send. it's being worked on.
As for sound, it's the same thing... i think i read a few builds have improved sound quality but i'm not sure which... just gotta keep trying em all out, that's what i did.
I am also having this problem hopefully the devs will fix this..its been a month since i could send or recieve MMS
oo and im running froyostone rom
add me to the list.
although...i did have it working for a bit, using the settings where the proxy was set up in the default apn as well as the mmsc field. but it was SLOOOOOOOW (like 10 mins) to send an MMS. I messed with it (of course) now it won't send at all.
I can't find where I saw it but as far as low volume goes you need to max the volume in Windows before booting Android. As android basically runs like an app initially the WM volume setting is applied to it. Hope that helps.
ok, mms is working again.
it's still really slow though. This is my setup. What's a bit different from what I've seen is the combo of filling out the default prox/port and the apn type. I think most of what i've seen suggests filling one or the other.
Name: T-Mobile US
APN: epc.tmobile.com
Proxy: 216.155.165.050
Port: 8080
Username:
Password:
Server:
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS Proxy: 216.155.165.050
MMS Port: 8080
MMS Protocol: WAP 2.0
MCC: 310
MNC: 260
APN Type:default,supl,mms
vic_gar said:
Oh, and i noticed that the volume(sound:ringtones, speakerphone in calls..) is lower than when running windows mobile. but to make things clear, i do have sound on my HD2 when on android froyo.
Click to expand...
Click to collapse
I had this issue before myself when I first installed Froyo. What I did:
Before booting into Android, I made a call and hit Speaker, then raised the Call Volume all the way. I then turned off Speaker and raised the Call Volume again. I also double-checked the "Sounds" settings and made sure everything was set to "Normal".
I no longer have issues with the sound.
Hope this helps!
I can send and reciece MMS in Android
Im running Htcclay's SuperHD2 on mine and the only thing that acts up is if i use Chomp SMS. When that preview popup comes up with the text, when i reply it doesnt send. Everything works fine if i open the text and send a sms/mms
I have better luck sending and receiving mms using RMNET rather than ppp. It is very slow to send though...
I tried xjjk settings and, they did work for me. I don't have the MMS Protocol setting. Mine is not slow either.
So far this is working for me.
I'm using Darkstone HD2Froyo V3
There is a mdeejay build revolution 1.5. It has a link to mms fix for t-mobile us.
Sent from my HTC HD2 using XDA App
thanks!
this worked perfectly!
xjjk said:
ok, mms is working again.
it's still really slow though. This is my setup. What's a bit different from what I've seen is the combo of filling out the default prox/port and the apn type. I think most of what i've seen suggests filling one or the other.
Name: T-Mobile US
APN: epc.tmobile.com
Proxy: 216.155.165.050
Port: 8080
Username:
Password:
Server:
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS Proxy: 216.155.165.050
MMS Port: 8080
MMS Protocol: WAP 2.0
MCC: 310
MNC: 260
APN Type:default,supl,mms
Click to expand...
Click to collapse
tooter1 said:
I tried xjjk settings and, they did work for me. I don't have the MMS Protocol setting. Mine is not slow either.
So far this is working for me.
I'm using Darkstone HD2Froyo V3
Click to expand...
Click to collapse
How'd you get it to start working?
While booted in android goto settings, wireless controls, mobile networks, access point names, press menu and select new apn, enter the above settings, press menu save. Go back into apn and select your apn you created.
Sent from my HTC HD2 using XDA App
I tried to use the settings, however I can not select WAP 2.0 I'm using nand cyanogen 2.1 build.. I get the little 3G symbol then all of a sudden it tells me "unsuccessful"
settings
yes follow the directions to add the MMS settings on your phone. everything will work after you install but with Android on your Micro SD card remember to reboot after the first boot. then everything should work.
once i got the settings right everything was working fine recv and sending MMS
xjjk said:
ok, mms is working again.
it's still really slow though. This is my setup. What's a bit different from what I've seen is the combo of filling out the default prox/port and the apn type. I think most of what i've seen suggests filling one or the other.
Name: T-Mobile US
APN: epc.tmobile.com
Proxy: 216.155.165.050
Port: 8080
Username:
Password:
Server:
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS Proxy: 216.155.165.050
MMS Port: 8080
MMS Protocol: WAP 2.0
MCC: 310
MNC: 260
APN Type:default,supl,mms
Click to expand...
Click to collapse
Those are one of the two most common TMOUS "working" settings I've seen floating around on the forums, and I highly believe that the settings depend on your plan, location, or some other vague difference. Also, some mention setting the proxy screws up their https sessions. The other version is:
APN: epc.tmobile.com
Proxy: <not set>
Port: <not set>
Username: <not set>
Password: <not set>
Server: <not set>
MMSC: http://216.155.174.84/servlets/mms
MMS Proxy: 216.155.165.50
MMS Port: 8080
MMS Protocol: WAP 2.0
MCC: 310
MNC: 260
APN Type:default,supl,mms
There's a few TMOUS MMS threads floating around that might have other settings as well. Try one of the two above & see what works for you.
Also, I found I can't send MMS to a friend of mine, and after some troubleshooting, found that it's our phones sending too big of pics for her phone (on AT&T) to receive. I installed an app on an earlier build (that I can't remember name of) that pre-shrunk pics before sending, which then worked fine. So, when testing, check to see if it's your phone not sending, or just theirs not receiving.
This fixed my issue! yay! Thanks you!
xjjk said:
ok, mms is working again.
it's still really slow though. This is my setup. What's a bit different from what I've seen is the combo of filling out the default prox/port and the apn type. I think most of what i've seen suggests filling one or the other.
Name: T-Mobile US
APN: epc.tmobile.com
Proxy: 216.155.165.050
Port: 8080
Username:
Password:
Server:
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS Proxy: 216.155.165.050
MMS Port: 8080
MMS Protocol: WAP 2.0
MCC: 310
MNC: 260
APN Type:default,supl,mms
Click to expand...
Click to collapse

[Q] Unable to send MMS on AT&T network

I can receive MMS just fine. I can use the internet, market place, etc. However, If i try to send one, it will just stay in the sending phase forever. I even tried sending one to myself with no luck.
I am using hyperdroid1.7 and I cannot get this to work.
Anyone ? I've seen fixes for other networks but not one for at&t
SOLUTION:
make sure password is set to CINGULAR1, may require a soft reset after.
I have been using this rom Moto234_Evo_Carbon_Remix on my HD2 and after I set the AT&T MMS settings, I can send msgs, you need to double check your MMS settings under msgs, and you need to check your settings under connections.
AngelDeath said:
I have been using this rom Moto234_Evo_Carbon_Remix on my HD2 and after I set the AT&T MMS settings, I can send msgs, you need to double check your MMS settings under msgs, and you need to check your settings under connections.
Click to expand...
Click to collapse
there really isn't much to be changed in the settings under the messaging app.
would you be able to double check these to see if they match yours? (under access point names)
name: ATT
apn: wap.cingular
proxy: -
port: -
username: [email protected]
password: -
Server: -
MMSC: http://mmsc.cingular.com
MMS Port: 80
MCC: 310
MNC: 410
Authentication type: -
APN type: default,supl,mms
brunodemelo said:
there really isn't much to be changed in the settings under the messaging app.
would you be able to double check these to see if they match yours? (under access point names)
name: ATT
apn: wap.cingular
proxy: -
port: -
username: [email protected]
password: -
Server: -
MMSC: http://mmsc.cingular.com
MMS Port: 80
MCC: 310
MNC: 410
Authentication type: -
APN type: default,supl,mms
Click to expand...
Click to collapse
Password is CINGULAR1
AngelDeath said:
Password is CINGULAR1
Click to expand...
Click to collapse
oh wow. Thanks, I tried this before but it didn't work. I guess I just needed a soft reset or wait longer. I feel dumb
i can send very small pictures, but it seems that regular sized non cropped pictures from the camera never get sent.
That I cant help you with, I can tell you that I sent a test pic from my phone to my tilt 2 and it wasnt a small pic but a fullscreen.
anyone have any info on this?

[Q][Help] Network/APN/Full Bars Failed Call

Hi,
First of all, I'm running Cotulla's Stock Desire NAND Rom on my HTC Leo.
Lately I've been having the problem, a week at this point, where I have full bars and am unable to place/receive phone calls or send/receive text messages. This problem goes on for about 5 minutes everytime I unlock my phone. It's at a point where I don't even get incoming calls/texts.
I've done some searches, but all threads I've read say that it's most likely my area's tower's fault. But I'm just making sure because it seems highly unlikely that it only happens when my phone is locked...
Anyways, I'm also wondering if it has anything to do with my APN settings, since sometimes when I switch from one of them to another it seems to fix the problem for an hour or two.
I am unable to post my APN's because of the restriction that new users can't post outside links (which I guess includes the links in MMSC and server of the APN) My first APN uses epc*tmobile*com and my second one uses wap*voicestream*com
I will try and post my full APN info as soon as I can.
Edit: Here are my two APN's with * instead of . (sorry if I'm breaking a rule)
(and *** = http)
Name T-mobile US
APN epc*tmobile*com
Proxy (Not Set)
Port (Not Set)
Username (Not Set)
Password (Not Set)
Server (Not Set)
MMSC ***www*mms*msg*eng*t-mobile*com/mms/wapenc
MMS proxy (Not Set)
MMS port (Not Set)
MMS protocol WAP 2.0
MCC 310
MNC 260
Authentication type None
APN type (Not Set)
#2
Name T-mobile US
APN wap*voicestream*com
Proxy 216*155*165*050
Port 8080
Username (Not Set)
Password (Not Set)
Server ***216*155*147*54/servlets/mms
MMSC ***www*mms*msg*eng*t-mobile*com/mms/wapenc
MMS proxy 216*155*165*050
MMS port 8080
MMS protocol WAP 2.0
MCC 310
MNC 260
Authentication type None
APN type (Not Set)
For a while I was using #2 because #1 was refusing to give me any data connection, but now I am using #1 after learning #2 was the old non-smartphone APN.
Is there anything wrong with my first APN setting? And could my inability to place calls be due to anything other than my local towers?
Thank You
Try these settings for APN. These are for data plan tmobile, it's hard to say which settings is best until we try it.
Name: T-Mobile US
APN: epc.tmobile.com
Proxy: <not set>
Port: <not set>
Username: <not set>
Password: <not set>
Server: <not set>
<>MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
<PPP**>MMSC: not set
MMS Proxy: <not set>
MMS Port: <not set>
MMS Protocol: WAP 2.0
MCC: 310
MNC: 260
Auth Type: <not set>
APN type: default,supl,mms
Name: T-Mobile US
APN: epc.tmobile.com
Proxy: 216.165.155.050
Port: 8080
Username: None
Password: **** (These are just stars, you can put it in there manually)
Server: * (Same)
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS Proxy: 216.165.155.050
MMS Port: 8080
MCC: 310
MNC: 260
So I tried both out for about half of the day, and I'm having better data speeds with the 2nd APN setting (consistently around 2.75-3.5Mbps) however I'm still having the issue of sometimes not receiving/being able to send texts and calls even though I have full bars and am able to open my browser and load webpages. Is it likely that this is just T-mobile's fault or could there my an issue with my phone?
_iKiller_ said:
So I tried both out for about half of the day, and I'm having better data speeds with the 2nd APN setting (consistently around 2.75-3.5Mbps) however I'm still having the issue of sometimes not receiving/being able to send texts and calls even though I have full bars and am able to open my browser and load webpages. Is it likely that this is just T-mobile's fault or could there my an issue with my phone?
Click to expand...
Click to collapse
Not being able to send out text could be a problem with your current ROM. Try tytung's ROM, follow my sig. It's really sweet with tmobile.
Have u tried changing you're radio...
Sent from my Nexus One
bigfdaddy said:
Have u tried changing you're radio...
Sent from my Nexus One
Click to expand...
Click to collapse
I've changed the radio twice now, from my original 2.08.50.08 to 2.15.50.14(latest htc version) to 2.09.50.29_2(latest tmous release) and I'm still having the same issues of having full bars and not receiving texts/calls.
I really would hate to switch from this ROM, is there any other possible solutions to this issue?
If not, I guess it's time to try a new ROM... to flash a new Android ROM onto my HD2, do I boot into the Magldr USB Flasher or HSPL Flasher?

Categories

Resources